MTA Woes: Postfix, Dovecot, MySQL...


I was hoping to clarify a few matters regarding virtualmin and its capacity to manage users via mysql. Are there any limitations about the way I setup my mail server to ensure virtualmin compatibility? I’m still in the process of configuring my mta, but already Virtualmin is seeming overly finicky with some of my configuration options.

I’m currently using Postfix, Dovecot, MySQL, SASL2 and ClamAV. I intend on using Maildirs, but I ran into some problems along the way. Virtualmin complains that “No virtual domains file was found in your Postfix configuration. Maybe no virtual domain map has been defined.” If I check postfix’ virtual domain setup, the “Domain mapping lookup tables” is set to “proxy:mysql:/etc/postfix/” and “Domains to perform virtual mapping for” is set to look “From domain mapping tables”. Is there another reason why this error might surface?



I’ve got my MTA work’n now, least partially, but still I can’t get virtualmin to recognize the virtual domains map. Why isn’t virtualmin satisfied with:

"Domain mapping lookup tables: proxy:mysql:/etc/postfix/"


Hey Tony,

Virtualmin isn’t satisfied with that because it doesn’t know how to deal with mail users stored in MySQL. We’ve simply never had a request for it, and I’m not sure if it’s trivial to implement. LDAP users are supported with Postfix (though not the type of LDAP mailbox that is divorced from normal user accounts that you’re trying to use here–there are a lot of things that Virtualmin wants to configure for you that can only be done for real system users), if you want users in a remote database rather than a local bdb.

We are probably going to implement Postfix LDAP mailbox-only accounts in the month or so, which will be similar to the current QMail implementation, which would then probably translate easily into a MySQL mailbox user account type…but it is unlikely we will ever address MySQL mailboxes. We have had quite a few requests for LDAP mailbox-only accounts, and so we will implement it–though I’m exceedingly skeptical of the alleged benefits (that same skepticism applies to MySQL, probably moreso), and it will never be the default.

Mind if I ask why you’ve chosen MySQL over LDAP or a simple local table? Seems like LDAP provides all of the heavy-duty stuff (easy/efficient replication, good user management tools, well-defined schema standards, option to use it with both real and mailbox only users, etc.), to a greater degree than MySQL, and local tables provide better performance and simpler deployments than either LDAP or MySQL. Just a humble opinion, and I’d certainly like to expand my knowledge if there’s some compelling reason for using MySQL for this purpose.

Hi Joe,

How’s the LDAP / Postfix coming? It would be so nice to have this feature, on so many levels! =)