Or rewrite the return path and visible from so that they're you instead of the original sender. The forwarding is failing SPF checks, your MTA or process could be doing something to invalidate DKIM signatures, and you're potentially running afoul of authentication failures and DMARC policies.
I have a number of users for whom I forward mail to their custom domain on to their real Gmail mailboxes. I haven't had any Gmail issues in as long as I can remember. I rewrite the headers to make my server the mail originator and I drop the original from into the Reply-to. Here's my laughably low tech shell script that gets the job done: http://xnnd.com/deanfwd.sh.txt I'm using Maildir with Postfix, so I just run this from cron periodically to check for any pending mail for my friend. If found, the script picks it up, rewrites the headers, forwards it to my friend. As I said, I've been running some version of this script for multiple users 'round these parts with no issues for a long time. Cheers, Al Iverson -- Al Iverson - Minneapolis - (312) 275-0130 Simple DNS Tools since 2008: xnnd.com www.spamresource.com & aliverson.com On Fri, Dec 11, 2015 at 10:13 PM, <frnk...@iname.com> wrote: > I'd recommend that rather than forward messages to Google that you have > those Google accounts POP the messages from smokva.net. > > Frank > > -----Original Message----- > From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Petar > Bogdanovic > Sent: Thursday, December 10, 2015 9:44 AM > To: mailop@mailop.org > Subject: [mailop] crippling gmail rate limit > > Hi, > > On the 6. of december, all google MTAs started rate limiting deliveries > from our MTA (dig mx smokva.net) to gmail- and gapps for work users: > > Our system has detected an unusual rate of unsolicited mail > originating from your IP address. To protect our users from spam, > mail sent from your IP address has been temporarily rate limited. > Please visit https://support.google.com/mail/answer/81126 to review > our Bulk Email Senders Guidelines. > > The sending domain in question hosts a handful of users, most of them > forwarding all their messages to gmail. During the past 7 days, this > domain has successfully delivered 45 messages to google MTAs. > > Based on the envelope sender addresses it is very likely that the vast > mojority these messages were ham. > > > I contacted google through their on-line form but am not holding my > breath. The queue is still growing and the first queued messages are > approaching max. queue lifetime (5d). > > Any ideas are welcome. > > A few technical details: The sending MTA, when forwarding, used to > rewrite envelope senders (because that's what seemed reasonable in an > SPF world) but I have disabled that practice based on google's own > recommendations. Outgoing messages are not DKIM signed, the MTA's IP > is listed in dnswl (which is a whitelist) and absent in any public > blacklist. > > > Thanks, > > Petar Bogdanovic > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
