| PLEX86 | ||
|
RFC2822 StandardClark Zahn said the following, on 09-07-05 23:54: I don't have any specific suggestions. As I'm sure you know, you are using a very old version of Netscape, and RFC 2822 does introduce some changes. Here is the summary of changes from that document: It's solved Walter, big thank you for your response. Actually, I got the things right on Friday but it got late and I scheduled calling off the help request for... === Appendix B. Differences from earlier standards This appendix contains a list of changes that have been made in the Internet Message Format from earlier standards, specifically RFC822 and STD3. Items marked with an asterisk (*) below are items which appear in section 4 of this document and therefore can no longer be generated. 1. Period allowed in obsolete form of phrase. 2. ABNF moved out of document to RFC2234. 3. Four or more digits allowed for year. 4. Header field ordering (and lack thereof) made explicit. 5. Encrypted header field removed. 6. Received syntax loosened to allow any token-value pair. 7. Specifically allow and give meaning to "-0000" time zone. 8. Folding white space is not allowed between every token. 9. Requirement for destinations removed. 10. Forwarding and resending redefined. 11. Extension header fields no longer specifically called out. 12. ASCII 0 (null) removed.* 13. Folding continuation lines cannot contain only white space.* 14. Free insertion of comments not allowed in date.* 15. Non-numeric time zones not allowed.* 16. Two digit years not allowed.* 17. Three digit years interpreted, but not allowed for generation. 18. Routes in addresses not allowed.* 19. CFWS within local-parts and domains not allowed.* 20. Empty members of address lists not allowed.* 21. Folding white space between field name and colon not allowed.* 22. Comments between field name and colon not allowed. 23. Tightened syntax of in-reply-to and references.* 24. CFWS within msg-id not allowed.* 25. Tightened semantics of resent fields as informational only. 26. Resent-Reply-To not allowed.* 27. No multiple occurrences of fields (except resent and received).* 28. Free CR and LF not allowed.* 29. Routes in return path not allowed.* 30. Line length limits specified. 31. Bcc more clearly specified. === The complete document is available here: It's hard to make any specific suggestions without being able to see a message that Netscape generates, but perhaps this will give you some leads. Please help. How to revive a broken raid1 OK. It's a bit complicated. I've got a server with a raids 1 on two discs (sda & sdb). There are 8 md devices on them. One of the discs (sda) is failing... (Incidentally, if you would consider changing mail apps, Mozilla Thunderbird is a descendant, in some sense, of the Netscape mail app. To the extent I can remember, it works in a pretty similar way.) -- Rich Gibbs "If you find yourself in a hole, stop digging." (Will Rogers)
|
||||
Please help. How to revive a broken raid1 Linux groups from Newsgroups The #1 Usenet Provider on the Internet
|
||||