On Mon, Sep 09, 2024 at 05:14:07PM +0200, Håkon Alstadheim via Postfix-users 
wrote:

> I got the attached report about a double bounce from my incoming postfix
> server "Postfix SMTP server: errors from
> nullbounce.com[116.202.14.127]:57394".

This wasn't a double-bounce, just an invalid SMTP recipient.  Rather,
your Postfix configuration sends detailed postmaster notices about
fairly routine events (errors).  Personally, I don't enable such
notices.  The default is:

    notify_classes = resource, software

> When I realize that this error is totally bogus, I want to blackhole
> that whole netblock.

An overreaction IMHO.  Just turn off the notifications.

> I see a double bounce, my heart jumps, I'm thinking "have I messed up
> my config?". I do NOT want bogus error-notifications.

See above.

> From: Mail Delivery System <[email protected]>
> Date: Mon,  9 Sep 2024 05:03:30 +0200 (CEST)
> Subject: Postfix SMTP server: errors from
>  nullbounce.com[116.202.14.127]:57394
> To: Postmaster <[email protected]>
> 
> Transcript of session follows.
> 
>  Out: 220 incoming.alstadheim.priv.no ESMTP Postfix (Debian/GNU)
>  In:  EHLO nullbounce.com
>  Out: 250-incoming.alstadheim.priv.no
>  Out: 250-PIPELINING
>  Out: 250-SIZE 512000000
>  Out: 250-VRFY
>  Out: 250-ETRN
>  Out: 250-STARTTLS
>  Out: 250-ENHANCEDSTATUSCODES
>  Out: 250-8BITMIME
>  Out: 250-SMTPUTF8
>  Out: 250 CHUNKING
>  In:  RSET
>  Out: 250 2.0.0 Ok
>  In:  MAIL FROM:<[email protected]>
>  Out: 250 2.1.0 Ok
>  In:  RCPT TO:<[email protected]>
>  Out: 550 5.1.1 <[email protected]>: Recipient address
>      rejected: User unknown in local recipient table
>  In:  QUIT
>  Out: 221 2.0.0 Bye

Completely routine delivery failure to a non-existent address, not worth
your or anyone else's time.  Just leave such traces in the logs, for
the rare case when you're troubleshooting inbound delivery issues.

-- 
    Viktor.
_______________________________________________
Postfix-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to