[EMAIL PROTECTED] writes:
By the time the packet hits badmail from you've already done a lot of work
to just reject the connection.
Filter it as soon as possible. BEFORE it get to you SMTP port so you
don't have to spawn an ident child, then a qmail-smtpd then reject the
packet. I'm
True. The spam may just que on a server somewhere for a few days then
die.
But you still need to process the mail up to a point to the badmailfrom
check and deny the mail.
Personal preference I would guess.
Paul Farber
Farber Technology
[EMAIL PROTECTED]
Ph 570-628-5303
Fax 570-628-5545
On
I would not think so. Filtering is based on a simple premise... don not
accept packets from a specific IP address or range of IP's. If you don't
know what IP 's to filter, then you must find a way to get that
information. Try netstat -n or grep your mail logs for the IP's in
question
On Sun, 26 Sep 1999 [EMAIL PROTECTED] wrote:
I would not think so. Filtering is based on a simple premise... don not
accept packets from a specific IP address or range of IP's. If you don't
know what IP 's to filter, then you must find a way to get that
information. Try netstat -n or grep
On Mon, 27 Sep 1999, Abel Lucano wrote:
Under qmail, i was able (until yesterday) to filter undesirable spam
mostly with /var/qmail/control/badmailfrom
The question here arises in one spammer (206.221.224.187)
who's spamming aol.com from one ppp session with a bogus domain "ba.net"
that
By the time the packet hits badmail from you've already done a lot of work
to just reject the connection.
Filter it as soon as possible. BEFORE it get to you SMTP port so you
don't have to spawn an ident child, then a qmail-smtpd then reject the
packet. I'm not sure of exactly how far up
On Sat, 25 Sep 1999 [EMAIL PROTECTED] wrote:
find out that ip address aol is using and
ipfwadm -I -a deny -S AOL.IP.ADDRESS.HERE -D YOUR.MAIL.SERVER.IP
or use tcpserver.
i believe that i'm doing so, but aol relays rotates and i'm receiving
bounces from differents ip's (lot of aol's
