| View previous topic :: View next topic |
| Author |
Message |
baboo
Senior Member
Joined: 04 Sep 2007
Posts: 676
|
 Posted: Mon Jul 12, 2010 9:02 pm Post subject: sqlgrey and yahoo.com |
 |
|
I have a friend on yahoo mail. When she sends me mail sqlgrey grey list for 5mins.. However, if she replies again to reject yahoo won't deliver.
I read docs at sqlgrey and they say it should auto deliver the next time its sent, but it doesn't.
Anyone else have this happen? |
|
| Back to top |
|
gerasimos_h
Site Admin
Joined: 09 Aug 2007
Posts: 1757
Location: Greece
|
| Posted: Mon Jul 12, 2010 9:09 pm Post subject: |
|
|
Have you try to add yahoo.com IP's to /etc/sqlgrey/clients_ip_whitelist.local for not greylisting them.
gerasimos_h
_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com |
|
| Back to top |
|
baboo
Senior Member
Joined: 04 Sep 2007
Posts: 676
|
| Posted: Mon Jul 12, 2010 9:36 pm Post subject: |
|
|
| thanks for input. I am trying that now, but will I have to do this for major sites responding to email? |
|
| Back to top |
|
gerasimos_h
Site Admin
Joined: 09 Aug 2007
Posts: 1757
Location: Greece
|
| Posted: Wed Jul 14, 2010 7:05 am Post subject: |
|
|
It supposed to automatically whitelist IPs the second time, after a greylist period of 5 minutes.
Either increase the greylisting period above 5 minutes, or if you know and trust a host, add it to your local whitelist for not greylisting them.
gerasimos_h
_________________
Superb! Mini Server Project Manager
http://sms.it-ccs.com |
|
| Back to top |
|
keopp
Senior Member
Joined: 08 Nov 2008
Posts: 166
Location: Romania
|
| Posted: Wed Jul 14, 2010 1:00 pm Post subject: |
|
|
Hi guys,
I'am using sqlgrey for 4 years now, and it did it's job very good. I had to act like gherasimos said for whitelisting several domains but they are less than 10 and never a "solid" one like yahoo, gmail, hotmail, etc.
I suggest you check if it's not a yahoo delivery issue.
It is also recomennded, form time to time (cronjob eventually) to update the whitelists(see about update_sqlgrey_config script in the end of the quote). I give you below a quote from the HOWTO file included in the package:
| Quote: |
##################
## Whitelisting ##
##################
Some MTAs don't play well with greylisting (often because they don't
respect the RFCs). To work around this problem (that your users won't
fail to report to you when it will happen):
- don't disable sqlgrey logs (by default it will log what you need).
- ask your user for the e-mail of the person that unsuccesfully tried
to send mail to her/him and when the unsuccessfull attempt occured.
- in the meantime, if the transmission failure occured recently (less than
max_connect_age in sqlgrey.conf, by default 24 hours) advise your user to
contact the sender and politely ask her to re-send the message, there are
good chances that the second attempt will get through (SQLgrey will probably
find a match: the first attempt).
- grep your mail logs for the address, you'll find a line like this
<timestamp> <system> sqlgrey: grey: new: <id>(www.xxx.yyy.zzz): <sender_address> -> <your_user>
by default, one day later you'll find this line:
<timestamp> <system> sqlgrey: spam: <id>: <sender_address> -> <your_user> at <timestamp>
What matters to you is the IP address (or the class C network) and
the domain name it is associated with. If Postfix could find a reliable
domain name (the reverse lookup must itself point to the IP address),
you'll find it in one of the lines in your log before the first
sqlgrey log line.
If you can get a reliable domain name, put it in
/etc/sqlgrey/clients_fqdn_whitelist.local
do *not* touch the /etc/sqlgrey/clients_fqdn_whitelist file as it will
be overwritten by a future sqlgrey installation or update_sqlgrey_config
The top of /etc/sqlgrey/clients_fqdn_whitelist explains the expected
formats.
You don't need to restart sqlgrey as it monitors the ".local" files
and reload them as soon as they change or when they are created for
the first time.
If you can't get a reliable domain name, just put the IP address in
the /etc/sqlgrey/clients_ip_whitelist.local file. If you need to,
you can add a whole class C network by putting a line with only the
three first bytes of the IP addresses.
IPv6 addresses are also supported in this file.
As it's quite important I repeat: only look for the installed
clients_*_whitelist files for reference and put your own entries
in the corresponding *.local files.
You are advised to subscribe to the sqlgrey-users mailing-list
(see http://lists.sourceforge.net/lists/listinfo/sqlgrey-users)
and submit the IP addresses and domain names you have to add to
your .local files to make your users happy and the reason why
you did so (see comments on why the existing systems are added).
As of 1.4.3, SQLgrey's whitelists can be updated from a central
repository with the update_sqlgrey_config script.
update_sqlgrey_config outputs modified entries on STDOUT.
Running it from cron once a day (updates are scarcely needed and
the average interval between updates is roughly one month) is a
great way to be warned of new whitelist entries or old entries
being cleaned up.
|
cheers to all SMS fan's |
|
| Back to top |
|
baboo
Senior Member
Joined: 04 Sep 2007
Posts: 676
|
| Posted: Wed Jul 14, 2010 6:06 pm Post subject: |
|
|
| keopp: thanks for the info! |
|
| Back to top |
|
|
