Extra "dot" being injected in embedded href's
Status: Beta
Brought to you by:
mikelbridge
Menu
▾
▴
I have a strange issue that I'm hoping I can adequately explain here. I don't think it is an issue with DotNetOpenMail but am posting it here with the hope that if it's not then maybe someone monitoring this discussion may have a hunch as to what it might be.
Some of our system emails that go out include a link to an application with some query strings in the link. Most of the links that go out are fine but some of them are ending up on the client with an extra dot in the page name. For instance, if the link should be http://www.mydomain.com/myapp/mypage.aspx?id=1 the link is rendering in the client's email as http://www.mydomain.com/myapp/mypage..aspx?id=1
Notice the extra dot between mypage and aspx in the link above. Our end users are internet users rather than corporate users so their email client can be anything so that part if fairly random and I haven't been able to see a pattern based on the email client. I log all of the correspondence that goes out and can confirm that the email that is sent does not include the extra dot so it is being injected somewhere on the wire (after it leaves my code).
As I said, very strange and I doubt it is an issue with DotNetOpenMail but if you have any suggestions please let me know as I'm at my wit's end right now.
Thanks.
Hi-
That's a pretty strange one. Is it possible that your outgoing firewall is doing some spam checking? It's possible (though unlikely) that a wayward firewall rule is doing some weird rewriting.
Do you have the "raw" email that someone tried to click on? Is it consistently the same links?
-Mike
I just had another "extra dot" situation. In this case the extra dot was placed inside of an email address rather than the situation described above where it is being placed in a hyperlink. It's wierd how it is totally random. I still doubt that it is DotNetOpenMail but figured I'd follow up here anyways. I'll post a thread on the SmarterMail board too as that's my outgoing mail server.
Normally a dot is doubled when it occurs at the beginning of a line---see RFC 821 section 4.5.2. I'm pretty sure this is correct in DotNetOpenMail, but I haven't tested SmarterMail to know if there's aa strange interaction with it or not.
You might try taking a raw sent message and resend it using SmtpDebug (from the same sourceforge page). If you can find the place where this happens or reproduce it.
Cheers,
-mike