HTML/Newsletters being received as unreadable code

[Mark Sapiro]

Steve Freegard wrote:

>Andrew Chester wrote:
>> X-Ukuvuma Solutions-MailScanner-From: support at kalahari.net
>           ^^^
>
>There's your problem - you have spaces in your %org-name% setting in 
>MailScanner.conf.

While the space in %org-name% is wrong, it does not seem to be the
cause of the problem.

Here's what I see in the last few headers and body:

---------------------------------------------------------------
content-transfer-encoding: base64
content-type: text/plain; charset=utf-8

X-Ukuvuma Solutions-MailScanner-From: support at kalahari.net
X-Spam-Status: No

X-Ukuvuma Solutions-MailScanner-From: support at kalahari.net
X-Spam-Status: No

WW91ciBLYWxhaGFyaS5uZXQgcGFzc3dvcmQgaXMgODAwNjAwCi0tIApUaGlz
IG1lc3NhZ2UgaGFzIGJlZW4gc2Nhbm5lZCBmb3IgdmlydXNlcyBhbmQKZGFu
Z2Vyb3VzIGNvbnRlbnQgYnkgdGhlIFVrdXZ1bWEgQXBvbGxvIGdhdGV3YXkg
YW5kIGlzCmJlbGlldmVkIHRvIGJlIGNsZWFuLgoK
-----------------------------------------------------------------

The two sets of MailScanner headers are curious, but it looks from the
Received: headers that the message passed twice through
apollo.ukuvuma.co.za so it was probably scanned twice.

The real problem is the empty lines preceeding each set of MailScanner
headers. This causes the MailScanner headers to be part of the body
which totally destroys the base64 encoding and results in the garbled
message.

I suspect that all base64 encoded messages get garbled this way and
non-bas64 encoded messages show the MailScanner headers in the body.

Perhaps someone with more MailScanner experience has a clue as to why
the MailScanner headers are preceded by an empty line.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan