Re: problem using greylist and gmail

5 msg	postfix/ldap - can one special_result_attribute...
2 msg	mailing list goes to bulk / spam folder
9 msg	SMTP Auth on multiple instances
4 msg	Auto-response, but not vacation
4 msg	bypassing reject_rbl_client for certain recipie...
12 msg	rewritten log
11 msg	Per user SPF and Anti Virus checks
9 msg	Instance on policies
2 msg	Removing internal mailers from headers
7 msg	Open Relay issue
1 msg	Messages not picked up from active queue
3 msg	Semantics question about myorigin
22 msg	mime, header_checks question

problem using greylist and gmail
\ nik600 (30 Mar 2008)
. \ mouss (30 Mar 2008)
. \ Sahil Tandon (30 Mar 2008)

9 msg	451 4.3.0 Error: queue file write error and vir...
5 msg	Network_biopair_interop errors
1 msg	what means error msg in auth.log (failed to map...
5 msg	problem upgrading from 2.4.5 to 2.5.1
5 msg	failover
13 msg	smtp_fallback_relay

Subject:	Re: problem using greylist and gmail
Group:	Postfix-users
From:	Sahil Tandon
Date:	30 Mar 2008

* nik600 <nik600> [2008-03-30 21:47:14 +0200]:

> Hi
>
> i've configured greylist on postfix 2.5.1 as described here
> http://www.postfix.org/SMTPD_POLICY_README.html#greylist
>
> The configuration works but i'm experiencing come problem with gmail,
> infact gmail as a very large number of mailserver so each time when it
> tries to deliver the mail the server has different ip and different
> fqdn.
>
> For example, i can see in the log:
>
>
> Mar 30 18:33:31 kumbemail postfix/smtpd[16097]: NOQUEUE: reject: RCPT
> from hs-out-0708.google.com[64.233.178.242]: 450 4.7.1 <xxx>:
> Recipient address rejected: Service is unavailable;
> from=<nik600> to=<xxx> proto=ESMTP
> helo=<hs-out-0708.google.com>
> Mar 30 18:40:07 kumbemail postfix/smtpd[16010]: NOQUEUE: reject: RCPT
> from wa-out-1112.google.com[209.85.146.176]: 450 4.7.1 <xxx>:
> Recipient address rejected: Service is unavailable;
> from=<nik600> to=<xxx> proto=ESMTP
> helo=<wa-out-1112.google.com>
> Mar 30 18:59:36 kumbemail postfix/smtpd[16915]: NOQUEUE: reject: RCPT
> from wx-out-0506.google.com[66.249.82.235]: 450 4.7.1 <xxx>: Recipient
> address rejected: Service is unavailable; from=<nik600>
> to=<xxx> proto=ESMTP helo=<wx-out-0506.google.com>
> Mar 30 19:30:59 kumbemail postfix/smtpd[18104]: NOQUEUE: reject: RCPT
> from wa-out-1112.google.com[209.85.146.180]: 450 4.7.1 <xxx>:
> Recipient address rejected: Service is unavailable;
> from=<nik600> to=<xxx> proto=ESMTP
> helo=<wa-out-1112.google.com>
> Mar 30 20:16:21 kumbemail postfix/smtpd[19338]: NOQUEUE: reject: RCPT
> from wx-out-0506.google.com[66.249.82.229]: 450 4.7.1 <xxx>: Recipient
> address rejected: Service is unavailable; from=<nik600>
> to=<xxx> proto=ESMTP helo=<wx-out-0506.google.com>
> Mar 30 21:14:01 kumbemail postfix/smtpd[21641]: NOQUEUE: reject: RCPT
> from wa-out-1112.google.com[209.85.146.177]: 450 4.7.1 <xxx>:
> Recipient address rejected: Service is unavailable;
> from=<nik600> to=<xxx> proto=ESMTP
> helo=<wa-out-1112.google.com>
>
> Do you know some workarounds?
> thanks

With postgrey, you can whitelist thusly:

> grep google postgrey_whitelist_clients
# google.com (big pool, reported by Matthias Dyer)
/^.*-out-.*\.google\.com$/

Instead of greylisting every new sender/client, have you considered selectively
greylisting only those senders/clients that, based on some other rules, appear
suspicious?

--
Sahil Tandon <sahil>