Robert Vazan <robertvazan(_at_)privateweb(_dot_)sk> writes:
On Wed, 09 Jul 2003 18:04:43 +0200 Matthias Andree
<ma(_at_)dt(_dot_)e-technik(_dot_)uni-dortmund(_dot_)de> wrote:
If you're not using multidrop, you can use the mda option of fetchmail
to avoid MasqMail and hand the mail off to procmail directly.
I am using it now and it works. Thanks. It might still be nice feature
to handle such situations without extra local setup.
The question is: is this a "feature"?
Normally, the Return-Path: header is added by the software that delivers
the mail into your mailbox, apparently Exchange in your setup.
It also appears as though the Return-Path: header was incomplete or
corrupt, and from your report, Exchange is the suspect.
Send yourself a mail with
( echo "subject: test" ; echo ; date ) | /usr/sbin/sendmail -f '<>' YOURADDRESS
and check if that triggers the problem.
I'm getting timeouts on these, so I can't make a more qualified
suggestion than above.
Sorry, broken router and no redundancy... It should work now.
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?
--
Matthias Andree