22 messages in net.sourceforge.lists.courier-users[courier-users] Re: remedy for non us...
FromSent OnAttachments
Alex TitovOct 2, 2001 1:20 pm 
Bill MichellOct 2, 2001 4:14 pm 
Alex TitovOct 3, 2001 3:15 am 
Bill MichellOct 3, 2001 4:43 am 
Sam VarshavchikOct 3, 2001 4:57 am 
Bill MichellOct 3, 2001 5:41 am 
Alex TitovOct 3, 2001 8:34 am 
Bill MichellOct 3, 2001 9:19 am 
Andrew SnyderOct 3, 2001 10:45 am 
Alex TitovOct 3, 2001 2:12 pm 
Sam VarshavchikOct 3, 2001 3:42 pm 
Sam VarshavchikOct 3, 2001 3:43 pm 
Bill MichellOct 4, 2001 2:33 am 
Alex TitovOct 5, 2001 4:06 am 
Bill MichellOct 5, 2001 4:45 am 
Sam VarshavchikOct 5, 2001 6:08 am 
Sam VarshavchikOct 5, 2001 6:09 am 
Bill MichellOct 5, 2001 6:36 am 
Sam VarshavchikOct 5, 2001 6:52 am 
Bill MichellOct 5, 2001 7:14 am 
Sam VarshavchikOct 5, 2001 7:29 am 
Alex TitovOct 5, 2001 8:00 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: remedy for non us-ascii charasters in headersActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Oct 5, 2001 6:52:43 am
List:net.sourceforge.lists.courier-users

Bill Michell writes:

Sam Varshavchik writes:

Bill Michell writes:

Encode the name FIRST, before you stick it into any header. Problem solved.

The application is written in java and is supplied/maintained by a third party. Is there a library or utility I can point them to?

Point them to RFC 2047, and explain to them that their software generates mail that violates several standards-track RFCs. That's really all that you need to do. To head off the predictable reply, point out that although in the past other mail software were fairly tolerant of protocol violations, as exhibited by their software, the trend in the recent times tends to go in the opposite way. Mentioning the fact that their mail cannot be read by Outlook Express in IMAP mode might get their attention.

-- Sam