My mail server emerged the latest postfix ebuild last night and it apparently did not complete the proxymap configuration properly and caused numerous proxymap errors. (Something like "could not access /var/spool/postfix/private/proxymap, File or Directory does not exist.") This prevented mail from coming in. Fortunately, I caught this rather quickly and after trying a postfix reload, etc., unmerged it, backed up and deleted the latest ebuild file, and emerged back to the old version, which corrected the problem. I'll attach the emerge output that I write to my emerge world file on a nightly (cron) basis if I can figure out how. If I can't attach it, please let me know you want it and I'll email it to you. The short version is I didn't see any errors. Here's the relevant section from the Release notes: "Version 2.0.1 introduces the proxymap service for centralized table lookup. The upgrade procedure adds the proxymap service to the master.cf file. If you see errors about problems contacting the proxymap service, then you did not properly upgrade Postfix." The strange thing is that I believe (based on the ebuilds I have) that I already had 2.0.1 operating without trouble and 2.0.2-r1 broke. I'm not sure why. -rw-r--r-- 1 root root 11132 Jan 24 00:52 ChangeLog drwxr-xr-x 3 root root 4096 Jan 19 18:54 files -rw-r--r-- 1 root root 5179 Dec 8 22:33 postfix-1.1.11-r5.ebuild -rw-r--r-- 1 root root 4939 Dec 8 22:33 postfix-1.1.11.20020917-r1.ebuild -rw-r--r-- 1 root root 4924 Dec 8 22:33 postfix-1.1.11.20020917.ebuild -rw-r--r-- 1 root root 4105 Dec 23 14:54 postfix-2.0.0.ebuild -rw-r--r-- 1 root root 5090 Jan 24 00:52 postfix-2.0.2-r1.ebuild -rw-r--r-- 1 root root 5071 Jan 19 18:23 postfix-2.0.2.ebuild Perhaps it wasn't working since Jan 19? Perhaps, but at least some of the mail got through. Unfortunately, I only have .5MB of mail logs (increasing that now!) and that only covers about four or five hours, but I do know that at least some of the mail had been arriving until this upgrade last night. Perhaps we should remask this patch until later? Thanks for all your help!! -Jamie
Created attachment 7616 [details] This is the log of the emerge that I had cron`ed (emerge world) last night. It covers Postfix 2.0.2-r1 and SASL2.
postfix-2.0.3 has been added to portage. Please test this new ebuild and let me know if it fixes your stated problem.
Please also make sure that you have updated your main.cf/master.cf.... there have been some significant changes since 1.1.11.20020917... I recorded all my previous changes and applied them to the new config file and everything has been working great with both 2.0.2 and 2.0.3... although there is a mention in the postfix ChangeLog between 2.0.2 and 2.0.3 about a proxymap related fix...
postfix-2.0.3 has been marked stable in portage.
db fix
This bug would be better cured by changing the instruction 'run /etc/postfix/post-install upgrade-permissions' to ' ... post-install upgrade-source' as this automatically adds the relevant entry to the config files. I for one didn't spot this difference when doing an etc-update and have spent a morning trying to figure out what's wrong with postfix.
