<html>
<body>
<br>
[quote]<br>
<blockquote type=cite class=cite cite="">... So if you think my docs can
be agreed, please do suggest an improvement. <br>
So you can insert comments and additions of your own ....
</blockquote>[/quote]<br><br>
Here is my humble suggestion <br><br>
# Example 1 (traditional)<br>
# Remove These Headers = X-Mozilla-Status: X-Mozilla-Status2:
X-Spam-Processed:<br>
# <br>
# Example 2 (mixed with regex expressions)<br>
# Remove These Headers = X-UID: /X-Mozilla-Status.*:/
/Disposition.*:/<br>
# <br>
# Example 3 (regex using \s as spaces)<br>
# Remove These Headers = X-UID: /your\sregex\swith\sspaces\shere/
/X-Mozilla-Status.*:/ /Disposition.*:/<br>
# <br>
# Example 4 (using a per domain rules file)<br>
# If you wish to remove (block) incoming return-receipt requests while
allowing the outgoing request to pass, set<br>
# Remove These Headers = %rules-dir%/remove.headers.rules <br>
# And edit the content of the remove.headers.rules file based on the
following examples<br>
#
From:<x-tab> </x-tab>*@yourdomain1.com<x-tab>
</x-tab>X-Mozilla-Status:
X-Mozilla-Status2: X-Spam-Processed:<br>
#
To:<x-tab> </x-tab><x-tab>
</x-tab>
*@yourdomain1.com<x-tab> </x-tab>
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>
#
FromOrTo:<x-tab> </x-tab>default<x-tab>
</x-tab><x-tab>
</x-tab><x-tab>
</x-tab>X-Mozilla-Status:
X-Mozilla-Status2: X-Spam-Processed:<br>
# Note: In this example, when an outgoing email is sent with at least one
copy to accounts in your own domain accounts, all matching headers will
be removed from all emails, including the outgoing ones.<br><br>
<br>
note: I believe Example 3 must not use the : but I'm not sure.<br>
<x-sigsep><p></x-sigsep>
Best Regards,<br><br>
<font color="#008080"><b>Hilario Fochi Silveira <br>
</font>Soliton Controles Industriais Ltda. <br>
Rua Alfredo Pujol, 1010 - Sao Paulo - SP - BRAZIL
<font size=2 color="#0000FF">ZIP: </font>02017-002<br><br>
<br>
</b>At 14:01 2009-05-23, Julian Field wrote:<br>
<blockquote type=cite class=cite cite="">-----BEGIN PGP SIGNED
MESSAGE-----<br>
Hash: SHA1<br><br>
On 23/05/2009 14:55, Hilario Fochi Silveira wrote:<br>
> humm... your example is interesting.<br>
><br>
> As regex uses "I" and the original system used
"spaces" for the "or" <br>
> function, I had interpreted that the instructions texts in <br>
> MailScanner.conf were not fully updated and that the spaces were not
<br>
> allowed anymore at all !<br>
Spaces are not allowed in the regexps, correct. So you need to use \s in
<br>
your regexp instead of a space character. That is explained in the docs
<br>
as shown below.<br>
> It looked like the old and the new system were incompatible with
each <br>
> other.<br>
> May I kindly suggest that you insert your example in the <br>
> MailScanner.conf file if possible with an \s anywhere that would
make <br>
> clear the correct usage of regex.<br>
Okay, I'll try to improve the docs example a bit. It does already make
<br>
it very clear that it mustn't contain spaces, and that you should use \s
<br>
instead of the space character.<br><br>
So if you think my docs can be agreed, please do suggest an improvement.
<br>
So you can insert comments and additions of your own, here is the bulk
<br>
of the documentation for this setting:<br><br>
# If any of these headers are included in a a message, they will be
deleted.<br>
# This is a space-separated list of a mixture of any combination of<br>
# 1. Names of headers, optionally ending with a ':'<br>
# (the ':' will be added if not supplied)<br>
# 2. Regular expressions starting and ending with a '/'.<br>
# These regular expressions are matched against the
entire header line,<br>
# not just the name of the header.<br>
# **NOTE** The regular expressions must *not* contain
spaces,<br>
#
so use '\s' instead of ' '.<br>
# This is very useful for removing return-receipt requests and any
headers<br>
# which mean special things to your email client application.<br>
# X-Mozilla-Status is bad as it allows spammers to make a message appear
to<br>
# have already been read, which is believed to bypass some naive
spam<br>
# filtering systems.<br>
# Receipt requests are bad as they give any attacker confirmation that
an<br>
# account is active and being read. You don't want this sort of
information<br>
# to leak outside your corporation. So you might want to remove<br>
(long list of header names removed)<br>
# If you are having problems with duplicate message-id headers when
you<br>
# release spam from the quarantine and send it to an Exchange server,
<br>
then add<br>
# Message-Id.<br>
# Each header should end in a ":", but MailScanner will add it
if you <br>
forget.<br>
# Headers should be separated by commas or spaces.<br><br>
Please add comments and suggestions for new docs or changes to existing
<br>
info above.<br>
> Either way it is an incredible coincidence that my box stopped
working <br>
> with the rules file just when the new regex feature was added.<br>
If the regexp is not surrounded by / characters then it will be treated
<br>
the same way the header names always used to be handled. So it should be
<br>
compatible with the old system. That was certainly my intention anyway.
<br>
The great advantage of using a regexp is that it is matched against the
<br>
*entire* header line, and not just the name of the header, so you can
<br>
use it to remove a header if its value contains a particular word or
<br>
something like that.<br><br>
> At 07:03 2009-05-23, you wrote:<br>
>> -----BEGIN PGP SIGNED MESSAGE-----<br>
>> Hash: SHA1<br>
>><br>
>> My intention was that you would present a list of regexps for
header<br>
>> names, so you could do things like<br>
>> Remove These Headers = X-UID: /X-Mozilla-Status.*:/
/Disposition.*:/<br>
>> and things like that, not one big regexp that covered
everything.<br>
>><br>
>> On 22/05/2009 20:35, Hilario Fochi Silveira wrote:<br>
>> > Wow, Now I am really confused !<br>
>> ><br>
>> > The following are the instructions I interpreted as new
regex feature<br>
>> > for "<br>
>> > Remove These Headers<br>
>> > "<br>
>> > I see them in two different places: the changelog and the
instructions<br>
>> > in the MailScanner.conf file inside the <br>
>> MailScanner-4.77.5-1.rpm.tar.gz<br>
>> > And the new instructions prohibit the use of spaces in the
new <br>
>> regex mode.<br>
>> ><br>
>> > a) The changelog file<br>
>> ><br>
>> > Reference:
<a href="http://www.mailscanner.info/ChangeLog" eudora="autourl">
http://www.mailscanner.info/ChangeLog</a><br>
>> > 1/4/2009 New in Version
4.75.11-1<br>
>> ><br>
>> >
=================================<br>
>> > ...<br>
>> > 9 Added support for regular
expressions in "Remove These<br>
>> > Headers". Note that<br>
>> ><br>
>>
>
the expression is matched against the whole header line, <br>
>> not<br>
>> > just the
name<br>
>> ><br>
>>
> of
the header. Note that the expressions must not <br>
>> contain any<br>
>> > spaces,
so<br>
>> ><br>
>>
>
use '\s' instead of ' '. The match is done <br>
>> case-insensitive in<br>
>> > all
cases.<br>
>> ><br>
>> > ...<br>
>> ><br>
>> ><br>
>> > b) The MailScanner.conf file
(MailScanner-4.77.5-1.rpm.tar.gz ).<br>
>> ><br>
>> > Reference:<br>
>> > ...<br>
>> > # If any of these headers are
included in a a message, they will<br>
>> > be deleted.<br>
>> > # This is a space-separated list of
a mixture of any <br>
>> combination of<br>
>> > # 1. Names of headers, optionally
ending with a ':'<br>
>> > # (the ':' will
be added if not supplied)<br>
>> > # 2. Regular expressions starting
and ending with a '/'.<br>
>> > # These regular
expressions are matched against the entire<br>
>> > header line,<br>
>> > # not just the
name of the header.<br>
>> > # **NOTE** The
regular expressions must *not* contain spaces,<br>
>> >
#
so use '\s' instead of ' '.<br>
>> > # This is very useful for removing
return-receipt requests and any<br>
>> > headers<br>
>> > ...<br>
>> ><br>
>> > I really thought it was a new regex feature to remove
headers and/or<br>
>> > additional information.<br>
>> > It works as a line in the Mailscanner.conf file, but I am
not able to<br>
>> > have my old per domain file working anymore.<br>
>> > I just do not know how to use it correctly and my server
does not<br>
>> > accept the file with spaces any more.<br>
>> ><br>
>> > Thanks again for helping.<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 16:00 2009-05-22, Julian Field wrote:<br>
>> ><br>
>> >> -----BEGIN PGP SIGNED MESSAGE-----<br>
>> >> Hash: SHA1<br>
>> >><br>
>> >><br>
>> >><br>
>> >> On 22/05/2009 18:11, Hilario Fochi Silveira wrote:<br>
>> >> > Interesting !<br>
>> >> > If it still accepts the old configuration way, I
am really <br>
>> curious to<br>
>> >> > learn what happened in my box for it to stop
accepting the old<br>
>> >> > configuration file. I will have to work on it this
week end !<br>
>> >> > When/How should I use the new regex feature in
the<br>
>> >> > remove.headers.rules file?<br>
>> >> What new regex feature? There never was one! Not in my
book <br>
>> anyway. What<br>
>> >> you may have exploited due to poor syntax checking on
my part was <br>
>> never<br>
>> >> in any way a supported feature, the feature is as
documented in the<br>
>> >> MailScanner.conf file, ie. a space-separated list of
header names.<br>
>> >> ><br>
>> >> > Thanks,<br>
>> >> ><br>
>> >> > Hilário<br>
>> >> ><br>
>> >> > At 10:43 2009-05-22, you wrote:<br>
>> >> ><br>
>> >> ><br>
>> >> >> On 22/05/2009 14:26, Hilario Fochi Silveira
wrote:<br>
>> >> >>> Good Morning<br>
>> >> >>><br>
>> >> >>> Thus of course I have done some kind of
mistake that I still <br>
>> did not<br>
>> >> >>> pinpoint. I will try again to double check
where I may have <br>
>> done the<br>
>> >> >>> mistake.<br>
>> >> >>><br>
>> >> >>> Is there any additional possibilities like
user:group or <br>
>> permission<br>
>> >> >>> related issues?<br>
>> >> >>> Is the following example line
correct?<br>
>> >> >>> To: *@domain1.com.br<br>
>> >> >>><br>
>> >> <br>
>>
\Confirm-Reading-To:|Delivery-Receipt-To:|Disposition-Notification-To:\<br>
>> >> >> That's wrong. The list, as I said, should be a
space separated <br>
>> list<br>
>> >> >> of header names. So you should just put it
like that, such as<br>
>> >> >> To: *@domain1.com.br Confirm-Reading-To:
Delivery-Receipt-To:<br>
>> >> >> Disposition-Notification-To:<br>
>> >> >><br>
>> >> >> No \ or | or anything like that at all.<br>
>> >> >>><br>
>> >> >>> Till now I am just looking at the log tail
for file load fails <br>
>> and<br>
>> >> >>> sending outside emails to myself with
return receipts to check <br>
>> if it<br>
>> >> >>> is working.<br>
>> >> >>> Is there a more intelligent way to test or
generate more log <br>
>> 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>
>> >> >>>> On 20/05/2009 02:58, Hilario Fochi
Silveira wrote:<br>
>> >> >>>>> Hello,<br>
>> >> >>>>><br>
>> >> >>>>> Installation details: RHEL5.3 with
cPanel and MailScanner Front<br>
>> >> >>>>> End (configserver.com)<br>
>> >> >>>>> MailScanner is running ok for more
than one year.<br>
>> >> >>>>> Our server uses the "Remove
These Headers =<br>
>> >> >>>>>
%rules-dir%/remove.headers.rules" setting to eliminate inbound<br>
>> >> >>>>> return receipts requests while
allowing outbound receipts <br>
>> headers<br>
>> >> >>>>> to stay intact.<br>
>> >> >>>>><br>
>> >> >>>>> Two weeks ago after upgrading to
version MailScanner - <br>
>> v4.76.24 we<br>
>> >> >>>>> begun to notice that some inbound
emails were asking for return<br>
>> >> >>>>> receipts.<br>
>> >> >>>>><br>
>> >> >>>>> We played a lot with the rules
file without success and as a<br>
>> >> >>>>> temporary solution, we replaced
the per domain rules file <br>
>> with the<br>
>> >> >>>>> following single line
instruction:<br>
>> >> >>>>><br>
>> >> >>>>> Remove These Headers =<br>
>> >> >>>>><br>
>> >> <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>
>> >> >>>>><br>
>> >> >>>>> This solution is working, we have
no receipts at all both <br>
>> inbound<br>
>> >> >>>>> and outbound, but we wish to
regain the fine granularity <br>
>> control<br>
>> >> >>>>> we once had.<br>
>> >> >>>> That should definitely not work, and
it was a small bug that was<br>
>> >> >>>> allowing it to work. The spec in the
MailScanner.conf file <br>
>> clearly<br>
>> >> >>>> states that:<br>
>> >> >>>> # Each header should end in a
":", but MailScanner will add <br>
>> it if<br>
>> >> >>>> you forget.<br>
>> >> >>>> # Headers should be separated by
commas or spaces.<br>
>> >> >>>>><br>
>> >> >>>>> The original rules file uses
spaces to separate the headers.<br>
>> >> >>>> That was correct.<br>
>> >> >>>>> The typical per domain lines we
had in the remove.headers.rules<br>
>> >> >>>>> file were:<br>
>> >> >>>>><br>
>> >> >>>>> # For each domain:<br>
>> >> >>>>> From: *@domain1.com.br
X-Mozilla-Status: X-Mozilla-Status2:<br>
>> >> >>>>> X-Spam-Processed:<br>
>> >> >>>>> To: *@domain1.com.br
Confirm-Reading-To: Delivery-Receipt-To:<br>
>> >> >>>>> Disposition-Notification-To:
Errors-To: MDRcpt-To:<br>
>> >> >>>>> MDSend-Notifications-To:
Read-Receipt-To: Receipt-Requested-To:<br>
>> >> >>>>> Return-Receipt-To: Status:
Smtp-Rcpt-To: X-Acknowledge-To:<br>
>> >> >>>>> X-Confirm-Reading-To: X-IMAPBase:
X-IMAP: X-Keywords:<br>
>> >> >>>>> X-Mozilla-Status:
X-Mozilla-Status2: X-PMrqc: X-Spam-Processed:<br>
>> >> >>>>> X-Status: X-UID: X-UIDL:<br>
>> >> >>>>><br>
>> >> >>>>> Those instructions used worked ok
with previous MailScanner<br>
>> >> versions.<br>
>> >> >>>> And I have just tried a system
with a rules file very much like<br>
>> >> >>>> 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>
>> >>
<a href="http://www.mailscanner.info/" eudora="autourl">
http://www.mailscanner.info/</a>> <<br>
>> >> >>>>
<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><br>
>> >>
<<a href="http://www.mailscanner.info/store" eudora="autourl">
http://www.mailscanner.info/store</a>><br>
>> >> >>>> <
<a href="http://www.mailscanner.info/store" eudora="autourl">
http://www.mailscanner.info/store</a>> <<br>
>> >> >>>>
<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<br>
>> >> 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!<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>
>> >>
<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><br>
>> >>
<<a href="http://www.mailscanner.info/store" eudora="autourl">
http://www.mailscanner.info/store</a>><br>
>> >> >> <
<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 <br>
>> 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!<br>
>> >> ><br>
>> >> > Atenciosamente,<br>
>> >> ><br>
>> >> > *Hilário Fochi Silveira<br>
>> >> > **Soliton Controles Industriais Ltda.<br>
>> >> > 02017-002 Rua Alfredo Pujol, 1010 - São Paulo - SP
- Brasil<br>
>> >> > Tel: +55 11 2950-1834 Fax: +55 11 2979-8980
e-mail:<br>
>> >> > hilario@soliton.com.br<br>
>> >> > *Distribuidor SSD Drives (Anteriormente Eurotherm
Drives), <br>
>> Eurotherm<br>
>> >> > Controls, Action Instruments, Montalvo, Koyo,
Sharp<br>
>> >> >
<a href="http://www.soliton.com.br/" eudora="autourl">
www.soliton.com.br</a>
<<a href="http://www.soliton.com.br/" eudora="autourl">
http://www.soliton.com.br/</a>> <<br>
>> >>
<a href="http://www.soliton.com.br/" eudora="autourl">
http://www.soliton.com.br/</a>>
<a href="http://www.eurotherm.com.br/" eudora="autourl">
www.eurotherm.com.br</a><br>
>> >>
<<a href="http://www.eurotherm.com.br/" eudora="autourl">
http://www.eurotherm.com.br/</a>><br>
>> >> > <
<a href="http://www.eurotherm.com.br/" eudora="autourl">
http://www.eurotherm.com.br/</a>>
<a href="http://www.actionio.com.br/" eudora="autourl">
www.actionio.com.br</a><br>
>> >>
<<a href="http://www.actionio.com.br/" eudora="autourl">
http://www.actionio.com.br/</a>><br>
>> >> > <
<a href="http://www.actionio.com.br/" eudora="autourl">
http://www.actionio.com.br/</a>>
<a href="http://www.montalvo.com.br/" eudora="autourl">
www.montalvo.com.br</a><br>
>> >>
<<a href="http://www.montalvo.com.br/" eudora="autourl">
http://www.montalvo.com.br/</a>><br>
>> >> > <
<a href="http://www.montalvo.com.br/" eudora="autourl">
http://www.montalvo.com.br/</a>><br>
>> >> ><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><br>
>> >>
<<a href="http://www.mailscanner.info/store" eudora="autourl">
http://www.mailscanner.info/store</a>><br>
>> >> Follow me at twitter.com/JulesFM<br>
>> >><br>
>> >> MailScanner customisation, or any advanced system
administration <br>
>> help?<br>
>> >> Contact me at Jules@Jules.FM<br>
>> >><br>
>> >> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947
1415 B654<br>
>> >> PGP public key:
<a href="http://www.jules.fm/julesfm.asc" eudora="autourl">
http://www.jules.fm/julesfm.asc</a><br>
>> >><br>
>> >><br>
>> >> -----BEGIN PGP SIGNATURE-----<br>
>> >> Version: PGP Desktop 9.10.0 (Build 500)<br>
>> >> Comment: Use PGP or Thunderbird Enigmail to verify this
message<br>
>> >> Charset: ISO-8859-1<br>
>> >><br>
>> >>
wj8DBQFKFvZSEfZZRxQVtlQRAq8uAKDnNpIOq06Iiihr1h3vD+D6qUE04QCg5M0G<br>
>> >> +QTTpHrgwHz371bPuVpt6bE=<br>
>> >> =Qvgv<br>
>> >> -----END PGP SIGNATURE-----<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!<br>
>><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>
>> Follow me at twitter.com/JulesFM<br>
>><br>
>> MailScanner customisation, or any advanced system administration
help?<br>
>> Contact me at Jules@Jules.FM<br>
>><br>
>> PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415
B654<br>
>> PGP public key:
<a href="http://www.jules.fm/julesfm.asc" eudora="autourl">
http://www.jules.fm/julesfm.asc</a><br>
>><br>
>><br>
>> -----BEGIN PGP SIGNATURE-----<br>
>> Version: PGP Desktop 9.10.0 (Build 500)<br>
>> Comment: Use PGP or Thunderbird Enigmail to verify this
message<br>
>> Charset: ISO-8859-1<br>
>><br>
>>
wj8DBQFKF8nsEfZZRxQVtlQRApzAAJ9FkThuK2sojwjemn4byMCtH0tF4QCgj9P8<br>
>> i/yXi7l76D6QCNylWxApkQs=<br>
>> =xPP8<br>
>> -----END PGP SIGNATURE-----<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!<br>
><br><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>
Follow me at twitter.com/JulesFM<br><br>
MailScanner customisation, or any advanced system administration
help?<br>
Contact me at Jules@Jules.FM<br><br>
PGP footprint: EE81 D763 3DB0 0BFD E1DC 7222 11F6 5947 1415 B654<br>
PGP public key:
<a href="http://www.jules.fm/julesfm.asc" eudora="autourl">
http://www.jules.fm/julesfm.asc</a><br><br>
<br>
-----BEGIN PGP SIGNATURE-----<br>
Version: PGP Desktop 9.10.0 (Build 500)<br>
Comment: Use PGP or Thunderbird Enigmail to verify this message<br>
Charset: ISO-8859-1<br><br>
wj8DBQFKGCvgEfZZRxQVtlQRAp1GAJkBcbObXYgGW6zHo97sZOflX7JBBwCgyKsR<br>
v+Eaju7OiKjyDpNfqYe3kJ0=<br>
=976l<br>
-----END PGP SIGNATURE-----<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></body>
</html>