|Morten Wartou||Jan 3, 2002 5:59 am|
|Toni Mattila||Jan 3, 2002 6:21 am|
|Morten Wartou||Jan 3, 2002 6:32 am|
|Toni Mattila||Jan 3, 2002 6:34 am|
|Sam Varshavchik||Jan 3, 2002 2:39 pm|
|Sam Varshavchik||Jan 3, 2002 2:39 pm|
|Morten Wartou||Jan 3, 2002 3:22 pm|
|Morten Wartou||Jan 3, 2002 3:23 pm|
|Sam Varshavchik||Jan 3, 2002 3:30 pm|
|Sam Varshavchik||Jan 3, 2002 3:31 pm|
|David||Jan 3, 2002 3:32 pm|
|Juha Saarinen||Jan 3, 2002 3:37 pm|
|Morten Wartou||Jan 3, 2002 4:11 pm|
|Juha Saarinen||Jan 3, 2002 4:15 pm|
|Joe Croft||Jan 3, 2002 5:20 pm|
|Michael Carmack||Jan 3, 2002 5:44 pm|
|Greg Owen||Jan 3, 2002 6:29 pm|
|Peter C. Norton||Jan 3, 2002 7:13 pm|
|Michael Carmack||Jan 3, 2002 7:48 pm|
|Sam Varshavchik||Jan 3, 2002 8:48 pm|
|Morten Wartou||Jan 4, 2002 12:32 am|
|Zon Hisham Z.Abidin||Jan 4, 2002 12:57 am|
|Francois PHILIPPO||Jan 4, 2002 1:27 am|
|MH - Entwicklung||Jan 4, 2002 3:05 am|
|Sam Varshavchik||Jan 4, 2002 5:09 am|
|Sam Varshavchik||Jan 4, 2002 5:10 am|
|Roger Thomas||Jan 4, 2002 5:58 am|
|Morten Wartou||Jan 4, 2002 6:13 am|
|MH - Entwicklung||Jan 4, 2002 9:26 am|
|Tony Kueh||Jan 4, 2002 11:05 am|
|Robert L Mathews||Jan 4, 2002 11:09 am|
|Peter C. Norton||Jan 4, 2002 11:51 am|
|Sam Varshavchik||Jan 4, 2002 6:20 pm|
|Sam Varshavchik||Jan 4, 2002 6:21 pm|
|MH - Entwicklung||Jan 7, 2002 1:13 am|
|Subject:||Re: [courier-users] Re: Suggestion about the RFC Checking of 8-bit-headers|
|From:||Peter C. Norton (spac...@lenin.nu)|
|Date:||Jan 4, 2002 11:51:39 am|
On Fri, Jan 04, 2002 at 01:05:07PM -0600, Tony Kueh wrote:
WRONG. Do we really expect everyone to understand RFCs and 7-bit vs 8-bit MIME headers?
Yes. Lets examine where email and smtp is taking us. Here in NYC when 9/11 hit us, email was how people got in touch with each other. The last earthquake in seattle? Email was the fastest way to get in touch with anyone. In the first world, email is becoming part of the infrastructure that should work.
If some silly idiot is too stupid to fix an application because they don't understand it, the rest of the world shouldn't be expected to break itself for them, especially since people and companies rely on email working.
Let me propose a contrived metaphor. If someone started feeding power back into the grid 1/4 cycle out of phase, would you agree that that power companies should fix their infrastructure to accept any phase, and fequency, AC and DC, or would you suggest that they get an injunction put on such a dangerous individual? Email doesn't have the disasterous consequences that unbalencing the power grid does, but the same basic question is there.
Extending that question to other companies who have to cooperate with others, like one that builds traffic lights, or plumbing, or anything else that becomes infrastructure, who in their right mind would tolerate it? Why should anyone have the luxury of not understanding what they're working with?
Don't get me wrong - its perfectly normal to not understand something because you just don't know, but if someone tells you that you're causing problems and they still don't get it, then they are a hazard because the next thing you know they'll be doing something else foolish. Has anyone else here worked with FirstClass or QuickMail gateways? I don't want to go back to the days where every other day some poor guy would run a $50 gui-based email server written by someone who didn't read relevant RFC.
If I may make a suggestion... Right now, an email message is consider "corrupted" because it uses 8-bit encoding for MIME headers instead of 7-bit. However, for the most part, Courier can probably handle this message. So instead of putting the whole message in an attachment, can't we do the following:
1. Email comes in with malformatted headers 2. Take all the MIME body parts in the original message, create a new message including the orginal MIME body part. Append/prepend the message with our error message. 3. Attach the original message, untouched. 4. Attach the rfcerrheader in a different attachment 5. Deliver the message
I'd add: 6. send the sender a message telling them that their mailer is broken, and include link referral to a web page that contains any known fixes.
Albeit, this doubles the disk space use for each malformatted message. However, users who doesn't really care about the RFC stuff can just read their message. We still deliver RFC compliant messages, and the error message is still there.
In spite of my ranting, I think its important that messages get through somehow.
-- The 5 year plan: In five years we'll make up another plan. Or just re-use this one.