"Remove These Headers" not working

[Julian Field]

On 22/05/2009 14:26, Hilario Fochi Silveira wrote:
> Good Morning
>
> Thus of course I have done some kind of mistake that I still did not 
> pinpoint. I will try again to double check where I may have done the 
> mistake.
>
> Is there any additional possibilities like user:group or permission 
> related issues?
> Is the following example line correct?
> To: *@domain1.com.br 
> \Confirm-Reading-To:|Delivery-Receipt-To:|Disposition-Notification-To:\
That's wrong. The list, as I said, should be a space separated list of 
header names. So you should just put it like that, such as
To: *@domain1.com.br Confirm-Reading-To: Delivery-Receipt-To: 
Disposition-Notification-To:

No \ or | or anything like that at all.
>
> Till now I am just looking at the log tail for file load fails and 
> sending outside emails to myself with return receipts to check if it 
> is working.
> Is there a more intelligent way to test or generate more log details?
>
> Thanks for taking your time to help.
>
> Best Regards,
>
> *Hilario Fochi Silveira
> **Soliton Controles Industriais Ltda.
> Rua Alfredo Pujol, 1010 - Sao Paulo - SP - BRAZIL ZIP: 02017-002
>
>
>
> *At 05:40 2009-05-22, Julian Field wrote:
>
>
>> On 20/05/2009 02:58, Hilario Fochi Silveira wrote:
>>> Hello,
>>>
>>> Installation details: RHEL5.3 with cPanel and MailScanner Front End 
>>> (configserver.com)
>>> MailScanner is running ok for more than one year.
>>> Our server uses the "Remove These Headers = 
>>> %rules-dir%/remove.headers.rules" setting to eliminate inbound 
>>> return receipts requests while allowing outbound receipts headers to 
>>> stay intact.
>>>
>>> Two weeks ago after upgrading to version MailScanner - v4.76.24 we 
>>> begun to notice that some inbound emails were asking for return 
>>> receipts.
>>>
>>> We played a lot with the rules file without success and as a 
>>> temporary solution, we replaced the per domain rules file with the 
>>> following single line instruction:
>>>
>>> Remove These Headers = 
>>> /Confirm-Reading-To:|Delivery-Receipt-To:|Disposition-Notification-To:|Errors-To:|MDRcpt-To:|MDSend-Notifications-To:|Read-Receipt-To:|Receipt-Requested-To:|Return-Receipt-To:|Status:|Smtp-Rcpt-To:|X-Acknowledge-To:|X-Confirm-Reading-To:|X-IMAPBase:|X-IMAP:|X-Keywords:|X-Mozilla-Status:|X-Mozilla-Status2:|X-PMrqc:|X-Spam-Processed:|X-Status:|X-UID:|X-UIDL:/
>>>
>>> This solution is working, we have no receipts at all both inbound 
>>> and outbound, but we wish to regain the fine granularity control we 
>>> once had.
>> That should definitely not work, and it was a small bug that was 
>> allowing it to work. The spec in the MailScanner.conf file clearly 
>> states that:
>> # Each header should end in a ":", but MailScanner will add it if you 
>> forget.
>> # Headers should be separated by commas or spaces.
>>>
>>> The original rules file uses spaces to separate the headers.
>> That was correct.
>>> The typical per domain lines we had in the remove.headers.rules file 
>>> were:
>>>
>>> # For each domain:
>>> From: *@domain1.com.br X-Mozilla-Status: X-Mozilla-Status2: 
>>> X-Spam-Processed:
>>> To: *@domain1.com.br Confirm-Reading-To: Delivery-Receipt-To: 
>>> Disposition-Notification-To: Errors-To: MDRcpt-To: 
>>> MDSend-Notifications-To: Read-Receipt-To: Receipt-Requested-To: 
>>> Return-Receipt-To: Status: Smtp-Rcpt-To: X-Acknowledge-To: 
>>> X-Confirm-Reading-To: X-IMAPBase: X-IMAP: X-Keywords: 
>>> X-Mozilla-Status: X-Mozilla-Status2: X-PMrqc: X-Spam-Processed: 
>>> X-Status: X-UID: X-UIDL:
>>>
>>> Those instructions used worked ok with previous MailScanner versions.
>> And  I have just tried a system with a rules file very much like 
>> yours and it works just fine.
>>
>> Sorry, but I cannot reproduce the problem.
>>
>> Jules
>>
>> -- 
>> Julian Field MEng CITP CEng
>> www.MailScanner.info <http://www.mailscanner.info/>
>> Buy the MailScanner book at www.MailScanner.info/store 
>> <http://www.mailscanner.info/store>
>>
>> Need help customising MailScanner?
>> Contact me!
>> Need help fixing or optimising your systems?
>> Contact me!
>> Need help getting you started solving new requirements from your boss?
>> Contact me!
>>
>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
>> Follow me at twitter.com/JulesFM and twitter.com/MailScanner
>>
>>
>> -- 
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>>
>> -- 
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>> Before posting, read http://wiki.mailscanner.info/posting
>>
>> Support MailScanner development - buy the book off the website! 

Jules

-- 
Julian Field MEng CITP CEng
www.MailScanner.info
Buy the MailScanner book at www.MailScanner.info/store

Need help customising MailScanner?
Contact me!
Need help fixing or optimising your systems?
Contact me!
Need help getting you started solving new requirements from your boss?
Contact me!

PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654
Follow me at twitter.com/JulesFM and twitter.com/MailScanner


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