Re: Malformed From: address in headers

Cameron Simpson wrote: On 15Aug2009 14:06, Gen-Paul wrote: [...nice rant...] Thanks for snipping. I've read some of his older posts and he sounds like a decent enough sort of chap otherwise. Actually, a few months back, his malformed "From:" email address was quoted and did not cause me

Re: Malformed From: address in headers

On 15Aug2009 14:06, Gen-Paul wrote: | I tried to send test emails with such malformed "From:" headers to | myself to try and figure out what others are seeing in different | contexts such as the above-mentioned, and guess what.. I never | managed to get one broken email such as his to make it to m

Re: Malformed From: address in headers

Cameron Simpson wrote: On 12Aug2009 14:56, I wrote: | I'm thinking about getting procmail to rewrite that header | as you describe. Maybe (untested): | | :0whf | * ^from:.* | | formail -i 'From: Joe User ' | | ahead of the other rules. I'm now running with

Re: Malformed From: address in headers

On 12Aug2009 14:56, I wrote: | I'm thinking about getting procmail to rewrite that header | as you describe. Maybe (untested): | | :0whf | * ^from:.* | | formail -i 'From: Joe User ' | | ahead of the other rules. I'm now running with this: :0 * ^from:.*

Re: Malformed From: address in headers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, August 11 at 11:23 PM, quoth Kyle Wheeler: >> wockas..? > > :) A name for greater-than and less-than symbols, collectively. Hmm... > I don't know where I got it from (Google has no idea either, though I > may be mispelling it). I though

Re: Malformed From: address in headers

On 11Aug2009 19:41, Patrick Gen Paul wrote: | On the python-users mailing lists, there are posts from a user who | forges his From: email address to something like: | | Joe User Ah, so I'm not the only person irritated by this guy. Possibly mutt users are the only

Re: Malformed From: address in headers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, August 11 at 11:47 PM, quoth Patrick Gen Paul: > Funny your mentioning T-Bird, btw, since my correspondent (?) > actually appears to use gnus. Huh. >> Since he's not including a route, the thing within the wockas (<>) >> MUST conform

Re: Malformed From: address in headers

On Tue, Aug 11, 2009 at 10:12 PM, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tuesday, August 11 at 09:34 PM, quoth Patrick Gen Paul: >> Is there a well-respected mail etiquette, or RFC even, that I could >> refer him to? > > Ah! Why did you say so? I thought you

Re: Malformed From: address in headers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, August 11 at 09:34 PM, quoth Patrick Gen Paul: > Is there a well-respected mail etiquette, or RFC even, that I could > refer him to? Ah! Why did you say so? I thought you were trying to decide whether or not mutt was misbehaving (I won

Re: Malformed From: address in headers

On Tue, Aug 11, 2009 at 8:19 PM, Kyle Wheeler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > On Tuesday, August 11 at 07:41 PM, quoth Patrick Gen Paul: >>Does anyone know why this is happening, and how I can work around it? > > I think you pretty much hit the nail on the head: his "

Re: Malformed From: address in headers

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, August 11 at 07:41 PM, quoth Patrick Gen Paul: >Does anyone know why this is happening, and how I can work around it? I think you pretty much hit the nail on the head: his "From:" header is invalid. Mutt can see that it's invalid, and s

Malformed From: address in headers

On the python-users mailing lists, there are posts from a user who forges his From: email address to something like: Joe User The result in mutt with "index_format" set to: %-30.30n ... is that the following is displayed in the index: python-list-bounces+pge