<html>
<body>
Interesting ! <br>
If it still accepts the old configuration way, I am really curious to
learn what happened in my box for it to stop accepting the old
configuration file. I will have to work on it this week end !<br>
When/How should I use the new regex feature in the remove.headers.rules
file?<br><br>
Thanks,<br><br>
Hilário<br><br>
At 10:43 2009-05-22, you wrote:<br><br>
<br>
<blockquote type=cite class=cite cite="">On 22/05/2009 14:26, Hilario
Fochi Silveira wrote:<br>
<blockquote type=cite class=cite cite="">Good Morning<br><br>
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.<br><br>
Is there any additional possibilities like user:group or permission
related issues?<br>
Is the following example line correct?<br>
To: *@domain1.com.br
\Confirm-Reading-To:|Delivery-Receipt-To:|Disposition-Notification-To:\</blockquote>
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<br>
To: *@domain1.com.br Confirm-Reading-To: Delivery-Receipt-To:
Disposition-Notification-To:<br><br>
No \ or | or anything like that at all.<br>
<blockquote type=cite class=cite cite=""><br>
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.<br>
Is there a more intelligent way to test or generate more log
details?<br><br>
Thanks for taking your time to help.<br><br>
Best Regards,<br><br>
*Hilario Fochi Silveira<br>
**Soliton Controles Industriais Ltda.<br>
Rua Alfredo Pujol, 1010 - Sao Paulo - SP - BRAZIL ZIP: 02017-002<br><br>
<br><br>
*At 05:40 2009-05-22, Julian Field wrote:<br><br>
<br>
<blockquote type=cite class=cite cite="">On 20/05/2009 02:58, Hilario
Fochi Silveira wrote:<br>
<blockquote type=cite class=cite cite="">Hello,<br><br>
Installation details: RHEL5.3 with cPanel and MailScanner Front End
(configserver.com)<br>
MailScanner is running ok for more than one year.<br>
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.<br><br>
Two weeks ago after upgrading to version MailScanner - v4.76.24 we begun
to notice that some inbound emails were asking for return
receipts.<br><br>
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:<br><br>
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:/<br>
<br>
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.</blockquote>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:<br>
# Each header should end in a ":", but MailScanner will add it
if you forget.<br>
# Headers should be separated by commas or spaces.<br>
<blockquote type=cite class=cite cite=""><br>
The original rules file uses spaces to separate the
headers.</blockquote>That was correct.<br>
<blockquote type=cite class=cite cite="">The typical per domain lines we
had in the remove.headers.rules file were:<br><br>
# For each domain:<br>
From: *@domain1.com.br X-Mozilla-Status: X-Mozilla-Status2:
X-Spam-Processed:<br>
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:<br><br>
Those instructions used worked ok with previous MailScanner
versions.</blockquote>And I have just tried a system with a rules
file very much like yours and it works just fine.<br><br>
Sorry, but I cannot reproduce the problem.<br><br>
Jules<br><br>
-- <br>
Julian Field MEng CITP CEng<br>
<a href="http://www.mailscanner.info/" eudora="autourl">
www.MailScanner.info</a>
<<a href="http://www.mailscanner.info/" eudora="autourl">
http://www.mailscanner.info/</a>><br>
Buy the MailScanner book at
<a href="http://www.mailscanner.info/store" eudora="autourl">
www.MailScanner.info/store</a>
<<a href="http://www.mailscanner.info/store" eudora="autourl">
http://www.mailscanner.info/store</a>><br><br>
Need help customising MailScanner?<br>
Contact me!<br>
Need help fixing or optimising your systems?<br>
Contact me!<br>
Need help getting you started solving new requirements from your
boss?<br>
Contact me!<br><br>
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654<br>
Follow me at twitter.com/JulesFM and twitter.com/MailScanner<br><br>
<br>
-- <br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br><br>
-- <br>
MailScanner mailing list<br>
mailscanner@lists.mailscanner.info<br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" eudora="autourl">
http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br><br>
Before posting, read
<a href="http://wiki.mailscanner.info/posting" eudora="autourl">
http://wiki.mailscanner.info/posting</a><br><br>
Support MailScanner development - buy the book off the website!
</blockquote></blockquote><br>
Jules<br><br>
-- <br>
Julian Field MEng CITP CEng<br>
<a href="http://www.mailscanner.info/" eudora="autourl">
www.MailScanner.info</a><br>
Buy the MailScanner book at
<a href="http://www.mailscanner.info/store" eudora="autourl">
www.MailScanner.info/store</a><br><br>
Need help customising MailScanner?<br>
Contact me!<br>
Need help fixing or optimising your systems?<br>
Contact me!<br>
Need help getting you started solving new requirements from your
boss?<br>
Contact me!<br><br>
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654<br>
Follow me at twitter.com/JulesFM and twitter.com/MailScanner<br><br>
<br>
-- <br>
This message has been scanned for viruses and<br>
dangerous content by MailScanner, and is<br>
believed to be clean.<br><br>
-- <br>
MailScanner mailing list<br>
mailscanner@lists.mailscanner.info<br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" eudora="autourl">
http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br><br>
Before posting, read
<a href="http://wiki.mailscanner.info/posting" eudora="autourl">
http://wiki.mailscanner.info/posting</a><br><br>
Support MailScanner development - buy the book off the website!
</blockquote>
<x-sigsep><p></x-sigsep>
Atenciosamente,<br><br>
<font color="#008080"><b>Hilário Fochi Silveira <br>
</font>Soliton Controles Industriais Ltda.<br>
02017-002 Rua Alfredo Pujol, 1010 - São Paulo - SP - Brasil<br>
<font size=2 color="#0000FF">Tel: </font><font size=2>+55 11
2950-1834
</font><font color="#0000FF">Fax:</font> +55 11
2979-8980
<font size=2 color="#0000FF">e-mail:</font><font size=2 color="#008080">
</font><font size=2>hilario@soliton.com.br <br>
</b></font>Distribuidor SSD Drives (Anteriormente Eurotherm Drives),
Eurotherm Controls, Action Instruments, Montalvo, Koyo, Sharp<br>
<a href="http://www.soliton.com.br/" eudora="autourl">
www.soliton.com.br</a>
<x-tab> </x-tab><x-tab>
</x-tab>
<a href="http://www.eurotherm.com.br/" eudora="autourl">
www.eurotherm.com.br</a><x-tab> </x-tab><x-tab>
</x-tab>
<a href="http://www.actionio.com.br/" eudora="autourl">
www.actionio.com.br</a><x-tab> </x-tab>
<x-tab> </x-tab>
<a href="http://www.montalvo.com.br/" eudora="autourl">
www.montalvo.com.br</a><x-tab> </x-tab><br>
<br>
</body>
</html>