The error is typically seen when your server has the sender blacklisted. Mail is now coming from a different source (I suspect) and that source is on a list used by whichever servers are not accepting the messages. Best solution is to contact your email provider and ask them about it, see if they can modify their lists.

Both sides need to check things... Titus needs to make sure the if mail is being sent from the web server local smtp, that the IP is not blacklisted... If sent from an actual mail server (different box) again, check the IP.

The same goes with the recipient, however that is most likely going to be worse than pulling teeth if you have to deal with a major ISP like Telus or Shaw.

I personally would recommend Canreef to check the IP's they are using, and if by chance they are being blacklisted, then you need to fix.

If Canreef email is being sent via a major ISP, then don't do it this way, as most major ISP's email servers are blacklisted at times.

Also if Canreef is hosting its own email/web services on a major ISP line, be careful, as the sending email port (SMTP) 25 is blocked by all major ISP's of the world now. What this means that even if you have your own mail server, IP, connection, but is provided by one of these such ISP's, most likely they are taking the email on port 25 and re-routing through their mail servers. And as stated above they have many servers, with some at times blacklisted, causing things like sparatic loss of email. You usually have to pay more to have an un-altered, un-filtered line with an open port 25. With some ISP's, they just won't offer an open port 25.

I just sold my hosting company, and I can testify, the one big issue I had was with the ISP's and how people had their systems, email, software, etc. setup... As this issue is known, but only if you know what to search for.

Hope this helps.

I would have to think that it's on CanReef side because I was getting notification up until the recent shut down. None of this IP stuff make sence to me as I am not a computer guru at all.

so I am to call my provider and tell them what......." Hey you know CanReef right? I am not getting any e-mail notifications from them any more, fix it "

Sounds like I need so real info like the IP address that the notifications are coming from or the server or what ever & the only one that know this is Titus but he has not provided any info for me to get this fixed so I can pass it along.

:frusty:

I haven't really been following this but could you deactivate your account then re instate it? Not sure if this is an option on here but it worked with facebook when it went all screwy on me :biggrin:

I'll try and get you the info. Essentially, Canreef is hosted on a server along with potentially many other sites. They can all use a single IP or range of IPs. If one of the sites has done something to get added to a spam filter, it would affect all the sites hosted on that server (or farm(collection of servers)). I'm not sure that it can even get adjusted manually if requested, even if the provider was so inclined.
But, we can get you the info and you can forward it (probably support@yourservername.com) and ask what you can do about it.

No, that won't help. It's actually an issue generated on the receiving side. Canreef is sending it just fine.

Hello,

Folks sorry for the delay. All the Canreef servers (public accessible or not) are on private servers that does nothing but Canreef related stuff. We own the 96.31.76.194/27 subnet on the Internet and both the www and mail servers are sitting on the same box with the IP 96.31.76.198.

Prior to the recent site maintenance we were on 96.31.86.198 so we did change IPs. A check with Cisco SenderBase shows that this IP is in good order (unlike our fiasco with Shaw last time).
http://www.senderbase.org/senderbase...g=96.31.76.198

The Grizz, please contact your ISP and give them the following. This is evident whatever it is, is occuring on your ISP end.
What I can tell based on checking last time and just now again is we do connect to your ISP just fine. The following response from your ISP occurs only after we have connected successfully to them. It's actually a failed transaction response to us when we specify your e-mail address as the recipient.
<grizzwelding@platinum.ca>: host inbound.platinum.ca[69.31.192.26] said: 554
Transaction failed (in reply to RCPT TO command)

Titus

Thanks Titus, one question I have is all the notifications coming from support@canreef.com? I had them add it to my white list so hopefully that worked.

I suspect the problem runs deeper.

The IP 96.31.76.198 is listed on three blacklists:

all.spamrats.com
noptr.spamrats.com
b.barracudacentral.org

I'm most familiar with barracuda. Many companies use Barracuda spam appliances to front end their mail servers. Our hosting provider for Conceptaquatics.ca seems to use spamrats.com - My guess is that it's part of a group of RBLs rather than programatically configured, but the end result is the same. We are not getting email notifications.

You can run a quick check here: http://www.barracudacentral.org/lookups/ip-reputation

I checked some of the other address in the 96.31.76.194/27 address space and many of them are listed on various RBLs. Some of them are listed on many. Fortunately, not all of them are listed.

96.31.76.221 seems to be clean. I stopped checking once I found one that was not listed. A quick fix would be to change the IP for outgoing mail to .221

- Brad