On 7/12/14, 10:22 AM, A. Schulze wrote:
Hello,
it may happen that postfix announce 8BITMIME SMTP extension and
clients use that by submitting messages
it may happen postfix has to relay such messages to a legacy server
not supporting that extension.
in this case postfix will recode the message.
it that situation visible in the logfile?
I like to do some statistical analyses how often my MTAs will destroy
DKIM signatures for example.
Are there other situations postfix has to recode a message?
Thanks & nice weekend
Andreas
Victor has indicated that you can't tell from the logs that this has
happened, but here are some ideas of how to get around the problem.
IF you can tell by the recipient domain that it might need to go to the
legacy server, point those domains to a different MTA that doesn't
promise 8BIT compatibility so the send will do the conversion to 7BIT,
and hopefully sign after they do the conversion.
Verify the signature before conversion, and then add a header that you
sign to indicate that you have verified the sender. Hopefully you can
tell the legacy server that it can trust you on this.
Add a header to the message to indicate that postfix recoded the message
and have the legacy server (or whatever) undo the encoding before
checking the signature.
--
Richard Damon
