February 26, 2021 Roberto Puzzanghera53 comments
Vpopmail provides an easy way to manage virtual email domains and non /etc/passwd email accounts on your mail servers.
The purpose of this note is to show how to use Mysql
as the authentication system. Having a users database also offers the advantage of communicating with the database via PHP
, and creating web-based user interfaces to manage accounts.
vsavealiasdomains
can now save all the existing domain aliases to MySQL. It can be useful in case of migrations to the dovecot
's sql auth driver.The patch we'll apply puts together the following patches:
gcc-10
Create vpopmail user and group:
groupadd -g 89 vchkpw useradd -g vchkpw -u 89 -d /home/vpopmail vpopmail
Download the source (original files here: http://sourceforge.net/projects/vpopmail/files/, but you can download my local copy) and configure.
cd /usr/local/src wget https://notes.sagredo.eu/files/qmail/tar/vpopmail-5.4.33.tar.gz wget https://notes.sagredo.eu/files/qmail/patches/vpopmail/roberto_vpopmail-5.4.33.patch tar xzf vpopmail-5.4.33.tar.gz cd vpopmail-5.4.33 chown -R root.root . patch -p1 < ../roberto_vpopmail-5.4.33.patch autoreconf -f -i ./configure \ --enable-qmaildir=/var/qmail/ \ --enable-qmail-newu=/var/qmail/bin/qmail-newu \ --enable-qmail-inject=/var/qmail/bin/qmail-inject \ --enable-qmail-newmrh=/var/qmail/bin/qmail-newmrh \ --disable-roaming-users \ --enable-auth-module=mysql \ --enable-incdir=/usr/include/mysql \ --enable-libdir=/usr/lib64 \ --enable-logging=p \ --disable-clear-passwd \ --enable-auth-logging \ --enable-sql-logging \ --disable-valias \ --disable-mysql-limits \ --disable-passwd \ --enable-qmail-ext \ --enable-learn-passwords \ --enable-sql-aliasdomains \ --enable-defaultdelivery
--disable-roaming-users
roaming users will be disabled, since we don't want to use POP before SMTP authorization. We will patch qmail with smtp-auth instead.
--enable-auth-module=mysql
builds mysql support and stores virtual users accounts into a mysql database.
--enable-incdir=/usr/include/mysql
Your MySQL include
dir (use just in case you installed mysql from binaries or source in a non standard location. Mount mysql dir somewhere if it is installed in a different machine).
--enable-libdir=/usr/lib64
Your MySQL lib
dir. Obviously it might be /usr/lib
on 32b systems
--disable-valias
Do not store aliases in MySQL
, but as dot-qmail
files.
Note: it appears that dovecot-lda
continues to look for .qmail-alias files also when you enable this. So this option is useless if you deliver via dovecot-lda
--disable-passwd
Don't include /etc/passwd support. I don't want to manage real users, this is just a web server.
--disable-clear-passwd
Clear password will be not be saved on DB. If you don't want to have problems when users forget their passwords and you want to recover them quickly switch this to --enable-clear-passwd
.
--enable-sql-logging
Maintain the vlog table in MySQL (shows failed authentication requests).
--enable-auth-logging
Maintain a lastauth table in MySQL (shows when / how a user last accessed their email)
--disable-mysql-limits
MySQL doesn't store limits instead of .qmailadmin-limits
files.
--enable-qmail-ext
Enable qmail email address extension support (emails containing dots).
--enable-sql-aliasdomains
(default) saves domain aliases to MySQL in order to validate the authentication for domain aliases when using the dovecot
's sql driver, provided that you modify the password_query
accordingly.
--enable-defualtdelivery
installs into the .qmail-default
file of each new domain the delivery agent stored in /var/qmail/control/defaultdelivery
.
Compile and install:
make install-strip
vusaged
looks up every vpopmail
user and tracks how much storage space they’re using. It requires libev
.
cd /usr/local/src wget http://dist.schmorp.de/libev/libev-4.33.tar.gz tar xzvf libev-4.33.tar.gz cd libev-4.33 chown -R root.root . ./configure make make install ldconfig
vusaged
cd /usr/local/src/vpopmail-5.4.33/vusaged ./configure make cp -f vusaged /home/vpopmail/bin cp -f etc/vusaged.conf /home/vpopmail/etc
Now copy the startup script ro /etc/rc.d (Slackware) or init.d and run it. This is a Slackware example:
cp contrib/rc.vusaged /etc/rc.d/ /etc/rc.d/rc.vusaged start
Check your ~vpopmail/etc/tcp.smtp
file This file should list all the static IPs of your machines that you want to allow to relay out to the internet. For example: to allow relaying for localhost and the localnet 10.0.0.x edit your ~vpopmail/etc/tcp.smtp as follows:
10.0.0.:allow,RELAYCLIENT="" 127.:allow,RELAYCLIENT=""
add any other IP later, whenever you want. To give a client relay access, add an entry to ~vpopmail/etc/tcp.smtp like:
IP address of client:allow,RELAYCLIENT=""
Now build the tcp.smtp.cdb. This command must be run every time you modify tcp.smtp
cd ~vpopmail/etc tcprules tcp.smtp.cdb tcp.smtp.tmp < tcp.smtp
Now setup a quota warning that will be delivered to users when they are at 90% quota
# nano ~vpopmail/domains/quotawarn.msg From: SomeCompany Postmaster <postmaster@yourdomain.com> Reply-To: postmaster@yourdomain.com To: SomeCompany User:; Subject: Mail quota warning Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Your mailbox on the server is now more than 90% full. So that you can continue to receive mail, you need to remove some messages from your mailbox. If you require assistance with this, please contact our support department : email : support@yourdomain.com Tel : xx xxxx xx
chmod 600 ~vpopmail/domains/quotawarn.msg chown vpopmail.vchkpw ~vpopmail/domains/quotawarn.msg
Now adjust ~vpopmail/etc/vlimits.default. I use to limit the default user quota to 100MB (in bytes):
default_quota 104857600
vusaged
bug (only vpopmail 5.4.30)This bug appears to have been fixed in version 5.4.32. So skip this section if you’re installing 5.4.32.
Setting the default quota seems to cause this error when creating new domains:
client_connect: warning: config_begin failed Segmentation fault
I saw the same error when creating new users via qmailadmin
. This appears to be a bug in the 5.4.30 version: http://www.mail-archive.com/vchkpw@inter7.com/msg27383.html So, even if you're not using vusaged
it'll be necessary to configure vusaged.conf
as by Matt Brookings suggests, in order to avoid this bug:
cat > ~vpopmail/etc/vusagec.conf << __EOF__ Server: Disable = True; __EOF__
If you’re interested in reading more about this, see http://comments.gmane.org/gmane.mail.qmail.admin/4761, where Matt says that vusaged
isn’t needed (for quotas to work) in vpopmail
version 5.4.30.
mysql
back endCreate the vpopmail
user and database. Grant all privileges to the vpopmail
user. Then quit out of MySQL
and save the authentication information for the vpopmail
account into the vpopmail.mysql
config file:
> /usr/local/mysql/bin/mysql [-h mysql-IP] -u root -p CREATE USER 'vpopmail'@'mailserver-IP' IDENTIFIED BY 'vpopmailpwd'; GRANT USAGE ON * . * TO 'vpopmail'@'mailserver-IP' IDENTIFIED BY 'vpopmailpwd' WITH MAX_QUERIES_PER_HOUR 0 MAX_CONNECTIONS_PER_HOUR 0 MAX_UPDATES_PER_HOUR 0 MAX_USER_CONNECTIONS 0 ; CREATE DATABASE IF NOT EXISTS `vpopmail` ; GRANT ALL PRIVILEGES ON `vpopmail` . * TO 'vpopmail'@'mailserver-IP'; > echo "mysql-IP|0|vpopmail|vpopmailpwd|vpopmail" > ~vpopmail/etc/vpopmail.mysql
where mysql-IP
is the IP of the server which runs mysqld
, and mailserver-IP
is the IP address where qmail
is running. Usually you can specify ‘localhost’ or 0.0.0.0 for both.
cd ~vpopmail/bin/
To add/delete a virtual domain
./vadddomain yourdomain.net [./vdeldomain yourdomain.net]
To add/delete a virtual user
./vadduser user@yourdomain.net [./vdeluser user@yourdomain.net]
To view information about user email accounts:
./vuserinfo user@yourdomain.net name: user passwd: xxxxxxxxxxxx clear passwd: xxxxxxxxx comment/gecos: Name Surname uid: 0 gid: 0 flags: 0 gecos: Name Surname limits: No user limits set. dir: /home/vpopmail/domains/yourdomain.net/user quota: 104857600S
These commands can be useful. But it will be much easier to manage domains and accounts when we install the vqadmin
and qmailadmin
web interfaces later.
You may be interested to take a look to this page concerning vpopmail
testing.
dovecot
's sql auth driverIf you don't have domain aliases or this is a fresh installation you can skip this step.
If you already have domain aliases and want to switch to the dovecot
's sql auth driver, don't forget to read carefully the page where the vpopmail/dovecot
setup concerning domain aliases is explained, as you'll have to save your existing alias/domains pairs to MySQL
.
In short, you can quickly save all your domain aliases to MySQL in this way
vsavealiasdomains -A
Type
vsavealiasdomains -h
for more options.
The database record will be saved by vpopmail for the new aliases that you will create from now on.
problem with passwords containing special characters like %
February 26, 2021 22:02
problem with passwords containing special characters like %
February 26, 2021 10:05
What about using --disable-many-domains on vpopmail configure ?
February 22, 2021 16:49
aliasdomain patch compilation issue
February 21, 2021 16:28
aliasdomain patch compilation issue
February 21, 2021 14:35
Lua backend
February 16, 2021 16:07
What about using --disable-many-domains on vpopmail configure ?
February 14, 2021 03:05
What about using --disable-many-domains on vpopmail configure ?
February 14, 2021 01:20
Lua backend
February 12, 2021 17:40
Lua backend
February 12, 2021 14:28
Tags
apache clamav dkim dovecot ezmlm fail2ban hacks lamp letsencrypt linux linux-vserver lxc mariadb mediawiki mozilla mysql openboard owncloud patches php proftpd qmail qmailadmin rbl roundcube rsync sieve simscan slackware spamassassin spf ssh ssl surbl tcprules tex ucspi-tcp vpopmail vqadmin
Comments
problem with passwords containing special characters like %
blueintheface February 26, 2021 10:05
I'm doinig a fresh installation, decided to compile with --enable-clear-passwd and am running into the following problem:
Using "%#" or "%+" or the like doesn't seem possible, but "%R" works.
OS: OpenSUSE 15.2
DB: MariaDB 10.4.17
Server-Character-Set: UTF-8 Unicode (utf8mb4)
Database "vpopmail" was created using collation "utf8mb4_general_ci", which is the default for standard MariaDB installation.
I'm ok with changing passwords for existing users (have to import a couple of existing domains) but am afraid there may be other issues with passwords and authentication.
Or is it just the clear password which is the problem and authentication with whatever client will be ok even when passwords like '%RxtraMT#66%' are used?
Reply | Permalink
problem with passwords containing special characters like %
Roberto Puzzanghera blueintheface February 26, 2021 22:02
Hi, I tested that password and it was accepted here...
which vpopmail version and patch?
PS tested both with mariadb-10.5.9 (query from command line) and mariadb-10.0.0.112
Reply | Permalink
aliasdomain patch compilation issue
Wouter de Geus February 21, 2021 14:35
Hi Roberto!
Recently I switched to the SQL driver and of course ran into the aliasdomains issue, so today I gave your patch a shot using a new alpine-3.13 build.
However, it runs into a snag:
This is after running autoreconf.
I did also apply the GCC 10 patch, because without it the compilation broke on MYSQL definitions.
Suggestions?
Reply | Permalink
aliasdomain patch compilation issue
Roberto Puzzanghera Wouter de Geus February 21, 2021 16:28
Hi Wouter!
I thought I have corrected this compilation issue in the feb 15 patch... can you confirm that you downloaded this latest version marked as 2021.02.15? Just look at the first line of the patch file
which gcc version?
PS gcc-10 compat patch is already included into the latest sql-aliasdomains patch
Reply | Permalink
You step "Installing and configuring vpopmail"
johan lesky February 12, 2021 13:57
... Do I need to have MySQL or MariaDB, installed before I run Your step "Installing and configuring vpopmail" ?
grdt.
Reply | Permalink
You step
Roberto Puzzanghera johan lesky February 12, 2021 14:26
One of the two. It does not make any difference
Reply | Permalink
Problem compiling vpopmail with postgresql support on alpine 12
Bogdan December 4, 2020 07:28
Hi,
I try compile vpopmail with pgsql support on alpine 12 and I get error:
Can somebody tell what I should do to fix this problem?
Reply | Permalink
Problem compiling vpopmail with postgresql support on alpine 12
Roberto Puzzanghera Bogdan December 4, 2020 18:41
You have compilation breaks because vpopmail is not compatible with the new gcc-10.
Try this patch (you may want to apply only the changes to vpgsql.c): https://notes.sagredo.eu/files/qmail/patches/vpopmail/vpopmail-5.4.33_gcc-10-compat.patch
Let me know if it works
Reply | Permalink
Problem compiling vpopmail with postgresql support on alpine 12
Bogdan Roberto Puzzanghera December 7, 2020 11:39
works well
Reply | Permalink
Using dovecot-lda with vpopmail valias database table
Michael Dick September 29, 2020 21:59
Hi Robert
I have an extensive valias table, and I recently added sieve filtering.
As mentioned above in the thread between you and Eric, dovecot-lda doesn't respect the vpopmail.valias entries in the database, and instead relies on .qmail-alias files. That meant that for mail to be delivered to my aliases, I either needed to create a .qmail-alias file for each one (which would be a mess), or keep using vdelivermail and skip sieve filtering.
As an alternative to Eric's solution of creating .qmail-alias files, you can --enable-valias and add an entry for the destination account to the valias table and keep the delivery agent set to vdelivermail.
This is my .qmail-default file (I prefer to use bounce)
To add the valias to the database table, I use this: (replacing mailboxname and example.com as appropriate)
Hopefully this helps someone else out there.
If I had more time, I'd look at patching dovecot to use the valias table. Maybe one day.
Reply | Permalink
Using dovecot-lda with vpopmail valias database table
Roberto Puzzanghera Michael Dick September 30, 2020 20:02
Hi Michael, thanks for your contribution, it's very much appreciated.
I think I am missing something on how things work in your configuration. You are using vdelivermail in your .qmail-default so you are giving up on sieve filters and vdelivermail can work well with valiases even without your hack... what I am missing?
Reply | Permalink
Using dovecot-lda with vpopmail valias database table
Michael Dick Roberto Puzzanghera October 3, 2020 11:17
Hi Robert
I was trying to show is that you can use the valias table from vpopmail and still make sieve filtering work, without having to set up any .qmail-alias files.
The existing instructions and comments suggest you had to choose one or the other.
Reply | Permalink
Using dovecot-lda with vpopmail valias database table
Roberto Puzzanghera Michael Dick October 3, 2020 11:27
I don't understand how you can have sieve working if you have vdelivermail in your .qmail-default
Reply | Permalink
Using dovecot-lda with vpopmail valias database table
Anonymous Roberto Puzzanghera October 3, 2020 11:58
Ah, that's the magic: I have an entry in the valias table for my actual mailbox name, that tells it to use dovecot's deliver program.
So:
Now, when an email for alias@example.com arrives, vdelivermail finds the alias michael@example.com and tells vdelivermail to deliver to that address. Vdelivermail then finds my alias for michael@example.com and calls dovecot's deliver to complete the delivery (which also processes the sieve rules).
Hopefully that's a bit clearer?
Michael
Reply | Permalink
Using dovecot-lda with vpopmail valias database table
Roberto Puzzanghera Anonymous October 3, 2020 13:41
That's clear now, even though this can be a solution suitable just for servers with a small bunch of users and for administrators who know what they are doing, otherwise patching qmailadmin and/or dovecot would be needed. Anyway it's good to know. Thank you
Reply | Permalink
vpopmail installation issue
Kenny Lee September 2, 2020 05:28
Hi Mr Roberto,
i am facing an issue while running this command "make install-strip", below is the message:
what shoud I do next? any settings need to be done in vpopmail folder?
Thank you
Regards, Kenny
Reply | Permalink
vpopmail installation issue
Roberto Puzzanghera Kenny Lee December 4, 2020 22:14
Today I released two patches, one for qmail and another for vpopmail, which solve these compilation breaks.
Reply | Permalink
vpopmail installation issue
Roberto Puzzanghera Kenny Lee September 2, 2020 08:58
No idea... any suspicious message from configure & make commands?
Reply | Permalink
vpopmail installation issue
Kenny Lee Roberto Puzzanghera September 2, 2020 10:32
Hi Mr Roberto,
my Linux is openSUSE Tumbleweed
mysql is MariaDB version 10.4.14
while running the configure command no issue, the summary as below:
but when i tried to run "make install-strip", the error message pop up :
do we need to define MYSQL data in vmysql.h?
thank you
Reply | Permalink
vpopmail installation issue
Roberto Puzzanghera Kenny Lee September 2, 2020 14:17
I didn't test it against mariadb-10.4, but I would try to declare with #ifndef those variables in mysql.h
Reply | Permalink
vpopmail installation issue
Kenny Lee Roberto Puzzanghera September 3, 2020 04:38
Hi Mr Roberto,
i deleted the vpopmail setup folder and extracted the zip file again, then this time i just run a "./configure" without any options and then "make install-strip", this time no error came out... then i tried to run again "./configure" with options then "make install-strip" .. no more error popup.
i continued your steps until netqmail setup which mean i done all the Patching steps. Now i hit another error, while i run "make setup check" in netqmail-1.06 folder, i got below error:
any idea?
Thank you
Reply | Permalink
vpopmail installation issue
Roberto Puzzanghera Kenny Lee September 8, 2020 23:06
I suppose you are compiling with gcc 10. Look at this https://gcc.gnu.org/gcc-10/porting_to.html
Reply | Permalink
vpopmail installation issue
Roberto Puzzanghera Kenny Lee September 3, 2020 09:11
It seems the same kind of error of vpopmail compilation.. did you try to download the sources, patching and compiling again?
Reply | Permalink
vpopmail installation issue
Kenny Lee Roberto Puzzanghera September 4, 2020 05:13
Hi Mr Roberto,
yes, i have redownloaded again the netqmail-1.06 file from your source and also the original source, then patch again.. but no luck.. both also same issue... what i have done, i just patch the file which only with smtp-auth, qmail-tls and force-tls. then it's works.
After that, when i tried to start Qmail and i found that the Daemontool was not start. for OpenSuse Tumbleweed, no more /etc/inittab use in the system, so what i have done, i need to ln that svscanboot file to /etc/rc.d/ then add it as auto start then completed Qmail Setup.
Thanks for the help.
Reply | Permalink
vpopmail installation issue
Roberto Puzzanghera Kenny Lee September 4, 2020 09:11
In the event of a systemd linux it is sufficient to start all services by rc.local, which should be created as a service in systemd
Reply | Permalink
vchkpw auth errors
Lawrence August 2, 2019 08:51
May need to fix suid permissions for vpopmail's vchkpw after compiling to avoid auth errors.
eg
Reply | Permalink
vchkpw auth errors
Roberto Puzzanghera Lawrence August 2, 2019 10:08
It wouldn't be better to run qmail-smtpd as vpopmail:vchkpw instead of letting everyone (not only qmail-smtpd) execute vchkpw with the owner's priviledges?
Reply | Permalink
libev missing
mizzio July 17, 2019 17:10
Hello Roberto,
I think I've found a small error in your guide: the latest available libev version is 4.27 and not 4.22: http://dist.schmorp.de/libev/libev-4.27.tar.gz
Ciao !
Reply | Permalink
valias doesn't work
Gabriel Torres June 19, 2019 15:05
Hello,
For some reason, vpopmail valias (i.e., storing valiases inside the MySQL database) doesn't work with chkuser, even if we configure both to do so. With valiases stored inside the database, vchkuser will reject emails sent to aliases (no mailbox). At least with me, chkuser only recognized valiases using the dot-qmail format. So, make sure to compile vpopmail with --disable-valias and --enable-qmail-ext as instructed, and remember that you will need to configure dot-qmail files for your aliases in the /home/vpopmail/domain/DOMAINNAME directory.
Reply | Permalink
Vusage configure error
Kevin Salt August 1, 2018 17:04
I get this message during the configure phase of vusage and can't progress from there:
So I am proceeding without implementing vusage (I also don't really acare about user quotas) so I hioe this will still work
Reply | Permalink
Vusage configure error
Stumpi Kevin Salt April 26, 2019 11:47
Same here, OS: Ubuntu 18.04
Reply | Permalink
Vusage configure error
Roberto Puzzanghera Kevin Salt August 2, 2018 08:36
look here (first item on google!) http://vchkpw.inter7.narkive.com/ftLwnnZq/vusaged-compile-error
Anyway everything will work even without vusaged
Reply | Permalink
Vusage configure error
GoofY Roberto Puzzanghera April 8, 2019 19:05
Which unfortunately doesn't provide a solution...
If anyone managed to workaround this issue plz share here
Reply | Permalink
Vusage configure error
Luca GoofY August 2, 2019 19:09
Try this:
Reply | Permalink
--disable-valias
Eric May 16, 2017 02:21
Hi Roberto,
As far I know and dovecot-lda is concerned it is not the presence of the configuration flag --enable-valias that hinders dovecot LDA from delivering to aliases it is the absence of a .qmail-'alias' alias file
Eric
Reply | Permalink
if the aliases are stored in
roberto puzzanghera Eric May 16, 2017 17:15
if the aliases are stored in the database, why the .qmail-alias is needed?
Reply | Permalink
valias
Eric roberto puzzanghera May 16, 2017 23:42
Hi Roberto,
I was only trying to point out that dovecot-lda is not affected by the --disable-valias/--enable-valias flags. On the other hand vdelivermail is affected and will use dot-qmail files in one case and the virtual alias database in the other case.
Dovecot-lda and --enable-valias can live quite happily together as long as you use dot-qmail files for you aliases.
Eric
Reply | Permalink
I agree. I will clarify this
roberto puzzanghera Eric May 17, 2017 17:23
I agree. I will clarify this in the lines above
Reply | Permalink
libev Version changed
Tiago Oliveira de Jesus November 9, 2016 18:41
Hi Roberto!
The libev 4.11 not exits, this changed to 4.22, at link http://dist.schmorp.de/libev/libev-4.22.tar.gz
Reply | Permalink
Permission issue on tcp.*
Wlad January 9, 2016 07:51
First of all, Roberto - THANK YOU for taking the time to put this resource together! I've formerly used JMS' tutorials etc but that was years ago. Once qmail etc is set up and working, you almost never have to touch it again except for security updates or maintenance so it's easy to forget the inner workings!
I have everything going so far but haven't been able to get passed the testing stages; When I telnet to 587, the logs for qmail-submission gives me this:
warning: dropping connection, unable to read /home/vpopmail/etc/tcp.submission.cdb: access denied
Can you please confirm what the perms are supposed to be? Right now they're owned by root at 644. Any pointers on this would be greatly appreciated!!
Reply | Permalink
Hi Wlad,
roberto puzzanghera Wlad January 9, 2016 11:11
Hi Wlad,
yes the priviledges are correct. It's strange because every user should be able to read that file..
Anyway, who is the user who runs qmail-smtpd and qmail-submission? If you migrated from JMS configuration you may have to check/adjust the priviledges of the ~vpopmail/ dir. In particular I suggest to check if the vpopmail:vchkpw userIDs are 89:89 (if I remember well JMS configuration uses non standard IDs for users..).
Reply | Permalink
Ok... I feel stupid.
Wlad roberto puzzanghera January 9, 2016 17:49
Ok... I feel stupid. ~vpopmail main dir was owned by root:root grrrr. Works now. ALL those dang hours - that happens when it's late, going on no sleep :) Again Roberto, thank you for this great guide! Lots of Coffee incoming to you haha
Reply | Permalink
ps -ef|grep qmail
Wlad roberto puzzanghera January 9, 2016 17:41
Wow long/ugly past - but all ownerships seem fine from looking at this and I'm perplexed. As for JMS, that was years ago on a separate server. I founds this guide last night and like the fact that things can be updated with the most current - in regards to paches etc. Versions of other sources:
And yes, id -g/-u vpopmail:vchkpw are both 89; I've turned every kind of permission based type of app off (apparmor for instance), every firewall etc etc with no change. I got no errors during compilation and did everything step by step and in order on this brand new server running ubuntu with multiple IPs. Speaking of IPs that was something I was going to ask about as well on how to specifically bind 587/25 to a specific IP but as long as MX records are set up properly there shouldn't be a need for that.
Roberto, sorry about the long post - just trying to figure this one out as everything seems to be running fine and like you said perms are right...
Reply | Permalink
Charset?
Anonymous July 3, 2014 09:24
Hello,
Some clients change their passwords with non-ascii char like "?š??žýáíé", but these characters are broken in MySQL as clear passwords. Any idea what charset set to Mysql db or how to set vpopmail to use UTF-8? Everythink else is in UTF...
Anyway if i do /home/vpopmail/bin/vuserinfo user@domain.cc clear password is ok, but in MySQL
SELECT pw_clear_passwd FROM vpopmail WHERE pw_name .... password is broken
Reply | Permalink
Hi, which tool are you using
roberto puzzanghera Anonymous July 3, 2014 19:42
Hi, which tool are you using to change the pwd? I can use UTF8 characters here when connecting via imap/roundcube pwd plugin, but if I try with qmailadmin I get an error...
PS: and I can retrieve the clear pwd with an SQL query
Reply | Permalink
Solved :)It was
Anonymous roberto puzzanghera July 4, 2014 09:23
Solved :)
It was misconfigured MySQL. I have no idea what charset did connection use when it was not configured but when I set this to my.cnf it start working correctly
Other problem is password from outlook... But I think there is no solution for clients using non UTF8 charset...
Reply | Permalink
Vpopmail configure
winnetou April 26, 2014 01:14
Hello!
While running ./configure on Gentoo systems (probably on other systems also) you have to add following options:
Vpopmail works also with MariaDB 5.5.37
BTW THX for great tutorial ;)
Best Regards
Winnetou
Reply | Permalink
Hello Winnetou This
roberto puzzanghera winnetou April 26, 2014 09:56
Hello Winnetou
This is the default location for mysql and mariadb, and I suppose that normally you don't even need to add those options, as the library will be automatically found. I just added them for those (like me) who compile from source or don't use the package provided by their own distro
Reply | Permalink
Hello! I'm aware that
winnetou roberto puzzanghera April 26, 2014 10:28
Hello!
I'm aware that those paths are default and ./configure should find them, but it didn't, that's why I decided to post a comment ;)
When I run ./configure without those 2 optins it failed. I was installing qmail and vpopmail on freshly installed Gentoo
Reply | Permalink
If I understand well,
roberto puzzanghera winnetou April 26, 2014 10:42
If I understand well, omitting those two options gets vpopmail not to find the libraries?
Anyway as soon as possible I will add a clarification on the purpose
Reply | Permalink
I am installing vpopmail and
Anonymous November 11, 2013 07:13
I am installing vpopmail and vusaged on CentOS release 6.4 (Final)
but i encountered the error on vusaged.
What is the problem? I am googling bu i couldn't found the solution.
please help me!!
Reply | Permalink
can you dostrace
roberto puzzanghera Anonymous November 11, 2013 13:25
can you do
and see what happens?
Reply | Permalink
it works now
Anonymous roberto puzzanghera January 21, 2014 05:22
It works now. I uninstalled the libev source then installed libev using yum rpmforge repository.
Sorry for the late reply. I totally forgot about this. I gave up last time and set up qmailtoaster on Centos 6 which was successful.
Now, I am experimenting qmail again using this setup. :)
Reply | Permalink