Re[2]: [vps-mail] Dramatic increase of SPAM during last days

[Abigail Marshall <abigail@xxxxxxxxxxxx>]

GS> On Tue, 24 Aug 2004 10:12:14 -0400, "Brian Haines"
GS> <providertalk@xxxxxxxxxxxxxxxx> wrote:

>> I meant dul.dnsbl.sorbs.net. Would that now allow me to send mail from my
>> Comcast ISP?

GS> I'm assuming you're using SMTP AUTH. Once you've authenticated yourself,
GS> this overrides any DNSBL used by sendmail.

Not true - if your DSL is on the blocklist, and you try to
send mail via your VPS, it will be blocked by sendmail.
However, there is an easy fix -- which is to simply enter
your own assigned IP into the access file:

So if you have a static IP, (example 123.45.67.89) - you
would enter:

123.45.67.89 OK

then:
VPS1:  % vnewaccess
VPS2:  % make

If you have a dynamic IP, it is more difficult - I'd suggest
adding the full range:

123.45.67 OK

Over time, with a dynamic IP I have had to add more IPs -
what happens is I will from time to time find my email
blocked - then I simply edit the access file as needed, and
resend the email & I am fine. But the entries in my access
file now look something like this:

# My ISP
123.45.67 OK
123.45.68 OK
123.45.69 OK

This will be a problem if customers/clients are allowed to
SMTP via the VPS as opposed to their own ISP - you would
spend all the time editing the access file - in that case,
it simply is better not to use the blocklists.

-Abigail

======================================================================
This is <vps-mail@xxxxxxxxxxxx>       <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).