" it�s like they deliberately added their block of clients to the blacklists to force people to use their own smtp server for outgoing."

 

Yes, they do deliberately block the IPs for residential users. In theory, their business accounts shouldn't be on the list. They want you to spend more money.

They say it is to stop virus spreading and it does.

 

Earthlink residential IP addresses are also on the lists, although I don't think Earthlink actually feeds their addresses to the RBL maintainers.

 

Those are the only two residential ISP's I have experience with. I just relay through their smtp server. There is a setting in Surgemail to do that.

 

 

 

---

Original message
From: "Jeff Sick" <sickjj@mail.buffalostate.edu>
To: surgemail-list@netwinsite.com;
Dated: 11/25/2013 9:18:07 AM
Subject: RE: RE: [SurgeMail List] RBL Issue

I was able to get a message from home on Roadrunner (I use Outlook as a client, not an issue with webmail) through Surgemail for the SMTP to a work account on google.

 

Here are the header lines that mention the originating home IP (when I opened it up at work using Outlook as a client, I added the XXX).

 

 

X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=76.180.xxx.xxx;

X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=0 Stars=0 Good=0 Friend=2 Surbl=0 Catch=0 r=0 ip=76.180.xxx.xxx

X-IP-stats: GreyPassed Incoming Last 0, First 23, in=44, out=0, spam=0 ip=76.180.xxx.xxx

 

 

I don�t know if Roadrunner is the only one that does this, it�s like they deliberately added their block of clients to the blacklists to force people to use their own smtp server for outgoing.

 

Thanks,

Jeff

 

 

 

From: surgemail-support [mailto:surgemail-support@netwinsite.com]
Sent: Sunday, November 17, 2013 3:06 PM
To: surgemail-list@netwinsite.com
Subject: re: RE: [SurgeMail List] RBL Issue

 

If that setting doesn't work, it means the problem is some other header or some header added by something else.   You need to examine the full headers of a message you send (making sure to send it in exactly the same way as when the problem occurs, but send to somewhere external you can get the headers (gmail) to see where it contains the problem ip address and then we can figure out what mail server is adding the problem entry. 

 

    ChrisP.

 

I�ll try this also, I get the exact same thing, also using roadrunner. The message almost seems to be a case of Roadrunner/Time Warner/Adelphia not wanting anyone to use any kind of SMTP other than their own.

 

Oops, nevermind, I checked and it�s already set to true, so that doesn�t take care of it.

 

I notice that it only blocks email to those you have never emailed before or aren�t in the process of replying.

 

Jeff

Buffalo State College

 

 

From: surgemail-support [mailto:surgemail-support@netwinsite.com]

Sent: Thursday, November 14, 2013 2:41 PM

To: surgemail-list@netwinsite.com

Subject: re: [SurgeMail List] RBL Issue

 

Try this it might help as it should then keep the users ip out of the message so then a rejection as you describe shouldn't be possible....

 

G_RECEIVED_SKIP "true"

 

ChrisP.

 

Hi,

 

I have one of our users who is unable to send an email to one of his clients. His messages get returned with this message:

 

Final-Recipient: rfc822;stevek@teraco.com <mailto:stevek@teraco.com>

Action: failed

Status: 5.0.0

Diagnostic-code smtp; Site teraco.com <http://teraco.com/> (12.12.240.139) said after data sent: 550 5.7.1 Please send this email to your IT personnel. 550-5.7.1 We are rejecting your email, because you were found on zen.spamhaus.org <http://zen.spamhaus.org/> spam black list.

 

His email takes the form of authorized_user@ehowe.com <mailto:authorized_user@ehowe.com>

I checked spamhaus.org and the IP address of ehowe.com is not being blacklisted. What is in their blacklist is his personal IP of the machine that he is sending the email from. It says 74.136.165.243 is listed in the PBL, in the following records:

 

PBL1548045 <http://www.spamhaus.org/pbl/query/PBL1548045>

 

This is why I can send an email to his client from an ehowe.com email address and he can't.

 

Shouldn't his client's mail server (teraco.com) be checking that the message it is receiving is from our email server given the address is @ehowe.com and then checking the IP for ehowe.com to make sure it's not blacklisted?

 

He tried to remove his IP address, which is assigned from his service provider, from the blacklist but spamhaus.org gave him this reply: Removal of IP addresses within this range from the PBL is not allowed by the netblock owner's policy.

 

Is there anything we can do here or is it all on his clients email server.

 

-- *Randy Zumwalde* . Tel: 513.651.1888 . Mobile/Direct 859.801.1419

The John K. Howe Company, Inc.

7188 Main Street | Cincinnati, OH 45244

 

Be sure to visit us online at http://www.ehowe.com

Like us on Facebook at _https://www.facebook.com/howemarketing_

Looking for product ideas? visit _http://ehowe.mypromohq.com_

 

 

 

---

This email is free from viruses and malware because avast! Antivirus protection is active.