15 messages in net.sourceforge.lists.courier-users[courier-users] Re: What does this me...
FromSent OnAttachments
Adam ShermanMar 24, 2001 1:59 pm 
Adam ShermanMar 24, 2001 5:25 pm 
Adam ShermanMar 24, 2001 5:57 pm 
Adam ShermanMar 24, 2001 7:59 pm 
Adam ShermanMar 25, 2001 11:07 am 
Adam ShermanMar 25, 2001 12:40 pm 
Adam ShermanMar 25, 2001 1:40 pm 
Yuan P LiApr 1, 2001 9:13 am 
Yuan P LiApr 1, 2001 3:43 pm 
Sam VarshavchikApr 1, 2001 5:04 pm 
Yuan P LiApr 1, 2001 5:34 pm 
Yuan P LiApr 1, 2001 5:49 pm 
Sam VarshavchikApr 1, 2001 5:58 pm 
Sam VarshavchikApr 1, 2001 6:17 pm 
Yuan P LiApr 1, 2001 7:46 pm 
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: What does this mean and how can we fix it?Actions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Apr 1, 2001 6:17:41 pm
List:net.sourceforge.lists.courier-users

Yuan P Li writes:

Hi,

Is there anyway to make webmail treat all messages as Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit

The problem is that when I put us-ascii in the CHARSET file, I can no longer send messages. I get an error 511 Headers specify no recipents (Does this make sense at all?)

No. It doesn't make sense at all. When you start messing around with things that you don't have a clear understanding how they work, expect bizarre things like that to happen.

After examining some mail systems that work for different languages (with changing of browser encoding on the fly), I saw the above header in most messages.

Which means that those mail systems are broken. The us-ascii character set covers only the low-end character range of 0 through 127. 128 and above are undefined in us-ascii. Anything that generates high-8bit text, in us-ascii character set, is broken.

-- Sam