-
A combination of my prior patch IDs(#1914929,#1910018) to this project. I got quite bored of maintaining two separate ones.
This patch takes a base 1.0.5 version, and:
- Adds the 'missing error callback' stuff I did to stop noisy milter errors.
- Adds the 'PassAfterMailerTable' for recipients.
- Adds a 'PassAfterVirtuserTable' for senders (don't try to verify locally known-good...
2008-03-21 19:31:20 UTC by kyrian
-
Makes no sense for this to be done on sender verify, as senders won't be in your mailertable, whereas known private-forward recipients will be, hence I've rewritten it again to use separate callbacks for the rcpt and mail from, which just flag PAMT differently.
File Added: bm-milter-1.0.5-passafter.patch.
2008-03-19 13:39:12 UTC by kyrian
-
File Added: bm-milter-1.0.5-missingcb.patch.
2008-03-15 21:11:13 UTC by kyrian
-
Replaced the patch version with an improved one that has a toggle switch for the error callbacks to be verbose.
2008-03-15 21:03:07 UTC by kyrian
-
File Added: bm-milter-1.0.5-missingcb.patch.
2008-03-15 21:01:24 UTC by kyrian
-
Although it's not fatal, I got annoyed by the messages of this type:
... sendmail[]: m2FJiKv7007674: Milter (bm-milter): write(D) returned -1, expected 97: Broken pipe
... sendmail[]: m2FJiKv7007674: Milter (bm-milter): to error state
There's a missing abort callback, and probably others, which means that Sendmail/Milter falls back to default error states, which is what that message is...
2008-03-15 19:54:13 UTC by kyrian
-
Also, might be good to use IO::Socket->connected() tests in check_email_address_on_server() to make sure the remote server has not 'gone away', as I seem to be getting quite a lot of milter internal errors from that scenario.
2008-03-08 11:16:54 UTC by kyrian
-
Kind of related to bug 1909224.
I've read through the source of this milter at some length and created a patch that adds a new directive "PassAfterMailerTable" to the configuration file which causes a SMFIS_CONTINUE (carry on processing as normal) if the domain is not found in mailertable after a virtusertable lookup, thereby avoiding the slow MX and try-all-MX problems, but also avoiding it...
2008-03-08 10:53:15 UTC by kyrian
-
As best I can tell there is no checking in the system for alternative mailhosts that are lower priority MX records, and subsequently they are not excluded, therefore upon not finding matches in virtusertable, or mailertable, this milter will try lower priority MX records for the domain, as well as localhost on a round-robin basis (depends on your DNS I guess), thereby intermittently causing...
2008-03-07 01:32:23 UTC by kyrian
-
We want to try this milter before we put it into production. Is it possible to have a debug mode where the milter only report what it will do, and not actually deny any incomming mail?
What is the status on this milter? Is it production ready?
Rune Hamnvik.
2006-11-29 06:51:07 UTC by runeh
