MLUG: RE: [UUG/MLUG] /var/spool/mail/...
RE: [UUG/MLUG] /var/spool/mail/...
Email address obfuscation in effect -- please click here to turn it off.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
The deal is this:
If you try to spoof a header "\nFrom " into the body of the email, it
actually gets written to the inbox file like this:

>From EMAIL:PROTECTED Some Date 1999

instead of the more verbatim
>From EMAIL:PROTECTED Some Date 1999

This is true anytime mail encounters "\nFrom " as far as I can tell.

So it is (at least seemingly on the surface evaluation) safe to search for
"\nFrom " minding ye the space after from.  I tested this under a few
different conditions and it seems to hold true each time.  Additionally, it
even prints the > in the body of the message when you read it through your
mail client.

Perhaps a more visible than desired solution, but it certainly works...

I'm not sure if your client (pine)(er whatever) puts in the > or if it is a
mail (sendmail) thing, but it stands to reason that you could parse out the
> at display-time when the user gets around to reading that line so a
paragraph like this:

>From someone who cares

doesn't read like:

>From someone who cares

Of course, it's terrible grammar to begin sentences with a preposition,
(this sentence, for example)*smirk*, but you know, it's things like this
that makes programming fun anyway!