Michael Neuffer wrote: > Hi Thomas, > > thank you for reactng so fast > > Thomas Goirand wrote: >> Postfix and dkimproxy are 2 SMTP servers. I really don't think that one >> needs the other to be able to start. I don't understand at all why you >> are saying that postfix needs to be started first. Can you make it more >> clear? > > Sure, when the system comes up dkimproxy is started first > since both are S20 and d<p and because in the dependency definitions > of their /etc/init.d files there is no dependency on each other. > > If you start postfix first, everything is fine. > > Apr 11 17:48:54 server postfix/master[6470]: fatal: bind 127.0.0.1 port > 10026: Address already in use
This shows that postfix can't bind on the port 10026. This is also the port that uses dkimproxy by default, and this is why it works when you start postfix first. But that doesn't mean that your configuration is working correctly! See this: [EMAIL PROTECTED]:x300>_ /etc/dkimproxy# more dkimproxy_in.conf # specify what address/port DKIMproxy should listen on listen 127.0.0.1:10026 # specify what address/port DKIMproxy forwards mail to relay 127.0.0.1:10024 When you have this: -------------excerpt from master.cf------------------------- ## For injecting mail back into postfix from the filter 127.0.0.1:10026 inet n - n - 16 smtpd which is conflicting. To me, the mistake is in the README.Debian of dkimproxy and in your configuration of the software, NOT in the priority when starting the daemons. I have found that our README.Debian IS wrong and should be updated. I will update it. Can you try to make it so postfix binds on port 10029 if using amavis, or 10024 if not using it? Do you agree that I can close this bug? Thomas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
