1. Forum
  2. USENET
  3. alt.os.linux.mint

  • odd postfix messages logged

    From Mike Scott@usenet.16@scottsonline.org.uk.invalid to alt.os.linux.mint on Wed Sep 23 15:32:15 2026
    From Newsgroup: alt.os.linux.mint

    Hi all, I've just started getting sequences like this:

    2026-09-23T15:15:33.327677+01:00 dax postfix/smtpd[773653]: connect from unknown[unknown]

    2026-09-23T15:15:33.335936+01:00 dax postfix/smtpd[773653]: lost
    connection after CONNECT from unknown[unknown]

    2026-09-23T15:15:33.336150+01:00 dax postfix/smtpd[773653]: disconnect
    from unknown[unknown] commands=0/0


    How can a server not know the connecting IP??? I'm puzzled.

    Comments?? Thanks.
    --
    Mike Scott
    Harlow, England

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.os.linux.mint on Thu Sep 24 02:08:39 2026
    From Newsgroup: alt.os.linux.mint

    On Wed, 23 Sep 2026 15:32:15 +0100, Mike Scott wrote:

    2026-09-23T15:15:33.327677+01:00 dax postfix/smtpd[773653]: connect from unknown[unknown]

    How can a server not know the connecting IP??? I'm puzzled.

    I think yourCOve got it configured to log the peer info in the format rCL-2dns-name-+[-2dns-name-+]rCY instead of rCLdns-name-+[-2ip-address-+]rCY. --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mike Scott@usenet.16@scottsonline.org.uk.invalid to alt.os.linux.mint on Thu Sep 24 07:08:39 2026
    From Newsgroup: alt.os.linux.mint

    On 24/09/2026 03:08, Lawrence DrCOOliveiro wrote:
    On Wed, 23 Sep 2026 15:32:15 +0100, Mike Scott wrote:

    2026-09-23T15:15:33.327677+01:00 dax postfix/smtpd[773653]: connect from unknown[unknown]

    How can a server not know the connecting IP??? I'm puzzled.

    I think yourCOve got it configured to log the peer info in the format rCL-2dns-name-+[-2dns-name-+]rCY instead of rCLdns-name-+[-2ip-address-+]rCY.

    Thanks, but no. Mostly I get things like

    118-208-201-71.tpgi.com.au[118.208.201.71]
    (where the reverse lookup works)

    or

    unknown[103.17.12.25]
    (where the reverse lookup fails. My own mobile phone co does this -
    really annoying!)

    But I've only ever seen
    unknown[unknown]

    over the last couple of days.
    --
    Mike Scott
    Harlow, England
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to alt.os.linux.mint on Thu Sep 24 23:46:42 2026
    From Newsgroup: alt.os.linux.mint

    On Thu, 24 Sep 2026 07:08:39 +0100, Mike Scott wrote:

    On 24/09/2026 03:08, Lawrence DrCOOliveiro wrote:

    On Wed, 23 Sep 2026 15:32:15 +0100, Mike Scott wrote:

    2026-09-23T15:15:33.327677+01:00 dax postfix/smtpd[773653]: connect from unknown[unknown]

    How can a server not know the connecting IP??? I'm puzzled.

    I think yourCOve got it configured to log the peer info in the format
    rCL-2dns-name-+[-2dns-name-+]rCY instead of rCLdns-name-+[-2ip-address-+]rCY.

    Thanks, but no. Mostly I get things like

    118-208-201-71.tpgi.com.au[118.208.201.71]
    (where the reverse lookup works)

    or

    unknown[103.17.12.25]
    (where the reverse lookup fails. My own mobile phone co does this -
    really annoying!)

    But I've only ever seen
    unknown[unknown]

    over the last couple of days.

    YourCOre right. I checked the log on my own VPS, and I see a few of
    those, too.

    A web search turned up this somewhat old discussion <https://mailing.postfix.users.narkive.com/MLhec3BE/lots-of-connections-from-unknown>,
    which says:

    A client connects but the connection is lost before postfix
    services it. This might be a sign of overload, or might be nothing
    important.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Mike Scott@usenet.16@scottsonline.org.uk.invalid to alt.os.linux.mint on Fri Sep 25 08:15:29 2026
    From Newsgroup: alt.os.linux.mint

    On 25/09/2026 00:46, Lawrence DrCOOliveiro wrote:
    On Thu, 24 Sep 2026 07:08:39 +0100, Mike Scott wrote:

    On 24/09/2026 03:08, Lawrence DrCOOliveiro wrote:

    On Wed, 23 Sep 2026 15:32:15 +0100, Mike Scott wrote:

    2026-09-23T15:15:33.327677+01:00 dax postfix/smtpd[773653]: connect from unknown[unknown]

    How can a server not know the connecting IP??? I'm puzzled.

    I think yourCOve got it configured to log the peer info in the format
    rCL-2dns-name-+[-2dns-name-+]rCY instead of rCLdns-name-+[-2ip-address-+]rCY.

    Thanks, but no. Mostly I get things like

    118-208-201-71.tpgi.com.au[118.208.201.71]
    (where the reverse lookup works)

    or

    unknown[103.17.12.25]
    (where the reverse lookup fails. My own mobile phone co does this -
    really annoying!)

    But I've only ever seen
    unknown[unknown]

    over the last couple of days.

    YourCOre right. I checked the log on my own VPS, and I see a few of
    those, too.

    A web search turned up this somewhat old discussion <https://mailing.postfix.users.narkive.com/MLhec3BE/lots-of-connections-from-unknown>,
    which says:

    A client connects but the connection is lost before postfix
    services it. This might be a sign of overload, or might be nothing
    important.

    I'd looked too, but found nothing useful. Thanks for checking: at least
    I'm Not Alone in this.
    --
    Mike Scott
    Harlow, England
    --- Synchronet 3.22a-Linux NewsLink 1.2