Re: Gmail specific transport

2022-06-17 Thread Wietse Venema
Viktor Dukhovni: > On Thu, Jun 16, 2022 at 07:35:20PM -0400, Wietse Venema wrote: > > > Bob Proulx: > > > Is there a transport mapping equivalent to match against the MX host > > > instead of against the the recipient address? That's really what is > > > desired here. I didn't think such a

Re: Gmail specific transport

2022-06-16 Thread Bob Proulx
Viktor Dukhovni wrote: > Transport resolutiont that does remote DNS lookups will be a prohibitive > performance bottleneck on systems delivering a steady non-trivial stream > of mail. The queue manager is not multi-threaded, and each recipient > domain can/will incur some delay. Yes. That would

Re: Gmail specific transport

2022-06-16 Thread Viktor Dukhovni
On Thu, Jun 16, 2022 at 07:35:20PM -0400, Wietse Venema wrote: > Bob Proulx: > > Is there a transport mapping equivalent to match against the MX host > > instead of against the the recipient address? That's really what is > > desired here. I didn't think such a feature existed yet. > > it

Re: Gmail specific transport

2022-06-16 Thread Wietse Venema
Bob Proulx: > Is there a transport mapping equivalent to match against the MX host > instead of against the the recipient address? That's really what is > desired here. I didn't think such a feature existed yet. it would require a Postfix lookup table that returns MX hosts for a domain,

Re: Gmail specific transport

2022-06-16 Thread Bob Proulx
Jaroslaw Rafa wrote: > Dnia 15.06.2022 o godz. 22:00:45 Bob Proulx pisze: > > It is interesting that mail to domains hosted at google that are not > > @gmail.com but other named domains delivered okay. Google accepted > > the exact same message to them fine. > > It can be that some domains that

Re: Gmail specific transport

2022-06-16 Thread Bob Proulx
Viktor Dukhovni wrote: > No, those settings are used by the queue manager to schedule deliveries > assigned to various delivery agent processes, the delivery agents > themselves only see one message at a time and can do little to affect > concurrency, and related limits. > > So these settings go

Re: Gmail specific transport

2022-06-16 Thread Jaroslaw Rafa
Dnia 15.06.2022 o godz. 22:00:45 Bob Proulx pisze: > It is interesting that mail to domains hosted at google that are not > @gmail.com but other named domains delivered okay. Google accepted > the exact same message to them fine. It can be that some domains that are actually hosting their email

Re: Gmail specific transport

2022-06-15 Thread Viktor Dukhovni
On Wed, Jun 15, 2022 at 10:00:45PM -0600, Bob Proulx wrote: > But did I get it right? > > In master.cf: > > gmail unix - - y - - smtp > -o gmail_destination_concurrency_limit=2 > -o gmail_destination_rate_delay=1s > -o gmail_destination_recipient_limit=2 No, those

Gmail specific transport

2022-06-15 Thread Bob Proulx
I have inherited being a caretaker of a sleepy local mailing list. It has about 200 subscribers on it. Unsurprisingly a large percentage of the subscribers use Google's Gmail. Google sometimes will decide that a message will not be accepted. It will log the error like this. Jun 15