Robert Vazan <robertvazan(_at_)privateweb(_dot_)sk> writes:
I tried to send myself such broken Return-Path by telneting to Smtp
server. I have been successful. Exchange is not the (only) problem.
Well, are we sure the original envelope sender was null or <> when the
Return-Path runs into the Received header? Or does it take characters
with high bit set such as äöü߀© or something to get such a broken
header?
The question is: can fetchmail recover from such a condition at all, or
has information been lost? In the latter case, Exchange must be fixed to
ALWAYS drop a syntactically correct Return-Path: header. It carries
ESSENTIAL information.
I tried some variations of this and none of them caused generation of
Return-Path.
But you are getting a Return-Path: for regular mail, i. e. after
MAIL FROM: <robertvazan(_at_)privateweb(_dot_)sk>
RCPT TO: <strange(_dot_)exch(_at_)ang(_dot_)example(_dot_)org>
DATA
blah
.
?
Is this message still on your POP3 or IMAP server (Exchange, I presume)?
If so, can you obtain it verbatim by telnetting into the server and
retrieving the message manually?
The file on website is exact original that I got with TOP 1 0 command.
Excellent.
Unfortunately, I don't have the original message in mailbox anymore and
As you've presented the original headers, that's OK. Can you leave the
example files available for a while?
--
Matthias Andree