1 Topic by guigouz

  • guigouz
  • Member
  • Offline
  • Registered: 2010-06-15
  • Posts: 7

Topic: Greylist delaying email from google

Hello, I'm having some issues with the google and greylisting (may happen to other providers too)
In this case, @bravado.com.br is a google-hosted domain and @prosoma.com.br is an iRedMail domain

Aug 19 10:31:56 hosting policyd: rcpt=3530463, greylist=new, host=209.85.218.42 (mail-yi0-f42.google.com), from=xxxxxx@bravado.com.br, to=xxxxx@prosoma.com.br, size=0
Aug 19 10:31:56 hosting postfix/smtpd[24672]: NOQUEUE: reject: RCPT from mail-yi0-f42.google.com[209.85.218.42]: 450 4.7.1 <xxxxxx@prosoma.com.br>: Recipient address rejected: Policy Rejection- Please try later.; from=<xxxx@bravado.com.br> to=<xxxxxx@prosoma.com.br> proto=ESMTP helo=<mail-yi0-f42.google.com>
Aug 19 10:38:11 hosting policyd: rcpt=3530642, greylist=new, host=209.85.160.170 (mail-gy0-f170.google.com), from=xxxxxx@bravado.com.br, to=xxxxxx@prosoma.com.br, size=0
Aug 19 10:38:11 hosting postfix/smtpd[8063]: NOQUEUE: reject: RCPT from mail-gy0-f170.google.com[209.85.160.170]: 450 4.7.1 <xxxxxx@prosoma.com.br>: Recipient address rejected: Policy Rejection- Please try later.; from=<xxxxxxx@bravado.com.br> to=<xxxxxx@prosoma.com.br> proto=ESMTP helo=<mail-gy0-f170.google.com>

The mail first arrived from 209.85.218.42 (mail-yi0-f42.google.com), and the second time from 209.85.160.170 (mail-gy0-f170.google.com), which denied it again.

Is there a fix for this situation, or maybe a way to whitelist major providers like google ?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by ZhangHuangbin

  • ZhangHuangbin
  • ZhangHuangbin
  • iRedMail Developers
  • Offline
  • Registered: 2009-05-06
  • Posts: 30,768

Re: Greylist delaying email from google

guigouz wrote:

The mail first arrived from 209.85.218.42 (mail-yi0-f42.google.com), and the second time from 209.85.160.170 (mail-gy0-f170.google.com), which denied it again.

Check section "Greylist Opt-in / Opt-out" in Policyd doc:
http://policyd.sourceforge.net/readme.html

guigouz wrote:

Is there a fix for this situation, or maybe a way to whitelist major providers like google ?

Not a good idea, spammers send out many SPAM with Gmail too.

3 Reply by guigouz

  • guigouz
  • Member
  • Offline
  • Registered: 2010-06-15
  • Posts: 7

Re: Greylist delaying email from google

I'm still having issues with greylisting

First try:
Aug 31 11:27:59 hosting policyd: rcpt=122983, greylist=new, host=201.76.49.243 (hm1481-31.locaweb.com.br), from=xxxxx@ymidia.com.br, to=xxxx@prosoma.com.br, size=0
Aug 31 11:27:59 hosting postfix/smtpd[16781]: NOQUEUE: reject: RCPT from hm1481-31.locaweb.com.br[201.76.49.243]: 450 4.7.1 <xxxx@prosoma.com.br>: Recipient address rejected: Policy Rejection- Please try later.; from=<xxxx@ymidia.com.br> to=<xxxx@prosoma.com.br> proto=ESMTP helo=<hm1481-31.locaweb.com.br>

Second try:
Aug 31 11:33:12 hosting policyd: rcpt=123138, greylist=new, host=201.76.49.91 (hm1479-21.locaweb.com.br), from=xxxx@ymidia.com.br, to=xxxx@prosoma.com.br, size=0
Aug 31 11:33:18 hosting postfix/smtpd[28251]: NOQUEUE: reject: RCPT from hm1479-21.locaweb.com.br[201.76.49.91]: 450 4.7.1 <xxxx@prosoma.com.br>: Recipient address rejected: Policy Rejection- Please try later.; from=<xxxx@ymidia.com.br> to=<xxxx@prosoma.com.br> proto=ESMTP helo=<hm1479-21.locaweb.com.br>

Although the IP is different, I have policyd configured with


#
# greylist host address:                              default: off
#
#   by default policyd will only use 3 octets when dealing
#   with greylisting information. this allows policyd to
#   work around roaming MTAs which are known to move mail
#   between different queues after a 450/temp rejection.
#   
#   some dont want this functionality and wish to be more
#   aggressive when receiving mail. example of the format
#   of the ips stored:
#
#   1=192
#   2=192.168
#   3=192.168.0            <- default/recommended
#   4=192.168.0.1
#
GREYLIST_HOSTADDR=2


Any ideas on what else I could verify ?