I'm seeing this in Fedora 10. postfix-2.5.6-1.fc10.i386 The problem is that /var/spool/postfix/public/pickup does not exist Running: mkfifo /var/spool/postfix/public/pickup fixes the problem. Original bug report listed below: +++ This bug was initially created as a clone of Bug #157811 +++ From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050509 Fedora/1.0.3-5 Firefox/1.0.3 Description of problem: [djo@peanut ~]$ mail djo Subject: test message This is a test. Cc: [djo@peanut ~]$ postdrop: warning: unable to look up public/pickup: No such file or directory (and the mail is never delivered) [root@peanut djo]# cat /var/log/maillog May 15 09:04:22 peanut postfix/postdrop[19447]: warning: unable to look up public/pickup: No such file or directory May 16 02:26:54 peanut postfix/postdrop[10125]: warning: unable to look up public/pickup: No such file or directory May 16 02:27:36 peanut postfix/postdrop[10138]: warning: unable to look up public/pickup: No such file or directory May 16 02:28:19 peanut postfix/postdrop[10151]: warning: unable to look up public/pickup: No such file or directory May 16 02:28:38 peanut postfix/postdrop[10173]: warning: unable to look up public/pickup: No such file or directory May 16 02:30:50 peanut postfix/postdrop[10242]: warning: unable to look up public/pickup: No such file or directory May 16 02:55:10 peanut postfix/postdrop[11116]: warning: unable to look up public/pickup: No such file or directory [root@peanut djo]# Version-Release number of selected component (if applicable): postfix-2.2.2-2 How reproducible: Always Steps to Reproduce: Exact commands given in Description. When I installed FC4-test3, I explicitly removed exim and added Postfix in the installer. I did *not* install exim, then remove it and install Postfix, or install both and then remove exim or anything like that. Actual Results: See above. Note also that the sent email is not bounced (the bounce couldn't be delivered) so the email is just lost. Expected Results: The mail should have been delivered. Additional info: --- Additional comment from twoerner on 2005-06-21 06:14:30 EDT --- Please run a rpm install test of the postfix package with "rpm -V postfix". If there are no errors (output), then check if postfix is activated with "alternatives --config mta". --- Additional comment from twoerner on 2005-09-30 12:06:48 EDT --- Closing due to user inactivity as NOTABUG.
This message is a reminder that Fedora 10 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 10. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '10'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 10's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 10 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.