>> It's not a bug.  Both are perfectly valid, and completely equivalent,
>> headers.
>>
>Nice to read this!
>Just for interrest, could you explaine why courier rewrites the header ?
>
>The reason I ask this are that one Provider will not accept such a
>header an don't pass on the mail to the recipient.
>
>Could you please point me to the relevant RFC to show him that's an
>valid header.
>

http://docs.perimeter.co.za/RFC/rfc822.txt  (My Copy - you may validate it
anywhere you choose :)

Look for section "B.1.  SYNTAX" .  It explains that field body may consist
of any text separated by white space and CRLF in any arbitrary combination
(well, almost any).

---
Regards,
Patrick O'Reilly.
    ___        _            __
   / _ )__ __ (_)_ __ ___ _/ /____ __
  / __/ -_) _) /  ~  ) -_), ,-/ -_) _)
 /_/  \__/_//_/_/~/_/\__/ \__/\__/_/
    http://www.perimeter.co.za




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to