On Fri, Feb 18, 2005 at 03:46:25PM +0000, Paul Howarth wrote:
Alexander Volovics wrote:
Ah, there were spammers on @home which resulted in whole sale black listing. Now that does happen. Also a lot of email admins will block dynamic IP address ranges. If you happen to be trying to run an email server from a dynamic IP address (even if your assigned address has not changed in years) a large part of the Internet will not accept SMTP connections from you. In that case you just need to route your email through your ISPs SMTP servers. Not much else you can do about that.
The problem is I *am* routing my email through my ISPs SMTP server!
No, you're not. At least you're sending mail to this mailing list directly from your own machine (cm10703-a.maast1.lb.home.nl [84.30.68.3]) to Red Hat's MX hosts, not via any smarthost:
Received: from cm10703-a.maast1.lb.home.nl (cm10703-a.maast1.lb.home.nl [84.30.68.3]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id j1IFgvvu021330 for <fedora-list@xxxxxxxxxx>; Fri, 18 Feb 2005 10:42:57 -0500 Received: by af.ever.maas (Postfix, from userid 500) id C7446140FEB; Fri, 18 Feb 2005 16:46:37 +0100 (CET)
Yes, I am! This is probably due to my postfix main.cf setup which contains
the line: "smtp_helo_name = cm10703-a.maast1.lb.home.nl"
I did this to keep all traces of my home network out of the headers. Maybe I should rethink this.
The top Received: line above shows mx1.redhat.com receiving a connection from 84.30.68.3; is that your IP or your ISP's smarthost's IP? My money's on the former.
Paul.