* Asif Iqbal <vad...@gmail.com>: > Currently our qmail uses QMAILQUEUE, qmail-scanner, clamd, > spamassassin, rbldnsd, greylite, qmail-pop, qmail-ldap, virtuals and > ezmlm. > (I hope I did not miss anything)
Here's the typical way most people go: qmail -> postfix <http://www.postfix.org/BASIC_CONFIGURATION_README.html> qmail-scanner -> amavisd-new <http://www.ijs.si/software/amavisd/README.postfix.html> clamd -> integrated in amavisd-new spamassassin -> integrated in amavisd-new rbldnsd -> integral part of postfix greylite -> postgrey <http://postgrey.schweikert.ch/> qmail-pop -> dovecot <http://wiki.dovecot.org/MailServerOverview> qmail-ldap -> postfix <http://www.postfix.org/LDAP_README.html> virtuals -> postfix <http://www.postfix.org/VIRTUAL_README.html> You probably want to use Dovecot's "deliver" program as LDA in conjunction with virtual domain hosting ezmlm -> use with Postfix or replace with mailman > I am guessing I need to install postfix as the front-end, will be > installed on a separate new box. I suggest to replace qmail with Postfix and not make things more complicated adding another MTA. > Then use the qmail, currently running on the existing system, as the back-end. > Hoping that will ease the migration, however not exactly sure how to > do it, quite yet :-). Setup Postfix in parallel. Test locally. Ask people on this list if you don't understand the documentation or how to test. Then sync messages from old system to new one and retire old one. > Then eventually expire qmail. Not quite sure how to do that either, but I > think have to do some MX tricks on that. Leave MX and give new machine old (and valid MX) IP address. p...@rick -- All technical questions asked privately will be automatically answered on the list and archived for public access unless privacy is explicitely required and justified. saslfinger (debugging SMTP AUTH): <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/>
