EXIM - fallback to smarthost

[Ed Wilts]

On Fri, Oct 07, 2005 at 09:24:18AM +0100, Gary Stainburn wrote:
> Hi Ed

Howdy!

> On Thursday 06 October 2005 6:05 pm, Ed Wilts wrote:
> > On Thu, Oct 06, 2005 at 04:44:30PM +0100, Gary Stainburn wrote:
> > > I don't have a smarthost set and SMTP delivery is set direct as I
> > > prefer this for both performance and logging reasons.
> >
> > You may prefer it but the target doesn't.  That's why your email is
> > being blocked.
> >
> > > However, I have just chaanged ISPs and for some reason my IP
> > > address range is on an RBL.
> >
> > "For some reason"?  Give us your IP address and we'll tell you why.
> > There's a good chance that you're in a dynamic IP address range and
> > that will be blocked by a LOT of hosts.
> 
> I have a leased line connection with a fixed IP subnet of 
> 80.193.83.129/25 (I think the netmask is right)

I did a spam lookup at dnsstuff.com and one hit came back at
http://moensted.dk/spam/no-more-funn/?addr=80.193.83.129

There is a "delist" button there.  His comment is "based on reverse dns
samples 1030744800 (Sat Aug 31 00:00:00 2002)".  It looks like the block
you're in used to be dynamic but you've since bought the static block.

Another hit came at http://dnsbl.rangers.eu.org/.  There's an FAQ there
on how to get delisted.

> This should not have been included on a dial-up RBL.

The main problem with RBLs is that they don't solve the real problem.
One of the assumptions is that dynamic IP addresses are spammers and
that's not always true.  Spam should be determined by content, not by
source address.

> > Personally, I gave up and send all email through my ISP.
> 
> The problem with this is performance.  Even the techie at my ISP 
> admitted that this would seriously slow down email, 

Then your ISP has slow email.  It should not be a serious slowdown -
it's adding one hop through their mail server(s) and your email has to go
through their network anyway.  You may be forced to switch ISPs if you
can't straighten out the RBL issues (which admittedly are broken mail
servers on the receiving end - they're rejecting non-spam as spam and
that's more of their problem than your problem).

-- 
Ed Wilts, RHCE
Mounds View, MN, USA
mailto:ewilts at ewilts.org
Member #1, Red Hat Community Ambassador Program