postfix not listening on 25/587

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

postfix not listening on 25/587

doug
I am upgrading from postfix-2.8.7,1 and cyrus-imapd-2.3.18 to
postfix-3.5.6,1 and cyrus-imapd30-3.0.14. The old system uses sasldb
authentication, the new one MySQL. This is on FreeBSD.

I have compared the conf files on two addition postfix systems and can see
no differences of consequence. I am not sure which files or parts thereof
to show. I am kind of surprised postfix can be encouraged not to listen on
these ports. I am quite lost and can supply whatever information that will
help anyone with a idea on how I messed this up.

_____
Douglas Denault
http://www.safeport.com
[hidden email]
Voice: 301-217-9220
   Fax: 301-217-9277
Reply | Threaded
Open this post in threaded view
|

Re: postfix not listening on 25/587

Noel Jones-2
On 8/30/2020 2:57 PM, Doug Denault wrote:

> I am upgrading from postfix-2.8.7,1 and cyrus-imapd-2.3.18 to
> postfix-3.5.6,1 and cyrus-imapd30-3.0.14. The old system uses sasldb
> authentication, the new one MySQL. This is on FreeBSD.
>
> I have compared the conf files on two addition postfix systems and
> can see no differences of consequence. I am not sure which files or
> parts thereof to show. I am kind of surprised postfix can be
> encouraged not to listen on these ports. I am quite lost and can
> supply whatever information that will help anyone with a idea on how
> I messed this up.
>
> _____
> Douglas Denault
> http://www.safeport.com
> [hidden email]
> Voice: 301-217-9220
>    Fax: 301-217-9277


Likely is postfix is failing to start, with clues in the logfile.
http://www.postfix.org/DEBUG_README.html#logging

If you need to ask for further help:
http://www.postfix.org/DEBUG_README.html#mail



   -- Noel Jones
Reply | Threaded
Open this post in threaded view
|

Re: postfix not listening on 25/587

doug
On Sun, 30 Aug 2020, Noel Jones wrote:

> On 8/30/2020 2:57 PM, Doug Denault wrote:
>> I am upgrading from postfix-2.8.7,1 and cyrus-imapd-2.3.18 to
>> postfix-3.5.6,1 and cyrus-imapd30-3.0.14. The old system uses sasldb
>> authentication, the new one MySQL. This is on FreeBSD.
>>
>> I have compared the conf files on two addition postfix systems and can see
>> no differences of consequence. I am not sure which files or parts thereof
>> to show. I am kind of surprised postfix can be encouraged not to listen on
>> these ports. I am quite lost and can supply whatever information that will
>> help anyone with a idea on how I messed this up.
>>
>> _____
>> Douglas Denault
>> http://www.safeport.com
>> [hidden email]
>> Voice: 301-217-9220
>>    Fax: 301-217-9277
>
>
> Likely is postfix is failing to start, with clues in the logfile.
> http://www.postfix.org/DEBUG_README.html#logging
>
> If you need to ask for further help:
> http://www.postfix.org/DEBUG_README.html#mail

Thank you for your thought, but not exactly. Postfix sort starts, cyrus is
all there:

working system:
    lighthouse:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
    postfix  smtpd      98709 6  tcp4   *:25                  *:*
    postfix  smtpd      98656 6  tcp4   *:25                  *:*
    postfix  smtpd      98656 19 tcp4   127.0.0.1:53654
    127.0.0.1:10023
    postfix  smtpd      98612 6  tcp4   *:25                  *:*
    root     master     52014 12 tcp4   *:25                  *:*
    root     master     52014 16 tcp4   *:587                 *:*

The one in question
    freeport:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
    root     master     3938  13 tcp4   *:25                  *:*
    root     master     3938  17 tcp4   *:587                 *:*

Any thought much appreciated. The only difference between two of the
other postfix/cyrus systems: one use sasldb, the other kerberos. The Not
working one uses mysql. There are some cyrus gliches not relevant to
this list. On the post fix front, the system can receive email, that's
what master does, it can not send email. Apparently what postfix does.

