I don't quite get this. Your outbound MTA is grouping separate domains together into one queue based on MX?
Or is it trying to relay some other mail through Google when at least one recipient is hosted on a Google MX? Cheers, Al Iverson On Wed, Sep 25, 2019 at 4:27 AM Simon Lyall via mailop <mailop@mailop.org> wrote: > > > Just had a bunch of people at a domain get unsubscribed from this list. > Appears to be some weird Google rule (which probably made sense with they > were not the MX for 30% of all active domains) > > Any chance of them fixing it (or failing that a quick work-around for > mailman)? . It looks like people have been complaining about it for a few > years though. > > us...@example.com > SMTP error from remote mail server after RCPT TO:<us...@example.com>: > host alt3.aspmx.l.google.com [108.177.97.26]: > 451-4.3.0 Multiple destination domains per transaction is unsupported. > Please > 451 4.3.0 try again. w4si7917585pjr.54 - gsmtp: > retry timeout exceeded > us...@example.com > SMTP error from remote mail server after RCPT TO:<us...@example.com>: > host alt3.aspmx.l.google.com [108.177.97.26]: > 451-4.3.0 Multiple destination domains per transaction is unsupported. > Please > 451 4.3.0 try again. w4si7917585pjr.54 - gsmtp: > retry timeout exceeded > > > -- > Simon Lyall | Very Busy | Web: http://www.simonlyall.com/ > "To stay awake all night adds a day to your life" - Stilgar > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop -- al iverson // wombatmail // chicago http://www.aliverson.com http://www.spamresource.com _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop