On Wed, 14 Dec 2005, Kenneth Porter wrote:
help a small company server. Perhaps a distributed greylist DB? Sort of like
a DNSBL but with white-listing. MD could store the successful entries in a
zone and we could publish our zones for others to use.
OK, how to keep the "Bad Guys" out?
You're
Any one has solution for this.
help me..
--- [EMAIL PROTECTED] wrote:
> bablu wrote:
> > I want to attach disclamer only to mails relayed
> by
> > smtp server. (i.e. mail sent by internal clients
> who
> > have account on smtp server)
> > Or is it possible to attach disclamer ba
Thank you all for your comments on greylisting. John Kirkland's work looks
like it will fit the bill nicely. I especially like the idea of using MySQL
for the database.
I think it might require a bit of prep work to make this a bit less
noticeable. The recommendation of building a whitelist a
David F. Skoll wrote:
It helps a lot, because you quickly build up a list of servers for
companies you correspond with often, and for large domains like
hotmail.com and aol.com.
Suppose you correspond with 10 people at CompanyA. Once *one* person
has passed the greylist test, all 10 of them can
--On Wednesday, December 14, 2005 10:50 PM -0500 "David F. Skoll"
<[EMAIL PROTECTED]> wrote:
Suppose you correspond with 10 people at CompanyA. Once *one* person
has passed the greylist test, all 10 of them can communicate with any
one of you without any greylisting delays.
True. But I was t
Kenneth Porter wrote:
>> Our (commercial) implementation of greylisting notes when a host
>> makes it past the greylist hurdle. Once that happens, we don't greylist
>> that host for 40 days.
> While I can see how that helps a large userbase, I don't see how it
> would help a small company server
--On Wednesday, December 14, 2005 9:37 PM -0500 "David F. Skoll"
<[EMAIL PROTECTED]> wrote:
Our (commercial) implementation of greylisting notes when a host
makes it past the greylist hurdle. Once that happens, we don't greylist
that host for 40 days. It's a simple trick that greatly reduces
Gary Funck wrote:
> something worth mentioning: greylisting is highly effective,
> but it takes some getting used to. Like when you go to a
> web site and register a new account, and wait, wait, wait for
> the reply to come in with your account confirmation e-mail.
Yup.
Our (commercial) impleme
something worth mentioning: greylisting is highly effective,
but it takes some getting used to. Like when you go to a
web site and register a new account, and wait, wait, wait for
the reply to come in with your account confirmation e-mail.
Or when you forget your password and wait for the mail to
I used John Kirkland's implementation, using MYSQL,
with great success (on an FC3 system):
http://www.bl.org/~jpk/md-greylist/
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
I am relatively new to MIMEDefang, and I'm very happy with what I've been
able to do so far. I'd like to take things to a higher level though, and
one of the areas I'd like to work on is greylisting. I've seen a couple of
emails in the archives, and I've tried using Jonas Eckerman's filter on my
bablu wrote:
> I want to attach disclamer only to mails relayed by
> smtp server. (i.e. mail sent by internal clients who
> have account on smtp server)
> Or is it possible to attach disclamer based on domain
> name.
>
> which solution is effective..
I think, perhaps, the solution is to imagi
Hi,
I get tons of the following errors in the mail.log after I start
mimedefang-2.54
Dec 14 12:27:09 sbox dns: select failed: Bad file number at
/usr/local/lib/perl5/site_perl/5.8.5/Mail/SpamAssassin/DnsResolver.pm line
347.
Dec 14 12:27:09 sbox mimedefang-multiplexor[10855]: [ID 980602 mail
13 matches
Mail list logo
