It turns out the previous admin neglected to include a section in master.cf
to indicate the relay port that was specified in the dkimproxy_in.conf file.
Adding that section cured the problem. Apparently the old system running on
lenny somehow tolerates the omission without causing any problems.
Very good, then. Thanks!
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-can-t-send-from-localhost-tp88417p88458.html
Sent from the Postfix Users mailing list archive at Nabble.com.
On 1/24/2017 1:03 PM, bithead wrote:
> Scott - can you (or anyone else) shed some light on why there would be a DKIM
> content filter on the pickup process? Nothing I've read about DKIM so far
> has ever shown an example of why one might do that. As previously
> indicated, I've inherited this ser
Scott - can you (or anyone else) shed some light on why there would be a DKIM
content filter on the pickup process? Nothing I've read about DKIM so far
has ever shown an example of why one might do that. As previously
indicated, I've inherited this server, so am trying to back-learn the
previous
Thank you Scott. Yes, I meant 2.11.3-1 for the postfix version. Per your
suggestion, I've posted this in the Debian forums as well.
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Postfix-can-t-send-from-localhost-tp88417p88424.html
Sent from the Postfix Users mailing li
On Monday, January 23, 2017 11:52:09 AM bithead wrote:
...
> postfix 2.1.3-1
...
OP meant 2.11.3-1.
> ... replace an old postfix server running on Debian Lenny ...
Which is ancient.
The Debian dkimproxy package no longer provides some of the helper scripts it
once did. Instead of trying to fi
I have a newly installed Debian 8 server, created to replace an old postfix
server running on Debian Lenny. I've installed and reconfigured as needed
the following newer packages on the new server:
postfix 2.1.3-1
dovecot 2.2.13-12~deb8u1
amavisd-new 2.10.1-2~deb8u1
spamassasin 3.4.0-6
clamav 0.99
