Matthias Andree <ma(_at_)dt(_dot_)e-technik(_dot_)uni-dortmund(_dot_)de> wrote:
Mike Yates <hctef(_at_)fonehelp(_dot_)co(_dot_)uk> writes:
I think the reason is that long "Received:" lines arrive already
"wrapped" by Microshit Exdrain at the ISP, so that
"for <localuser(_at_)localdomain>" appears on a different line.
Has anyone a fix for this?
Why would one be needed? Is the folding of the Received: line actually
the cause?
From my tests it seems to be.
I haven't analysed the source of fetchmail (yet) so perhaps you could
save me time by telling me,
if you happen to know, whether header lines are parsed up to the next LF
and/or CR?
Would the option "stripper" affect the email body as well as the head?
In this case, the header lines have been broken with 0D0A09 sequences to
indent the wrap.
Perhaps parsing up to another header-line ( defined as a second argument
) would work?
I am trying to persuade the ISP (Blueyonder Workwise) to use
"X-Envelope-to:" but they refered me to
rockcliffe.com who said that "Rockcliffe Mailsite" is NOT configurable
to add "X-envelope-to:" lines.
byworkwise.co.uk (formerly cobweb.co.uk) say they have plans to migrate
from the Rockcliffe MTA but cannot say when.
Rockcliffe blame the line-wrapping on MsExdrain at byworkwise.co.uk
Yes, Rob MacGregor, I am using multidrop, else it WOULD be irrelevant.
I would like to know if others have succeeeded in capturing "bcc"
addresses for correct internal distribution
from various ISPs with fetchmail.
--
Have fun,
Mike
--
http://fonehelp.co.uk - PC support, no fix, no fee!