From: Lionel B. <lio...@bo...> - 2008-07-19 23:03:02
|
sql...@xe... a écrit, le 07/17/2008 06:19 PM : > Hello list, I have a problem with a user that sends their email through hostedmail.com being greylisted. They use their own domain name, but send through this hostedmail server. The problem is that every time the hostedmail server resends it is from a different IP address. I have added *.hostedemail.com OK > and hostedemail.com Not needed unless the servers IP resolve to this address. > to the clients_fqdn_whitelist.local file as well as the domain name which the user is using, Not needed : if I understand correctly hostedmail uses their domain name for their reverse lookups. > *.kimxxxxxx.net and kimxxxxxx.net. However, sqlgrey seems to just ignore this and continues to greylist all of these emails. I have seriously considered adding the IP range (216.40.44.) to clients_ip_whitelist.local, but that just isn't a good fix IMO. Here is an exert from my mail logs: > > Jul 13 11:12:29 mail postfix/smtpd[9730]: connect from smtprelay0085.hostedemail.com[216.40.44.85] > Jul 13 11:12:32 mail sqlgrey: grey: new: 216.40.44.85(216.40.44.85), ki...@th... -> xx...@ou... > Jul 13 11:12:32 mail postfix/smtpd[9730]: NOQUEUE: reject: RCPT from smtprelay0085.hostedemail.com[216.40.44.85]: 450 <xx...@ou...>: Recipient address rejected: Greylisted for 5 minutes; from=<ki...@th...> to=<xx...@ou...> proto=ESMTP helo=<smtprelay.hostedemail.com> > Jul 13 11:12:33 mail postfix/smtpd[9730]: disconnect from smtprelay0085.hostedemail.com[216.40.44.85] > Can you confirm that when you modified the clients_fqdn_whitelist.local file its content was reloaded (you should get a log line on the next message processing stating this) ? > Next day, log now shows this: > > Jul 14 11:35:44 mail sqlgrey: spam: 216.40.44.85: ki...@th... -> xx...@ou... at 20080713111232 > Given the log lines above this is normal : the mail was rejected and never seen again. > What is up? Can anyone enlighten me? > 3 possibilities : - you don't modify the right files, - SQLgrey doesn't detect the change -> try restarting it after modifying the whitelists, if the changes apply then, I'd like to know more about your system (OS, filesystem, Perl / SQLgrey versions, ....), - there's a bug in SQLgrey : can anyone confirm/deny this behaviour (I don't use local whitelists...). Lionel |