davew
Fri, 25 Apr 2008 14:47:57 -0700
>
>>
>> Okay, basically one specific person who sends email to our server enjoys
>>using periods to break up logical sections of his emails.. which for some
>>reason is making citadel barf on them.. Are incoming emails escaped so those
>>.'s don't get misinterpreted?
>
>
>We are unaware of any such problems. Would it be possible for you to send a
>copy of one such mail to me at [EMAIL PROTECTED] so we can test to
>see if we can reproduce the problem.
>
>
Fusion,
Thanks for the mail you sent me on this issue. I'm appending the relevant
part of it here for clarity.
Sending an email that looks something like this:
text
<period>
some more text
For all folks that do not know this is a very very VERY VERY bad thing to let
your users do. Users that construct emails in this manner deserve "to die in
a car fire" to quote a regular poster here on Uncensored 8-)
Traditionally, sending a <period> on a line of its own is the way to mark the
end of an email. Even today this remains as part of the standard protocol
Some mail servers may handle this in the manner the user expects but most
will adhere strictly to the protocol and consider the <period> on a line of
its own to signal the end of the message at which point the mail server will
stop receiving that message and any text that follow will be rejected.
Fusion, you should refer your user to RFC821 which clearly specifies this
behaviour.
RFC821 also describes a method of working around this problem for mail
servers and clients but both parts need to cooperate. The mail client has
detect this situation and modify the message for transmission and the server
has to detect the modified message and alter it back on completion of
reception.
What mail client is your user using?
Does this problem only occur when he sends to a Citadel server or does it
occur when the user sends through a Citadel server?