Hmmm I have tried to send this a couple times and it keeps bouncing back to me. Not sure why. Sorry if you are getting this multiple times. -Geoff
WOW! I upgraded to 2.6.5 and everything just sorta started working. haha I have to admit that I was using 2.3 purely because that is the version captured in the repositories for CentOS. But after using the upgrade from source, it just... works. I am still off a couple versions for amavisd but the fact that everything started working makes me think I should burn this server to the ground and build each component from scratch to make sure I have the latest. Repositories are good, but they do have their drawbacks. and sorry about not including the postconf -n. I read that in the subscription email and completely forgot. Thanks for the advice! -Geoff -----Original Message----- From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org] On Behalf Of Noel Jones Sent: Tuesday, September 22, 2009 12:55 PM To: postfix-users@postfix.org Subject: Re: can't get postfix to work with amavisd-new On 9/22/2009 2:08 PM, Geoff Sweet wrote: > Greetings everyone, > I'm transitioning a lot of my mail servers from Qmail to Postfix and > thus far it has gone very well. I got Postfix 2.3 (from the CentOS > 5.3) up and running in a flash and then even got it all running with > MySQL virtual users! My hats off to the Postfix devs. > > However now I want to incorporate a few things like ClamAV, and > Spamassassin and it appears that Amavisd-new is the preferred way to > do it. I installed it out of the RPMForge repositories and > Spamassassin, ClamAV, and amavisd-new all seem to be running > correctly. If I telnet to port 10024 on localhost I can successfully > see the Amavisd-new prompts and commands. Welcome to postfix! Yes, amavisd-new is a popular and reliable way to integrate SpamAssassin and clamav with postfix. Be aware that postfix 2.3 is getting rather long in the tooth. The current patchlevel for the 2.3 series is 2.3.19. While postfix 2.3.19 is quite reliable, it's lacking tons of useful features introduced in newer versions. I think it's better to build a new server with the current stable version rather than something already outdated; the current postfix stable version is 2.6.5. > > When I startup Postfix and attempt to send mail through it, I get this > error in the maillog: > > Sep 18 17:02:03 mail postfix/qmgr[16473]: warning: connect to transport > scan: Connection refused Looks like a leftover from a previous configuration when you were using content_filter = scan:... Fix this by requeueing all mail with postsuper -r ALL > Sep 18 17:02:03 mail postfix/cleanup[16474]: fatal: unsupported > dictionary type: mysql Looks as if postfix doesn't have mysql support compiled in. type "postconf -m" to see what map types your version of postfix supports. > Sep 18 17:02:40 mail postfix/smtpd[16475]: warning: dict_nis_init: NIS > domain name not set - NIS lookups disabled I assume you don't use NIS. You can get rid of this harmless warning by setting in main.cf: alias_maps = hash:/etc/aliases > Below are my main.cf and master.cf. As I am relatively new to this we strongly prefer "postconf -n" output as explained in the list welcome message. If you have more questions, see: http://www.postfix.org/DEBUG_README.html#mail -- Noel Jones
