[Exim] Re: Mail relay problems

Page principale
Supprimer ce message
Répondre à ce message
Auteur: Suresh Ramasubramanian
Date:  
À: exim
Sujet: [Exim] Re: Mail relay problems
+++ Derrick 'dman' Hudson [09/06/02 13:58 -0500]:
> Actually, the bigger the ISP the more worried you need to be. When an
> ISP is large enough, it will have lots of IP addresses and customers
> who could be spammers. In addition, their abuse desk (if they have


There are several ISPs who - even with their size, are proactive about spam.

> one) will be overloaded and in the end they probably won't do much to
> help the problem. As for reputation ... has anyone heard of AOL,
> Yahoo, Hotmail, MSN, or Earthlink? Lots of spam comes through there.


Freemail services and spam - yes, spam comes through them, but the majority
of spam with a freemail (hotmail, email.com, yahoo, whatever) address in the
from or headers is either totally forged headers, or did not originate from
or pass through the freemail service's network at all.

Earthlink in fact has a pretty good abuse desk. Oh, and they use Exim.

> apart from people who will stop accepting all mail from your server
> (and your valid customers). In fact, people who use sa-exim won't


Spamassasin being the thingy that recently blocked the CAUCE newsletter as
spam because it contains the word spam, has the words "opt out" in it, etc
etc? Heh. Content based filtering, no matter how efficient and how well
setup, is a can of worms. If you use spamassasin, or other content filtering
system, the way to go would be to tag a header onto those things and/or file
them to a separate folder, not bounce / bitbucket all mail that spamassasin
thinks is spam.

    -srs


--
Suresh Ramasubramanian  <---->  mallet <at> efn dot org
EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
[Linux One Stanza Tip]    From : <bish@???>
LOST #119     -**< Sub : How to make a Loadlin bootdisk >**-
This is the simplest way making your own boot disk.  Totally a
DOS prompt job. In DOS [1] "format a: /s/v" [2] Copy two files
your kernel (usually vmlinuz) and "loadlin.exe" to it, [3] and
make a one-line config.sys to point to your / device and boot:
e.g. "shell=a:\loadlin.exe a:\vmlinuz root=/dev/hda2 ro"