Question about custom functions / generic spam plugin: Can they add headers?

[Julian Field]

    [ The following text is in the "ISO-8859-1" character set. ]
    [ Your display is set for the "US-ASCII" character set.  ]
    [ Some characters may be displayed incorrectly. ]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Neuman van der Hans wrote:

> Julian Field wrote:
>
>> Beat you to it by miles on that one. What you want is this:
>>
>> # Do you want to add the Envelope-From: header?
>> # This is very useful for tracking where spam came from as it
>> # contains the envelope sender address.
>> # This can also be the filename of a ruleset.
>> Add Envelope From Header = yes
>>
>> # Do you want to add the Envelope-To: header?
>> # This can be useful for tracking spam destinations, but should be
>> # used with care due to possible privacy concerns with the use of
>> # Bcc: headers by users.
>> # This can also be the filename of a ruleset.
>> Add Envelope To Header = no
>>
>> # This is the name of the Envelope From header
>> # controlled by the option above.
>> # This can also be the filename of a ruleset.
>> Envelope From Header = X-MailScanner-From:
>>
>> # This is the name of the Envelope To header
>> # controlled by the option above.
>> # This can also be the filename of a ruleset.
>> Envelope To Header = X-MailScanner-To:
>>
>> On 10 Oct 2005, at 04:38, Stijn Jonker wrote:
>>
>>
>>
>>
>>
>>
>>
>>> Hello all,
>>>
>>> There is currently a requirement popping up to add to headers for all
>>> email towards an domain:
>>> X-SMTP-From: <containing sender email>
>>> X-SMTP-To: <containing recipient(s) email>
>>>
>>> Before diving in writing my own libmilter function/program I was
>>> thinking of the custom function and/or the generic spam plugin.
>>>
>>> Whilst reading the book it didn't become really clear whether  
>>> either of
>>> them can do it. I checked the source and although some experience at
>>> perl I'm unsure if i can call the functions AddHeader/ChangeHeader  
>>> from
>>> the various mailer pm's suchs as Sendmail.pm.
>>>
>>> Therefore my question, is this possible?
>>>
>>> Thanks in advance,
>>> Stijn
>>>
>>
> You might want to consider letting your users know that even if they 
> send e-mail out with BCC: the header will be included, so anyone who 
> looks at the message source will see who the recipients were. This 
> way, either they must send each message individually (some MUA's will 
> let you do this) or risk others knowing who they BCC:'d the message to.

This is precisely why I leave the Envelope-To header switched off by 
default. I thoroughly disapprove of switching this on, but people can 
find it useful when diagnosing mail routing problems.

- -- 
Julian Field
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store
Professional Support Services at www.MailScanner.biz
MailScanner thanks transtec Computers for their support

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


-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.0.2 (Build 2424)

iQA/AwUBQ0qrRRH2WUcUFbZUEQIavwCgnOiDJIPlW76bA9JUVeMqvLlgZFgAoMSd
6BgqQsXphmqHpF8BWuUiVDbL
=3Zmc
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

------------------------ 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 Wiki (http://wiki.mailscanner.info/) and
the archives (http://www.jiscmail.ac.uk/lists/mailscanner.html).

Support MailScanner development - buy the book off the website!