>Sam Ewalt
>Croswell, Michigan
>USA
>-- Arachne V1.70;rev.3, NON-COMMERCIAL copy, http://arachne.cz/
>
>
>--MIME-multipart-message-boundary-981730858
>Content-Type: application/octet-stream ;name=autoexec.bat
>Content-Transfer-Encoding: base64
>
>DQoNCkBFQ0hPIE9GRg0KUFJPTVBUICRwJGcNClBBVEggQzpcRE9TO1x1dGlscztDOlxNT1VT
>RTtDOlxBUkFDSE5FNTtDOlxBUkFDSE5FNg0KTEggL0w6MiwzNjA2NCBNT1VTRQ0KTEggL0w6
>MDsyLDQ1NDcyIC9TIFNNQVJURFJWLkVYRSAvTiA0MDk2IDAgL0U6ODE5MiAvQjozMiAvVg0K
>U0VUIFRFTVA9QzpcVEVNUA0KcmVtIEM6XHNkZFx1bml2YmUuZXhlIC13DQo=
>--MIME-multipart-message-boundary-981730858--
What's the purpose of attaching text files like autoexec.bat, config.sys and
arachne.cfg base64-encoded, as opposed to straight text? I could use MUNPACK if
I thought it worth the trouble, but don't really see why I should.
I am on a medicinal herbs list that absolutely prohibits HTML, quoted-printable
and base64. Such messages are automatically bounced by the list software, which
unfortunately gets overzealous, bouncing good messages that contain a certain
word like "attachment". Messages must be one-part plain text, a principle that
I fully agree with for emailing lists.
