Mailscanner doesn't add charset when adding signature

Julian Field mailscanner at ecs.soton.ac.uk
Thu Aug 26 14:34:35 IST 2004


<x-flowed>
As I just tack the signature on the end of the message for compatibility
with the mail clients, if I just get a message without a charset setting in
it, I don't know what it might be. I think my only option would be to add
the MIME-Version header with the charset parameter's value taken from
MailScanner.conf. But I don't think that actually helps at all.

Do I actually have enough information available to work out what the right
answer is? At the moment, I don't think so.

At 14:14 26/08/2004, you wrote:
>Julian Field wrote:
>
>>Have you seen this option:
>>
>># What character set do you want to use for the attachment that
>># replaces viruses (VirusWarning.txt)?
>># The default is "us-ascii" but if you speak anything other than
>># English, you will probably want "ISO-8859-1" instead.
>># This can also be the filename of a ruleset.
>>Attachment Encoding Charset = us-ascii
>>
>>Does it help you at all?
>
>Actually, I had to rewrite my signature so it would not contain any
>accented character because this (which I have set to "ISO-8859-1") doesn't
>help if you just sign messages and you don't have to add the
>viruswarning.txt file.
>
>The email charset is applied to the signature.  When that carset is
>incompatible with my "ISO-8859-1" characters, the results are pretty useless.
>
>Denis
>
>>
>>At 22:45 25/08/2004, you wrote:
>>
>>>When adding a signature, MailScanner adds this line:
>>>MIME-Version: 1.0
>>>
>>>But appearently this line also requires a charset-line.
>>>
>>>Because later in the chain of sendmails, when the next receiving mailserver
>>>doesn't accept 8-bit, this get added, and an exchange-server can't read the
>>>message:
>>>
>>>Content-Type: text/plain; charset=unknown-8bit
>>>Content-Transfer-Encoding: quoted-printable
>>>X-MIME-Autoconverted: from 8bit to quoted-printable by
>>>
>>>In comp.mail.sendmail I got this:
>>>
>>>"Actually the fact that using MailScanner causes the problem implies that
>>>it (or perhaps your configuration of it) is rather broken - either it
>>>drops an existing charset= parameter that was correct, or it adds some
>>>MIME-part that needs a charset= parameter (due to not being US-ASCII)
>>>but doesn't have one, or it adds "raw 8-bit" text to a (non-MIME)
>>>message that didn't have any originally. Or something like that.
>>>
>>>--Per Hedeland
>>>per at hedeland.org"
>>>
>>>Could we get this fixed? :-)
>>>
>>>Leif

--
Julian Field
www.MailScanner.info
MailScanner thanks transtec Computers for their support

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654

------------------------ MailScanner list ------------------------
To unsubscribe, email jiscmail at jiscmail.ac.uk with the words:
'leave mailscanner' in the body of the email.
Before posting, read the MAQ (http://www.mailscanner.biz/maq/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).
</x-flowed>



More information about the MailScanner mailing list