Honestly as for RTFM, been there, done that. Did little for mysql all
help there came from /var/log/messages and sql errors.

_____
Douglas Denault
http://www.safeport.com
[hidden email]
Voice: 301-217-9220
   Fax: 301-217-9277
Reply | Threaded
Open this post in threaded view
|

Re: postfix not listening on 25/587

Bill Cole-3
On 30 Aug 2020, at 20:24, Doug Denault wrote:

> On Sun, 30 Aug 2020, Noel Jones wrote:
>
>> On 8/30/2020 2:57 PM, Doug Denault wrote:
>>> I am upgrading from postfix-2.8.7,1 and cyrus-imapd-2.3.18 to
>>> postfix-3.5.6,1 and cyrus-imapd30-3.0.14. The old system uses sasldb
>>> authentication, the new one MySQL. This is on FreeBSD.
>>>
>>> I have compared the conf files on two addition postfix systems and
>>> can see no differences of consequence. I am not sure which files or
>>> parts thereof to show. I am kind of surprised postfix can be
>>> encouraged not to listen on these ports. I am quite lost and can
>>> supply whatever information that will help anyone with a idea on how
>>> I messed this up.
>>>
>>
>>
>> Likely is postfix is failing to start, with clues in the logfile.
>> http://www.postfix.org/DEBUG_README.html#logging
>>
>> If you need to ask for further help:
>> http://www.postfix.org/DEBUG_README.html#mail
>
> Thank you for your thought, but not exactly. Postfix sort starts,
> cyrus is all there:
>
> working system:
>    lighthouse:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
>    postfix  smtpd      98709 6  tcp4   *:25                  *:*
>    postfix  smtpd      98656 6  tcp4   *:25                  *:*
>    postfix  smtpd      98656 19 tcp4   127.0.0.1:53654
>    127.0.0.1:10023
>    postfix  smtpd      98612 6  tcp4   *:25                  *:*
>    root     master     52014 12 tcp4   *:25                  *:*
>    root     master     52014 16 tcp4   *:587                 *:*
>
> The one in question
>    freeport:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
>    root     master     3938  13 tcp4   *:25                  *:*
>    root     master     3938  17 tcp4   *:587                 *:*

That's absolutely normal. Postfix's 'master' process only spawns smtpd
processes as needed to handle SMTP sessions. As shown, it listens on any
ports that need persistent listeners, and hands off connections to child
processes.

> Any thought much appreciated. The only difference between two of the
> other postfix/cyrus systems: one use sasldb, the other kerberos. The
> Not working one uses mysql. There are some cyrus gliches not relevant
> to this list. On the post fix front, the system can receive email,
> that's what master does, it can not send email. Apparently what
> postfix does.

So, your chosen subject makes no sense. The master process is part of
Postfix, and it is what listens on ports 25 and 587.

> Honestly as for RTFM, been there, done that.

The bit of the documentation that you seem to have ignored is what Noel
mentioned:  http://www.postfix.org/DEBUG_README.html#mail

Actual log entries and actual configuration are essential information.


--
Bill Cole
[hidden email] or [hidden email]
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not For Hire (currently)
Reply | Threaded
Open this post in threaded view
|

can not send mail was Postfix users not listening ...

doug
On Mon, 31 Aug 2020, Bill Cole wrote:

> On 30 Aug 2020, at 20:24, Doug Denault wrote:

>> working system:
>>    lighthouse:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
>>    postfix  smtpd      98709 6  tcp4   *:25                  *:*
>>    postfix  smtpd      98656 6  tcp4   *:25                  *:*
>>    postfix  smtpd      98656 19 tcp4   127.0.0.1:53654
>>    127.0.0.1:10023
>>    postfix  smtpd      98612 6  tcp4   *:25                  *:*
>>    root     master     52014 12 tcp4   *:25                  *:*
>>    root     master     52014 16 tcp4   *:587                 *:*
>>
>> The one in question
>>    freeport:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
>>    root     master     3938  13 tcp4   *:25                  *:*
>>    root     master     3938  17 tcp4   *:587                 *:*
>
> That's absolutely normal. Postfix's 'master' process only spawns smtpd
> processes as needed to handle SMTP sessions. As shown, it listens on any
> ports that need persistent listeners, and hands off connections to child
> processes.
>
> Actual log entries and actual configuration are essential information.

