>> I have written postmas...@comcast.net and never received a reply. I have >> tried several times and will try again per your suggestion.
>Probably better to go the web form route: > https://postmaster.comcast.net -> https://spa.xfinity.com/report The web form results in an automated email saying, "Your ip addresses are not blocked." from Comcast. This is a difficult group to interact with. On Sun, Sep 22, 2024 at 11:27 PM Viktor Dukhovni via Postfix-users < postfix-users@postfix.org> wrote: > On Sun, Sep 22, 2024 at 07:29:30PM -0500, Greg Sims wrote: > > > The only traffic we send on these ip addresses is a Bible > > Daily Devotion email using double opt-in subscriptions. > > Despite the double opt-in, some receivers will report your mail as spam, > either because they fail to distinguish between "Trash" and "Junk" when > choosing to delete a message, or because they no longer wish to receive > the messages, and choose to have them filtered, rather than > unsub<nospace>scribe. > > > I have written postmas...@comcast.net and never received a reply. I > have > > tried several times and will try again per your suggestion. > > Probably better to go the web form route: > > https://postmaster.comcast.net -> https://spa.xfinity.com/report > > > I can see that the number of comcast deferrals reduces when I reduce the > > arrival rate of all our outbound email to postfix. One idea is to reduce > > the delivery rate of only comcast.net email using postfix. Is this > > suggested/possible? > > Yes, provided you can live with 1 message/sec or less (total under 86k > per day per transport). > > # > http://www.postfix.org/postconf.5.html#default_destination_rate_delay > transport_destination_rate_delay = 1 > > The actual parameter name depends on the name of the master.cf transport > to which you relegate comcast.net traffic. With a rate delay, the > destination concurrency is always equal to 1, (delivery spacing is > at least one second apart, so of course no concurrent deliveries). > > With rate delays, consider also: > > # > http://www.postfix.org/postconf.5.html#default_destination_concurrency_failed_cohort_limit > transport_destination_concurrency_failed_cohort_limit = 3 > > so that just a single delivery failure (failed or lost connection, > refused EHLO, ... ) does not throttle the transport. See also: > > http://www.postfix.org/TUNING_README.html#rope > http://www.postfix.org/SCHEDULER_README.html#concurrency_limitations > > These are qmgr(8) parameters, do not make the mistake of setting them in > master.cf as transport-specific overrides. > > -- > 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
