[pfx] Rate limiting a group of domains
I want to implement rate limiting based on the target server rather than by recipient domain. Specifically, I want to rate limit email sent to domains like yahoo.com, ymail.com, aol.com, myyahoo.com, and verizon.net as a group, since these domains appears to be handled by the same servers. This grouping should be done in case the receiving server does not discriminate based on domain for rate limiting purposes. (I'm not sure how yahoo works in this respect. I also want to do this for google, for which there can be a large group of related domains (eg gmail, googlemail, and users using their own domain with google workspace?). Currently, I have grouped the domains under the same transport, but if i'm not mistaken this approach rate limits each domain independently. Is there a way to group domains as a single entity for rate limiting purposes? iow i think i might want a particular transport to rate limit all the traffic it handles regardless of the domain ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: status=deferred (bounce or trace service failure)
I discovered I had bounce set to discard I don't recall why, it's been that way for years. Maybe to suppress backscatter. After i set it back to bounce' i got the expected 550 reject On Mon, Apr 22, 2024 at 2:09 AM Viktor Dukhovni via Postfix-users wrote: > > On Mon, Apr 22, 2024 at 12:21:01AM -0400, 785 243 via Postfix-users wrote: > > > Recently i'm seeing a few messages deferred with status=deferred > > (bounce or trace service failure) > > > > instead of status=deferred (host .. said: 450 ...) > > > > from the logs: > > > > postfix/smtp[272605]: warning: unexpected protocol > > delivery_request_protocol from private/bounce socket (expected: > > delivery_status_protocol) > > Your master.cf file has bad settings. Post the verbatim (no rewrapping > of whitespace of line breaks) output of "postconf -Mf". > > The "bounce" service entries should be: > > # Possibly chrooted, if Debian prefers that. > # > bounce unix - - n - 0 bounce > defer unix - - n - 0 bounce > trace unix - - n - 0 bounce > > Or perhaps the "bounce" service executable has been replaced with a link > to a delivery agent? The "real" bounce service supports the expected > protocol. > > -- > Viktor > ___ > Postfix-users mailing list -- postfix-users@postfix.org > To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] status=deferred (bounce or trace service failure)
Recently i'm seeing a few messages deferred with status=deferred (bounce or trace service failure) instead of status=deferred (host .. said: 450 ...) from the logs: postfix/smtp[272605]: warning: unexpected protocol delivery_request_protocol from private/bounce socket (expected: delivery_status_protocol) postfix/smtp[272605]: warning: read private/bounce socket: Application error postfix/smtp[272605]: status=deferred (bounce or trace service failure) This started right after upgrading the mx server (from ubuntu 20 focal to ubuntu 22 jammy, postconf mail_version now reports 3.6.4 (not sure before). But i have another mx server with similar config, on jammy and 3.6.4 for a long time. I don't have anything special in the configuration re deferred or bounce. Why would the status be "bounce or trace service failure" as opposed to the usual "host said: 450..." reply from the remote server? ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
