Mailscanner 5.0.6-4 ant port 25 not listening
Antony.Stone at mailscanner.open.source.it
Mon Sep 4 11:39:17 UTC 2017
On Monday 04 September 2017 at 13:32:59, Marek Górny wrote:
> Please correct me if I'm wrong:
> When i run mailscanner.service he should check postfix and his services
> (when MTA is set to postfix od course)?
No; you need to start the postfix services, and you also need to start the
MailScanner will not start postfix for you (you might not want it to start
under some circumstances), and will run quite happily with postfix stopped
(processing any emails which happen to be in the incoming queue, for example).
For debugging purposes it is often very useful to:
- stop mailscanner and start postfix
- send an email and ensure that it is received
- check that it is placed in the incoming queue
- then stop postfix and start mailscanner
- check that the mail is found in the incoming queue and processed
- check that the mail gets put into the outbound queue
- then restart postfix and check that the email is found and delivered
If the processes were interconnected so that starting mailscanner
automatically started postfix you couldn't do this sort of thing.
> -----Original Message-----
> From: MailScanner
> [mailto:mailscanner-bounces+marek.gorny=bolix.pl at lists.mailscanner.info]
> On Behalf Of Antony Stone Sent: Monday, September 4, 2017 1:23 PM
> To: MailScanner Discussion <mailscanner at lists.mailscanner.info>
> Subject: Re: Mailscanner 5.0.6-4 ant port 25 not listening
> On Monday 04 September 2017 at 13:15:10, Marek Górny wrote:
> > with postfix.service stoped:
> > netstat -lpn | grep 25
> (no TCP socket listening on port 25 in output displayed)
> > and when postfix.service is started:
> > netstat -lpn | grep 25
> > tcp 0 0 0.0.0.0:25 0.0.0.0:*
> > LISTEN
> > 31008/master
> Okay, so that shows that when postfix is started, you have a process called
> "master" (which is standard for postfix), with PID 31008 on this occasion,
> listening on port 25.
> When postfix is not started, you have nothing listening on port 25.
> I realised after sending my last email that a better command to use is:
> # netstat -lptn | grep :25
> The "t" option restricts the output to TCP sockets only, and the colon in
> the grep makes sure you only match port numbers.
> But anyway, I think this has shown that postfix is indeed listening on port
> 25, and if you stop it, nothing is listening on port 25.
> > -----Original Message-----
> > From: MailScanner
> > [mailto:mailscanner-bounces+marek.gorny=bolix.pl at lists.mailscanner.info]
> > On Behalf Of Antony Stone Sent: Monday, September 4, 2017 1:05 PM
> > To: MailScanner Discussion <mailscanner at lists.mailscanner.info>
> > Subject: Re: Mailscanner 5.0.6-4 ant port 25 not listening
> > On Monday 04 September 2017 at 12:57:52, Marek Górny wrote:
> > > On my "prod version" OpenSUSE 13.2 with MailScanner 4.85.2
> > > postfix.service is disabled:
> > >
> > > and port 25 is listening:
> > >
> > > netstat -an |grep 25
> > > tcp 0 0 0.0.0.0:25 0.0.0.0:*
> > > LISTEN
> > Please add a "p" option and show us the output (as root):
> > # netstat -lpn | grep 25
> > Antony.
"Remember: the S in IoT stands for Security."
- Jan-Piet Mens
Please reply to the list;
please *don't* CC me.
More information about the MailScanner