Sorry for offtopic, but some might be affected by this.
Mate Wierdl wrote:
> 1) My server started to get a lot of spam from dialup sources (the
I'm using a dialup line. When I started encountering resistance to
sending of mail from my local sendmail, the easy solution was to use
my ISP's SMTP host as a sendmail smart host. It required a one-line
change to the .cf. It's also more efficient to use the smart host
because it's always up and responsive -- I didn't like dealing with
unresponsive receiving servers since I was using a dialup line.
You are doing what every dialup user is supposed to be doing. Indeed,
there is always a good percentage (~10) of the remote mail that will be
deferred because of connection problems on the receiving end. So
every dialup user should use their ISP's mail server as a relay so
that the mail can get queued there if needed and not on the local
box. Besides this being a sensible way of sending your mail, any
other way is *unauthorized* by your ISP.
The new kind of spammer directly connects to the (victim) server to
upload her deed.
So those people who directly try to connect to my server might have
problems---if they are using an IP number that was used to spam
before, and appear in the dul list. Most people do not have to worry
about this, but if your ISP is known to tolerate (dialup) spam, you
want to use your ISP's mailserver to send messages.
Again, if you think you have a problem posting to this list, please
complain to
[EMAIL PROTECTED]
(which is me on a different server).
Mate
