I don't know if I can bring myself to do that, occasionally
we have problems with false positives, so silently dropping
mail would seriously aggravate the issue. People around
here depend on the bounce messages.
I'm sure we have false-positives, and misaddresses email,
etc. But, the number
On Wednesday 16 March 2005 04:10 pm, Chris Myers wrote:
Well, after nearly 6 years and lots of hand wringing, we finally were
awarded US patent 6,868,498 for our user-level blacklisting as long-ago
disclosed to the ASRG in
http://www.shaftek.org/publications/asrg-ipr.html#4.2 .
USPTO link:
On Monday 20 December 2004 01:07 pm, Matthew Hall wrote:
OK, so access will reject all networks, BUT, because we enable
delay_checks, that gets delayed long enough to hit the
spam:@ourdomain FRIEND
and be accepted for relay to our smart host? That spam rule
looks for To:@ourdomain, not
On Wednesday 22 December 2004 01:46 pm, John wrote:
Incorrect.
The older versions of sendmail are that way. I think they changed that in
the 8.11.x or 8.12.x
The correct syntax for a domain is:
Spam:domainname.com FRIEND
FEATURE(`delay_checks',`friend') must be in your sendmail.mc
On Friday 17 December 2004 04:09 pm, Matthew Hall wrote:
I want to effectively whitelist our domain and a few others
for delivery, while dropping all others. I attempted to use
FEATURE(`delay_checks') but was unable to find an appropriate
set of rules to use in access.db to do what I'm
On Tuesday 16 March 2004 10:43, Charles Mount wrote:
Thanks everyone. As a follow-up, with add_recipient or resend_message, is
the new recipient obvious to the other recipients, or is it like a bcc?
As background on the legal issues; it is clear that legally the company not
the employee is
On Friday 13 February 2004 04:44, Andrzej Marecki wrote:
I'm using MD+SA+Sophie+Sophos (SAVI libs + .ide).
Do you think that what has been written in:
http://www.securitynewsportal.com/cgi-bin/securitynews.cgi?database=JanDDi
d=74
...means my system is vulnerable to attacks via that hole?
7 matches
Mail list logo
