History of GreyListing

Difference (from prior major revision) (no other diffs)

Changed: 1c1

We use http://policyd.sourceforge.net/ to do [greylisting].

We use [postgrey] to do [greylisting] as a spam fighting measure. It's a perl script that I'm not thrilled about but it seems to be much more solid than our old solution which was ... flaky. Old whitelists and user opt-outs should be preserved, but if something's not working, squawk.

Changed: 5c5

This does mean that your e-mail may be delayed. This should only happen on the first time someone e-mails you, though, and will never happen from places like Caltech, and ofb.

This does mean that your e-mail may be delayed. This should only happen on the first time someone e-mails you, though, and will never happen from places like Caltech or ofb.

Changed: 7c7

If you want to "opt-out", and not have this happen for e-mails delivered to you, we can accommodate that fairly easily. E-mail wnoise, and I'll do so. I can also add other places to the white list.

If you want to "opt-out", and not have this happen for e-mails delivered to you, we can accommodate that fairly easily. If you don't want to futz with the configuration yourself, e-mail wnoise, and I'll do so. I can also add other places to the white list.

Changed: 11,32c11

Its config file is /etc/postfix-policyd.conf, which also contains the mysql password for the database. It's fairly, but not completely transparent. The data is stored in mysql, the database, user, and password are in the conf file, should you want to add whitelists, or opt-outs, or whatever.

mysql -u <user> -D <database> -p

Depending on exactly how one wants to whitelist, one of the following should be used:
INSERT INTO whitelist (_whitelist, _description) VALUES ('ip.add.ress', 'description');
INSERT INTO whitelist_dnsname (_whitelist, _description) VALUES ('%host.pat.tern', 'description');
INSERT INTO whitelist_sender (_whitelist, _description) VALUES ('e-mail@add.ress', 'description');

These all have some downside. IP addresses change, the dns whitelisting only works if forward and reverse match, and the sender is "spoofable" by spammers.

Opt-in/out are controlled by the "policy" table.

INSERT INTO policy (_rcpt, _optin, _priority) VALUES ("<username@our.dom.ain>", 0, 50);

or a whole virtual domain:

INSERT INTO policy (_rcpt, _optin, _priority) VALUES ("@virtual.domain", 0, 50);

This is controlled by address, not UID. If you have multiple addresses that you want exempt, you need to add them all. Yes, wildcards would be nice. We don't have them.

Read the docs for more details.

The main configuration files are stored in /etc/postgrey/ and should be self-explanatory. There's also /etc/defaults/postgrey that is used by the init.d controlling script to set some defaults.

	Revision 11 . . November 18, 2010 00:45 by Aaron
	Revision 10 . . May 9, 2007 20:21 by c-24-7-18-198.hsd1.ca.comcast.net