MTA like sendmail efficiently look up the MX for the recipient list and
batch them up, but Google doesn't allow it, leading to a logjam. I have a mailing list server and also a bulkmail server on which I both notice
stuff queueing up for retries quite often.
Is there any workaround for this in Sendmail yet?
Hi,
It's been 9 years since Google did whatever backend change causes this: 451-4.3.0 Multiple destination domains per transaction is unsupported.
Please
451 4.3.0 try again. fa9si788651wic.42 - gsmtp
MTA like sendmail efficiently look up the MX for the recipient list
and batch them up, but Google doesn't allow it, leading to a logjam.
I have a mailing list server and also a bulkmail server on which I
both notice stuff queueing up for retries quite often.
Is there any workaround for this in Sendmail yet?
451-4.3.0 Multiple destination domains per transaction is unsupported.
Is there any workaround for this in Sendmail yet?
Vincent Fox wrote:
451-4.3.0 Multiple destination domains per transaction is unsupported.It's fantastic that these big companies can make up whatever
rules they like...
Is there any workaround for this in Sendmail yet?Maybe turn off the m flag for the mailer?
m This mailer can send to multiple users on the same
host in one transaction.
There are other options, but this should be the easiest.
I was hoping something similar had come along for Sendmail.
m This mailer can send to multiple users on the same
host in one transaction.
Is this the same as max_rcpts 1?
Simple case I'm submitting an email:
67 *@gmail.com
1 *@foo.com. (MX is google)
12 *@bar.edu. ( ditto)
3 *@baz.org. (ditto)
If I move to splitting per.single recipient.... well I can do that but it's more to the inefficient end of things than I'd like.
On Thursday, June 10, 2021 at 10:50:01 AM UTC-7, Claus Aßmann wrote:
Vincent Fox wrote:
451-4.3.0 Multiple destination domains per transaction is unsupported.It's fantastic that these big companies can make up whatever
rules they like...
I agree, but they are a 900 lb gorilla and will not change. Most infuriating is how Google doesn't even respond to questions about why they do it. Non-Google apologists claim it is "anti-spam" which makes no sense at all. […]
Not yet - maybe you can write a patch? Unfortunately I don't have
much time to loook into this, hopefully someone does!
In any case, savvy users have started to notice and complain about delays into gmail hosted domains because of this.
In your sendmail.mc stick these in:
define(`SMTP_MAILER_MAXRCPTS', `1')dnl
define(`RELAY_MAILER_MAXRCPTS', `1')dnl
attention too and the ability to split envelopes by domain (something which Brandon Long thinks sendmail can do, but I can't figure out how) or perhaps
Try the following:...
Add this to your mc file in the proper places:
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 293 |
Nodes: | 16 (2 / 14) |
Uptime: | 236:42:55 |
Calls: | 6,624 |
Files: | 12,172 |
Messages: | 5,319,832 |