Thanks, I will look at the debugging link, perhaps I've not been there. BTW
I fully understand it is likely I've done something really dumb. In
comparing the setup with a kerberos system, one running webmail and a older
version of the setup I am testing all work and I can not see/find any
differences.

I was not clear. The system receives email just fine. It will not send.
There are no log entries. The above output is from sockstat. I do not know
what or if the linux equivalent is. On all the working systems the
processes listed as postfix are present. They seem to be needed/used by the
email clients to communicate with postfix to send mail. The sockstat output
from a running system:

USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN ADDRESS
postfix  smtp       7130  6  stream private/smtp
postfix  smtp       7130  7  dgram  -> /var/run/logpriv
postfix  smtpd      7129  6  tcp4   *:587                 *:*
postfix  smtpd      7129  7  dgram  -> /var/run/logpriv
postfix  smtpd      7129  18 stream -> private/anvil
postfix  lmtp       7070  6  stream private/lmtp
postfix  lmtp       7070  7  dgram  -> /var/run/logpriv
postfix  local      7069  6  stream private/local
postfix  local      7069  7  dgram  -> /var/run/logpriv
postfix  cleanup    7068  6  stream public/cleanup
postfix  cleanup    7068  7  dgram  -> /var/run/logpriv
postfix  cleanup    7068  16 stream -> private/rewrite
postfix  smtpd      7067  6  tcp4   *:25                  *:*
postfix  smtpd      7067  7  dgram  -> /var/run/logpriv
postfix  smtpd      7067  18 stream -> private/anvil
postfix  smtpd      7067  20 tcp4   127.0.0.1:57874       127.0.0.1:10023
postfix  cleanup    7066  6  stream public/cleanup
postfix  cleanup    7066  7  dgram  -> /var/run/logpriv
postfix  cleanup    7062  6  stream public/cleanup
postfix  cleanup    7062  7  dgram  -> /var/run/logpriv
postfix  cleanup    7062  16 stream -> private/rewrite
postfix  trivial-re 7027  6  stream private/rewrite
postfix  trivial-re 7027  7  dgram  -> /var/run/logpriv
postfix  trivial-re 7027  128 streamprivate/rewrite
postfix  trivial-re 7027  129 streamprivate/rewrite
postfix  trivial-re 7027  129 streamprivate/rewrite
postfix  trivial-re 7027  131 streamprivate/rewrite
postfix  trivial-re 7027  132 streamprivate/rewrite
postfix  smtpd      6994  6  tcp4   *:25                  *:*
postfix  smtpd      6994  7  dgram  -> /var/run/logpriv
postfix  smtpd      6994  17 stream -> private/tlsmgr
postfix  smtpd      6994  18 stream -> private/rewrite
postfix  smtpd      6994  19 stream -> private/anvil
postfix  smtpd      6994  20 tcp4   127.0.0.1:48692       127.0.0.1:10023
postfix  lmtp       6991  6  stream private/lmtp
postfix  lmtp       6991  7  dgram  -> /var/run/logpriv
postfix  lmtp       6990  6  stream private/lmtp
postfix  lmtp       6990  7  dgram  -> /var/run/logpriv
postfix  local      6989  6  stream private/local
postfix  local      6989  7  dgram  -> /var/run/logpriv
postfix  local      6988  6  stream private/local
postfix  local      6988  7  dgram  -> /var/run/logpriv
postfix  lmtp       6957  6  stream private/lmtp
postfix  lmtp       6957  7  dgram  -> /var/run/logpriv
postfix  local      6956  6  stream private/local
postfix  local      6956  7  dgram  -> /var/run/logpriv
postfix  smtpd      6936  6  tcp4   *:25                  *:*
postfix  smtpd      6936  7  dgram  -> /var/run/logpriv
postfix  smtpd      6936  17 stream -> private/tlsmgr
postfix  smtpd      6936  18 stream -> private/anvil
postfix  smtpd      6936  19 stream -> private/rewrite
postfix  smtpd      6936  20 tcp4   127.0.0.1:59645       127.0.0.1:10023
postfix  smtpd      6935  6  tcp4   *:25                  *:*
postfix  smtpd      6935  7  dgram  -> /var/run/logpriv
postfix  smtpd      6935  17 stream -> private/tlsmgr
postfix  smtpd      6935  18 stream -> private/anvil
postfix  pickup     6617  7  dgram  -> /var/run/logpriv
postfix  anvil      60373 6  stream private/anvil
postfix  anvil      60373 7  dgram  -> /var/run/logpriv
postfix  anvil      60373 128 streamprivate/anvil
postfix  anvil      60373 129 streamprivate/anvil
postfix  anvil      60373 131 streamprivate/anvil
postfix  anvil      60373 132 streamprivate/anvil
postfix  anvil      60373 136 streamprivate/anvil
postfix  tlsmgr     52038 6  stream private/tlsmgr
postfix  tlsmgr     52038 7  dgram  -> /var/run/logpriv
postfix  tlsmgr     52038 128 streamprivate/tlsmgr
postfix  tlsmgr     52038 129 streamprivate/tlsmgr
postfix  tlsmgr     52038 130 streamprivate/tlsmgr
postfix  qmgr       52016 7  dgram  -> /var/run/logpriv

