Site Registration Email Treated as Spam 1

[audiopro]

Emails containing links in the form

name@domain.domain.ext

are being blocked by my ISP's spam filter.
Is there any way round this problem apart from moving ISP?



Keith

http://www.studiosoft.co.uk

 

[smah]

[ignore]user@host.domain.tld[/ignore] is common and legitimately correct. Your ISP is probably flagging it as spam for other reasons. There are many possible reasons that messages can be flagged as spam, and including a valid host name is not likely to be one of them.

(Does it come from a static or dynamic IP address? Is the ip address it's coming from listed on any RBL's? Is the sending host's MX records properly configured? SPF or Domain Keys?, etc....)

 

[audiopro]

The email came form a forum host as a result of signing up to a forum. It is the type that sends an activation code via email in order to activate an account. It isn't just a one off thing as an email is also sent when a thread is added to a flagged topic.
I failed to get emails from them on one of my regular email addresses so sent it to another where the spam filtering was a lot lower.

Once I got the email, to take the host out of the equation, I forwarded it to the email address which refused it in the first place and it faled to get through. I reduced the contents to one line which was simply a link in the form of

[URL unfurl="true"]http://www.forumaddress.[/URL][red]forumhost[/red].index.cgi?var1=12&var2=something&var3=somethingelse

This email was not delivered by my ISP.
I altered the address by removing the section in red above leaving

[URL unfurl="true"]http://www.forumaddress.index.cgi?var1=12&var2=something&var3=somethingelse[/URL]

and the email was delivered. The forum's own support forum contains a few other examples of complaints about non delivered emails so I wondered what could be wrong.

This is of interest as I have written scripts which send emails and wondered if there was something I could do to prevent this problem.

Keith

http://www.studiosoft.co.uk

 

[58sniper]

Let's assume an email is coming from the address of user@sub.domain.com

If the administrator for the RECEIVING server did his part, then an inbound email from user@sub.domain.com is going to get checked for a bunch of different things.
1. Is the IP address it's coming from dynamic or static?
2. Does the PTR record (reverse DNS) for that IP match sub.domain.com?
3. What's the MX record for sub.domain.com? Does it match what the PTR record says?
4. What's the SPF record say? Is the IP address that the email is coming from listed in the SPF record?
5. Are there any configured IP blocks for that IP address/range?
6. Is sub.domain.com blacklisted?
7. Are DomainKeys being used?

And on, and on.....

Without seeing the bounce message, or the SMTP log, it's impossible to know for sure why it's bouncing, but it's almost certainly one of these reasons.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[audiopro]

Thanks.
I don't think I have access to that information so I have asked my ISP to look into it.
I tried taking a letter out of the domain name and that was forwarded with no problem.
I am thinking that it is on the blacklisted list.

Keith

http://www.studiosoft.co.uk

 

[audiopro]

I have managed to register with the Forum provider's own support section using the email address which failed initially.
A thought occurred to me.
The original forum I joined has only been going for few weeks, is it possible that the DNS and PTR records (something I know nothing about) take some time to be registered so at the moment, they are being rejected until the records are set up?

Keith

http://www.studiosoft.co.uk

 

[58sniper]

No. PTR records are immediate, but may be cached for up to 24 hours.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[audiopro]

Darn, I thought I was on to something. Is there anything more I can do from a remote location to work out the problem?

Keith

http://www.studiosoft.co.uk

 

[cckens]

Seriously? Have your ISP whitelist the user@host.domain.tld. Single e-mail addresses on the whitelist bypass all filtering algorithms. If they can't or won't, then you're better off going with a provider who will. An ISP should NOT control your access list, and any that do are not worth the money to have. Get a free account if you have to...
My 2 cents...

cckens

"Not always my best shot, but I hit the target now and then"
-me

 

[58sniper]

Single e-mail addresses on the whitelist bypass all filtering algorithms.

No they don't. They only bypass SMTP address related filters.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/