Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Google's 4.3.0 Multiple destination domains per transaction is unsupported

3,997 views
Skip to first unread message

Stephen Borrill

unread,
May 16, 2014, 8:41:44 AM5/16/14
to
Domains hosted by Google Apps use the same MX servers and sendmail will
deliver mail to multiple recipients with the same MX in a single
transaction (sensibly). Unfortunately, Google have seen fit to reject
recipients with a domains that do not match the first on in the
transaction, i.e.

send to us...@domain1.com - OK
send to us...@domain2.com - OK
send to us...@domain1.com and us...@domain1.com - OK
send to us...@domain1.com and us...@domain2.com - REJECT 2nd rcpt

Message is:
451-4.3.0 Multiple destination domains per transaction is unsupported.
Please
451 4.3.0 try again. fa9si788651wic.42 - gsmtp

Yes, I can work round with SMTP_MAILER_MAXRCPTS=1, but that's very
suboptimal. Similarly, I could set up a new mailer with r=1 and then use
mailertable, but this would require an entry for each affected domain.
Is there a way to either:
- tell sendmail to batch by domain rather than by MX
- select mailers on the basis of MX server being connected to (so you
could blacklist Google's MX servers)

--
Stephen

Message has been deleted

Stephen Borrill

unread,
May 19, 2014, 7:30:13 AM5/19/14
to
On 17/05/2014 09:07, Ralf Döblitz wrote:
> Stephen Borrill <gsbo...@precedence.co.uk> wrote:
> [...]
>> Message is:
>> 451-4.3.0 Multiple destination domains per transaction is unsupported.
>> Please
>> 451 4.3.0 try again. fa9si788651wic.42 - gsmtp
>>
>> Yes, I can work round with SMTP_MAILER_MAXRCPTS=1, but that's very
>> suboptimal.
>
> Why do you feel the need to do anything at all? All recipients in the
> first domain will have their mails accepted and the rest will stay in
> the queue as it is only a temporary error. Just process the queue again
> soon (e.g. -qp1m) and everything will be fine.

Mails may be sent to many affected domains, the default retry periods
mean it may be some time before the mail is sent to all recipients
(without manual intervention as above) and end-users get warning
messages. I suppose that tweaking notification settings and the initial
retry period may improve things slightly.

--
Stephen

Andrzej Adam Filip

unread,
May 29, 2014, 3:42:54 PM5/29/14
to
Stephen Borrill <gsbo...@precedence.co.uk> wrote:
> [...]
> Is there a way to either:
> [...]
> - select mailers on the basis of MX server being connected to (so you
> could blacklist Google's MX servers)

A few lines in sendmail.cf may select special mailer based on bestmx map
lookup.

http://etutorials.org/Server+Administration/Sendmail/Part+III+The+Configuration+File/Chapter+23.+The+K+Database-Map+Configuration+Command/bestmx/
The bestmx database-map type looks up a hostname as the key and returns the
current, single best MX record as the value.


--
[Andrew] Andrzej A. Filip - https://www.linkedin.com/in/andfil
0 new messages