The postconf output is 1,000 lines. I've done a full compare with the
working system finding nothing I will work on that and probably not bother
anyone here further. I was going for things to look at and seem to have
gotten what's available here. Thanks

_____
Douglas Denault
http://www.safeport.com
[hidden email]
Voice: 301-217-9220
   Fax: 301-217-9277
Reply | Threaded
Open this post in threaded view
|

Re: can not send mail was Postfix users not listening ...

Bill Cole-3
On 31 Aug 2020, at 13:12, Doug Denault wrote:

> On Mon, 31 Aug 2020, Bill Cole wrote:
>
>> On 30 Aug 2020, at 20:24, Doug Denault wrote:
>
>>> working system:
>>>    lighthouse:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
>>>    postfix  smtpd      98709 6  tcp4   *:25                  *:*
>>>    postfix  smtpd      98656 6  tcp4   *:25                  *:*
>>>    postfix  smtpd      98656 19 tcp4   127.0.0.1:53654
>>>    127.0.0.1:10023
>>>    postfix  smtpd      98612 6  tcp4   *:25                  *:*
>>>    root     master     52014 12 tcp4   *:25                  *:*
>>>    root     master     52014 16 tcp4   *:587                 *:*
>>>
>>> The one in question
>>>    freeport:~> sockstat | egrep "postfix|master" | egrep ":[2\5]+"
>>>    root     master     3938  13 tcp4   *:25                  *:*
>>>    root     master     3938  17 tcp4   *:587                 *:*
>>
>> That's absolutely normal. Postfix's 'master' process only spawns
>> smtpd processes as needed to handle SMTP sessions. As shown, it
>> listens on any ports that need persistent listeners, and hands off
>> connections to child processes.
>>
>> Actual log entries and actual configuration are essential
>> information.
>
> Thanks, I will look at the debugging link, perhaps I've not been
> there.

That specific link explains how best to get useful support from this
list. It's also likely to be on your local machine, somewhere like
/usr/local/share/doc/postfix/DEBUG_README.

> BTW I fully understand it is likely I've done something really dumb.

