dcinege@??? said:
} Should exim (the MTA) be doing this with a POP3 send? Should the
} popper be doing the hacking the CRLF? (the newest qpopper doesn't. I
} don't think cuci-pop did either.) Or is this just a downfall of
} sending with POP3?
I guess there are spec problems here - there isn't an RFC that I know of
for pop send although I know a couple of versions do this (cucipop is
*not* one of them).
Both SMTP & POP specify that text transfer should be done in canonical
form - ie line endings are \r\n - so the transfers appear to be being done
right. However the pop daemon should set the line ends right for the
local system if doing local mail submission.... and it looks like things
are falling apart here. I guess that sendmail is always stripping \r`s
and so things just work.
Would it be possible for exim to have a (selectable by config) mechanism
for auto-magically detecting this sort of nasty abuse. The easy thing is
to check the headers supplied - unlike the body they do no suffer from
possible binary-isms - and see if they have \r\n line ends. However its
probably just much better to recompile your pop daemon, setting the
parameters to exim/sendmail to add -dropcr
Nigel.
--
[ Nigel.Metheringham@??? - Systems Software Engineer ]
[ Tel : +44 113 251 6012 Fax : +44 113 234 6065 ]
[ Real life is but a pale imitation of a Dilbert strip ]
--
*** Exim information can be found at
http://www.exim.org/ ***
