10 Dec
2003
10 Dec
'03
5:37 p.m.
Whether questionable headers mean that the emails
should be flagged
as potential spam is another matter... :-)
Well, for a long time I've been rejecting mail with Content-Type:
_and_ Content-Transfer-Encoding: but no MIME-Version:. It trips on
non-spam once every blue moon or thereabouts (well, actually, probably
more often than blue moons: maybe every six months or so) but trips
relatively often on spam.
The world seems to have become a complex place... I
miss the days of
command-line mail clients, and if you really wanted to send an
attachment it was a case of encoding it yourself and relying on the
recipient knowing how to decode it...
Well...the software is stil around. Even the recipients who knew what
to do when they see a "begin 644 fnord.tar.gz" line are still around.
The trouble is, they're drowned out by the hordes who wouldn't
recognize btoa output if it bit them. :-( Nowadays you have to do
protocol first to ensure that you can agree on compression and encoding
methods. (And if I want to create a message with "attachments", I go
up and edit the Content-Type: header by hand, run the binary blobs
through "base64 -e", edit in the separator lines...and occasionally get
it wrong, but oh well.)
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse(a)rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B