Not really. It is more likely to be a result of the changes in Postfix
*OR* in the surrounding environments between your old and new systems.
2.8->3.5 is most of a decade, and if you're also going FreeBSD 8->12
you've got a large collection of changes that could cause problems
inside and outside of Postfix, mostly outside. e.g. packet filter config
differences between your old machine's ipfw and whichever on-host
'firewall' you might be using on the new system.

> In comparing the setup with a kerberos system, one running webmail and
> a older version of the setup I am testing all work and I can not
> see/find any differences.

That is why other eyes are useful. There has been substantial change
between 2.8 and 3.5, and we might see something relevant, if we were
looking at anything tangible.


> I was not clear. The system receives email just fine. It will not
> send. There are no log entries.

I find that surprising. Are you looking at /var/log/maillog? That is the
normal place to find log messages from Postfix. The default
/etc/syslog.conf on the base FreeBSD install since forever has included
a line like this:


    mail.info    /var/log/maillog

If you can stop and start postfix with nothing showing up in
/var/log/maillog, you have a deeper problem than Postfix.

> The above output is from sockstat. I do not know what or if the linux
> equivalent is.

The linux version of netstat has some of sockstat's features that are
lacking in FreeBSD's netstat, such as process correlation. Not really
relevant.

> On all the working systems the processes listed as postfix are
> present. They seem to be needed/used by the email clients to
> communicate with postfix to send mail.

Not exactly. If a Postfix server is idle, it will have a master, qmgr,
and pickup process running and maybe a tlsmgr and an anvil process if it
has been active recently. All other processes are transient, as are
their sockets.


> The sockstat output from a running system:
>
> USER     COMMAND    PID   FD PROTO  LOCAL ADDRESS         FOREIGN
> ADDRESS
> postfix  smtp       7130  6  stream private/smtp
[ long list elided ...]

> The postconf output is 1,000 lines.

Which is why the DEBUG_README section suggests using 'postconf -nf' to
just show the non-default settings.

> I've done a full compare with the working system finding nothing I
> will work on that and probably not bother anyone here further. I was
> going for things to look at and seem to have gotten what's available
> here. Thanks

The limit on the help you can get here is set by how much detail you can
provide about the problem. If you can't find where the log messages
which Postfix sends are going, it is going to be exceedingly difficult
for anyone to discern what exactly is failing to work.


--
Bill Cole
[hidden email] or [hidden email]
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not For Hire (currently)
Reply | Threaded
Open this post in threaded view
|

Re: can not send mail was Postfix users not listening ...

Noel Jones-2
In reply to this post by doug
On 8/31/2020 12:12 PM, Doug Denault wrote:

>
> I was not clear. The system receives email just fine. It will not
> send. There are no log entries. The above output is from sockstat.

Don't waste your time looking at listening sockets/ports for
outgoing connections that are never made.

If there are no log entries, fix that. Whatever problem you're
having can almost certainly be solved by normal non-debug logging.

Maybe smtp (NOT smtpd) process is failing to start due to some
library conflict or missing table. If that's the problem, it will be
noted in the logs.

>
> The postconf output is 1,000 lines. I've done a full compare with

Staring at postconf (or somewhat easier, postconf -n) output is
unlikely to fix this without clues in the log of what the problem is.

Start here:
http://www.postfix.org/DEBUG_README.html#logging

If you need more help from us:
http://www.postfix.org/DEBUG_README.html#mail



   -- Noel Jones
Reply | Threaded
Open this post in threaded view
|

Re: can not send mail was Postfix users not listening ...

doug
On Mon, 31 Aug 2020, Noel Jones wrote:

> Staring at postconf (or somewhat easier, postconf -n) output is unlikely to
> fix this without clues in the log of what the problem is.
>
> Start here:
> http://www.postfix.org/DEBUG_README.html#logging
>
> If you need more help from us:
> http://www.postfix.org/DEBUG_README.html#mail

Thank you, links did the trick as you suggested

_____
Douglas Denault
http://www.safeport.com
[hidden email]
Voice: 301-217-9220
   Fax: 301-217-9277