/dev/rob0
2005-06-26 13:01:12 UTC
I've got it going now, was rather easy. I started in test mode, with
"warn_if_reject check_policy_service inet:127.0.0.1:2501" in main.cf.
Will this really populate my database? Since nothing is being rejected,
it looks like non-returning triplets. Nothing is autowhitelisted until
the first appearance after the greylist period, correct?
Other things I'm wondering, and please forgive me if they're in the
archives[1]:
1. localhost:2501 vs. Unix socket
Wouldn't a socket be slightly faster than TCP?
2. Running under control of master(8)
That would be convenient, start and stop with Postfix; are there other
benefits? Why the standalone choice?
3. Database population commands
I'm totally lost with SQL (hence the poor choice of mysql), can someone
help with the manual commands I'd use to add to the database?
4. Database population scripts
Is there something I could run against user's maildirs which would add
entries to the AWL? If not should I commission such a project from my
private farm of Perl coders[2]; I mean, would there be interest?
5. External files vs. database tables
$conf_dir/clients_*_whitelist* - why flat files vs. having additional
database tables?
6. dyn_fqdn.regexp
That's quite an expression. I didn't figure the whole thing out, but I
did look for a string "\.res\." which is commonly used for dynamic
space, e.g., *.res.rr.com. (residential customers.) Perhaps the second
dot should be any non-alpha character (-, _, ., digit), and to be safe
there should be at least 2 domain segments following and at least one
segment preceding (implied by the leading dot.)
7. Coordination with infidels
Greylisters, regardless of their MTA and choice of implementation, are
all in this together. We're all going to run into the same issues with
stupid and/or big providers which have problems getting real mail
through greylisting. I didn't see a list or forum at greylisting.org.
What is being done to coordinate with outsiders? I personally have
subscribed to the postgrey list, where just this morning a thread of
general grey interest was started (well, just one post so far.)
8. Beyond grey
This is a biggie which probably warrants its own thread. This is all
about spam abatement. What about integrating other antispam strategies
under the roof of the same policy service? Yes, this belongs in its own
thread. I'll write more of my thoughts about that later.
Thanks, Lionel, this looks good so far. I went live with a small but
heavily-spammed domain yesterday evening, and no spam has been seen
there since. (The sqlgrey is last in a long list of restrictions with
numerous RBL checks.)
[1] Is it just me, or are Sourceforge list archives atrocious?
[2] a/k/a /dev/wife. I might need some help with #3 above to get her
started, but OTOH she has some PostgreSQL knowledge.
"warn_if_reject check_policy_service inet:127.0.0.1:2501" in main.cf.
Will this really populate my database? Since nothing is being rejected,
it looks like non-returning triplets. Nothing is autowhitelisted until
the first appearance after the greylist period, correct?
Other things I'm wondering, and please forgive me if they're in the
archives[1]:
1. localhost:2501 vs. Unix socket
Wouldn't a socket be slightly faster than TCP?
2. Running under control of master(8)
That would be convenient, start and stop with Postfix; are there other
benefits? Why the standalone choice?
3. Database population commands
I'm totally lost with SQL (hence the poor choice of mysql), can someone
help with the manual commands I'd use to add to the database?
4. Database population scripts
Is there something I could run against user's maildirs which would add
entries to the AWL? If not should I commission such a project from my
private farm of Perl coders[2]; I mean, would there be interest?
5. External files vs. database tables
$conf_dir/clients_*_whitelist* - why flat files vs. having additional
database tables?
6. dyn_fqdn.regexp
That's quite an expression. I didn't figure the whole thing out, but I
did look for a string "\.res\." which is commonly used for dynamic
space, e.g., *.res.rr.com. (residential customers.) Perhaps the second
dot should be any non-alpha character (-, _, ., digit), and to be safe
there should be at least 2 domain segments following and at least one
segment preceding (implied by the leading dot.)
7. Coordination with infidels
Greylisters, regardless of their MTA and choice of implementation, are
all in this together. We're all going to run into the same issues with
stupid and/or big providers which have problems getting real mail
through greylisting. I didn't see a list or forum at greylisting.org.
What is being done to coordinate with outsiders? I personally have
subscribed to the postgrey list, where just this morning a thread of
general grey interest was started (well, just one post so far.)
8. Beyond grey
This is a biggie which probably warrants its own thread. This is all
about spam abatement. What about integrating other antispam strategies
under the roof of the same policy service? Yes, this belongs in its own
thread. I'll write more of my thoughts about that later.
Thanks, Lionel, this looks good so far. I went live with a small but
heavily-spammed domain yesterday evening, and no spam has been seen
there since. (The sqlgrey is last in a long list of restrictions with
numerous RBL checks.)
[1] Is it just me, or are Sourceforge list archives atrocious?
[2] a/k/a /dev/wife. I might need some help with #3 above to get her
started, but OTOH she has some PostgreSQL knowledge.
--
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header
mail to this address is discarded unless "/dev/rob0"
or "not-spam" is in Subject: header