Rules with IP addresses
Alex Neuman van der Hans
alex at rtpty.com
Tue Sep 2 12:56:59 IST 2008
Reload, I believe, would be sufficient.
Sent from my iPhone
On Sep 2, 2008, at 6:46 AM, Caza Henha <cazahenha at hotmail.com> wrote:
> Hi Jules,
>
> I considered that transport maps in postfix was not the general case
> and was not suggesting that it is somthing that should be worked
> into the product, not unless it was specifically warranted. I will
> look into the CustomFunctions as i do know a bit of Perl and sorry
> you did answer the question initially, just my eyes not working so
> good sitting at a screen all day...Just as a quick question though,
> does and ammendment to a ruleset require a restart of MailScanner?
>
> Regards
>
> Caza
>
> > Date: Tue, 2 Sep 2008 09:00:33 +0100
> > From: MailScanner at ecs.soton.ac.uk
> > To: mailscanner at lists.mailscanner.info
> > Subject: Re: Rules with IP addresses
> >
> >
> >
> > Caza Henha wrote:
> > > Hi Jules,
> > >
> > > Thanks for the answer, I presumed that would be the case, but I
> was
> > > thinking that as our postfix configuration has transport maps it
> does
> > > actually know before sending the mail to our application server
> what
> > > the destination IP address is.
> > But that is not the general case, and I'm certainly not going to
> start
> > processing entire Postfix configurations in an attempt to work it
> out.
> > Sorry :(
> > > Does this mean then that something like the following would be
> necessary:
> > >
> > > To: support at example.com <mailto:support at example.com> store
> > > //Ticketing server
> > > To: issues at example.com <mailto:issues at example.com> store
> > > //Ticketing server
> > > ....
> > > To: application1 at example.com <mailto:application1 at example.com>
> > > delete //App Server 1
> > > To: application2 at example.com <mailto:application2 at example.com>
> > > store //App Server 2
> > > ...
> > > To: user at example.com <mailto:user at example.com> delete
> > > //Exchange server
> > > To: user at example.com <mailto:user at example.com> delete
> > > //Exchange server
> > > .....
> > > FromOrTo: default deliver //Public Mail server
> > >
> > > Bearing in mind that there are 1000s of different email address
> > > permutations going to the app servers (writing a script to
> create the
> > > rules is easy) would there be any performance problems with
> > > Mailscanner reading these files?
> > I wouldn't advise more than 1000 or so rules in a ruleset file. For
> > anything bigger than that use a Custom Function. I suspect yours
> could
> > be written as a Custom Function quite easily. Take a look in
> > /usr/lib/MailScanner/MailScanner/CustomFunctions/*.pm and you'll
> see how
> > to do it. Not hard if you know a bit of Perl.
> > > Also when using an IP address in the "From" could you direct me to
> > > information from the question below:
> > >
> > > > > Consequently I have noticed a number of examples have IP
> addresses in
> > > > > the From section of the rules and I was just wondering where
> this IP
> > > > > address was coming from and what it can actually be as I
> cannot seem
> > > > > to find any documentation on it. For example is this IP
> address (or
> > > > > the RegEx of one) the connecting smtp server (or any smtp
> server that
> > > > > the mail has passed through), client address, MX address of
> the
> > > > > sending domain etc or any combination of all the previous?
> > I answered that in my previous mail, I believe. Here it is again
> > copy-and-pasted from the quote below:
> >
> > > It is the IP address of the machine that was the client end of
> the SMTP
> > > connection to the server. So in the case of a customer-facing SMTP
> > > server, it will be the customer's client IP address. In the case
> of an
> > > MX it would be the IP address of the SMTP server talking to you.
> > >
> > > > Date: Mon, 1 Sep 2008 12:22:45 +0100
> > > > From: MailScanner at ecs.soton.ac.uk
> > > > To: mailscanner at lists.mailscanner.info
> > > > Subject: Re: Rules with IP addresses
> > > >
> > > >
> > > >
> > > > Caza Henha wrote:
> > > > >
> > > > > Hi,
> > > > >
> > > > > I have recently installed Mailscanner with Postfix and
> MailWatch and
> > > > > it seems over the last week the system is running great,
> however I am
> > > > > now getting requests to tweak the default rules that I have
> from
> > > > > various users in different departments. I have been trying
> to delve
> > > > > into the knitty gritty of the rules and understand the
> principles and
> > > > > they do not seem very complicated and when looking at some
> > > examples on
> > > > > the Wiki things shouldn't be to difficult.
> > > > >
> > > > > Consequently I have noticed a number of examples have IP
> addresses in
> > > > > the From section of the rules and I was just wondering where
> this IP
> > > > > address was coming from and what it can actually be as I
> cannot seem
> > > > > to find any documentation on it. For example is this IP
> address (or
> > > > > the RegEx of one) the connecting smtp server (or any smtp
> server that
> > > > > the mail has passed through), client address, MX address of
> the
> > > > > sending domain etc or any combination of all the previous?
> > > > It is the IP address of the machine that was the client end of
> the SMTP
> > > > connection to the server. So in the case of a customer-facing
> SMTP
> > > > server, it will be the customer's client IP address. In the
> case of an
> > > > MX it would be the IP address of the SMTP server talking to you.
> > > > >
> > > > > Also can this be used in a "To" configuration,
> > > > No. Due to the way mail delivery works, you don't know the IP
> > > address of
> > > > the destination until you have already started sending the
> message.
> > > > Can't be done.
> > > >
> > > > 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
> > > >
> > > >
> > > > --
> > > > 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!
> > >
> > >
> > >
> ---
> ---------------------------------------------------------------------
> > > Try Facebook in Windows Live Messenger! Try it Now!
> > > <http://clk.atdmt.com/UKM/go/111354030/direct/01/>
> >
> > 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
> >
> >
> > --
> > 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!
>
>
> Try Facebook in Windows Live Messenger! Try it Now!
> --
> 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!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mailscanner.info/pipermail/mailscanner/attachments/20080902/f9521b29/attachment.html
More information about the MailScanner
mailing list