Stop our emails ending up in spam...
Discussion
andy-xr said:
It looks like some of the main Gotchas are sorted now
http://www.dnsinspect.com/canvashut.com/1436453303
Are you still having problems getting emails delivered? Is the mail server a shared hosted one at your domain registrars or somewhere else? You're with Heart Internet from the looks of it. Their support is very very good, ask them if they can help make email more deliverable for you
Won't know if we're still having problems until we hear from customers saying they haven't had emails through or we don't receive replies. Will have to give it a few days really.http://www.dnsinspect.com/canvashut.com/1436453303
Are you still having problems getting emails delivered? Is the mail server a shared hosted one at your domain registrars or somewhere else? You're with Heart Internet from the looks of it. Their support is very very good, ask them if they can help make email more deliverable for you
All I know is that the website was created by a company called netbiz who manage all the hosting for use. We have no control over that. As we do is manage the content ourselves.
Looks like they may have acted on what we asked them to sort from that link. Thanks again for the help. I will report back soon.
I've never had any problem receiving emails from work emails, but I imagine it's because I quite often send emails backwards and forwards from them.
Seems to be random anyway. Some customers will have no issue, others will never see the emails, regardless which provider they are from. Who gets them and who doesn't has never been consistant.
We will just have to see how it goes really
Seems to be random anyway. Some customers will have no issue, others will never see the emails, regardless which provider they are from. Who gets them and who doesn't has never been consistant.
We will just have to see how it goes really
Sounds like I'm the only person that runs a mail server that finds SPF more of a nuisance than a help.
If you know a friendly person running spamassassin as their filter, ask them to send you back your message including headers after it has been through the filter. It helpfully lists the reasons why it thinks a message is spam in those headers (well, if the mail admin hasn't configured it not to) and a lot of them are human readable, e.g.
Most of these make some kind of sense, although I'd need to look up a couple if we were sending out emails that were triggering filters with them.
Note that I give zero weight to SORBS.
If you know a friendly person running spamassassin as their filter, ask them to send you back your message including headers after it has been through the filter. It helpfully lists the reasons why it thinks a message is spam in those headers (well, if the mail admin hasn't configured it not to) and a lot of them are human readable, e.g.
Content analysis details: (24.8 points, 4.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
2.5 URIBL_DBL_SPAM Contains a spam URL listed in the DBL blocklist
[URIs: besthealingelement.ru]
1.7 URIBL_WS_SURBL Contains an URL listed in the WS SURBL blocklist
[URIs: besthealingelement.ru]
1.9 URIBL_JP_SURBL Contains an URL listed in the JP SURBL blocklist
[URIs: besthealingelement.ru]
0.0 URIBL_SC_SURBL Contains an URL listed in the SC SURBL blocklist
[URIs: besthealingelement.ru]
0.9 RCVD_NUMERIC_HELO Received: contains an IP address used for HELO
0.0 RCVD_IN_SORBS_DUL RBL: SORBS: sent directly from dynamic IP address
[178.151.69.1 listed in dnsbl.sorbs.net]
3.6 RCVD_IN_SBL_CSS RBL: Received via a relay in Spamhaus SBL-CSS
[178.151.69.1 listed in zen.spamhaus.org]
3.6 RCVD_IN_PBL RBL: Received via a relay in Spamhaus PBL
0.7 RCVD_IN_XBL RBL: Received via a relay in Spamhaus XBL
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?178.151.69.1>]
1.3 RCVD_IN_RP_RNBL RBL: Relay in RNBL,
https://senderscore.org/blacklistlookup/
[178.151.69.1 listed in bl.score.senderscore.com]
2.7 RCVD_IN_PSBL RBL: Received via a relay in PSBL
[178.151.69.1 listed in psbl.surriel.com]
1.6 RCVD_IN_BRBL_LASTEXT RBL: RCVD_IN_BRBL_LASTEXT
[178.151.69.1 listed in bb.barracudacentral.org]
0.1 MISSING_MID Missing Message-Id: header
2.0 FSL_HELO_BARE_IP_2 FSL_HELO_BARE_IP_2
1.0 BODY_URI_ONLY Message body is only a URI in one line of text or for
an image
Most of these make some kind of sense, although I'd need to look up a couple if we were sending out emails that were triggering filters with them.
Note that I give zero weight to SORBS.
onomatopoeia said:
Sounds like I'm the only person that runs a mail server that finds SPF more of a nuisance than a help.
Why do you find them a nuisance ?They do make a huge difference, as does auto-generated emails through a 3rd party like mandrill or sendgrid as I have explained before.
cornet said:
Why do you find them a nuisance ?
I send an email from me@foo.com while in the office of foo.com to fred@bar.org. SPF checking on mx.bar.org looks at the server I sent through and sees it's one that's allowed, so accepts the mail and sends it on to fred's mailbox/maildir.fred, being a conscientious sort of chap, likes to keep up to date with his email at weekends, so has a forwarding rule that sends on any mail that comes to his work mailbox to fred@fredsisp.net so they come into his inbox at home, his employer not offering access to the local POP3/IMAP server from outside the company intranet. Fred's ISP checks the SPF record for foo.com and sees that mx.bar.org is not an allowed sender and bounces it back to me.
I get a bounce message from an address I wasn't trying to send to. This is fine, I can understand what is going on. Most people won't understand why their mail to fred@bar.org has been refused delivery to fred@fredsisp.net.
tl;dr SPF breaks simple forwarding where the sender is not rewritten.
onomatopoeia said:
....
fred, being a conscientious sort of chap, likes to keep up to date with his email at weekends, so has a forwarding rule that sends on any mail that comes to his work mailbox to fred@fredsisp.net so they come into his inbox at home, his employer not offering access to the local POP3/IMAP server from outside the company intranet.
Some firms would fire people for doing that.fred, being a conscientious sort of chap, likes to keep up to date with his email at weekends, so has a forwarding rule that sends on any mail that comes to his work mailbox to fred@fredsisp.net so they come into his inbox at home, his employer not offering access to the local POP3/IMAP server from outside the company intranet.
Some firms appreciate that someone cares enough to deal with problems and / or clients outside their contracted hours without being asked, so those on different continents don't end up waiting a whole day for a response.
Swings and roundabouts. I know which I'd rather be employed by, not that it has much relevance to SPF breaking forwarding.
Swings and roundabouts. I know which I'd rather be employed by, not that it has much relevance to SPF breaking forwarding.
k it upI was just going to start a thread about similar, when I spotted this one near the top. I sent an email which was bounced as spam before arriving at its destination. Since then my emails seem to be landing in junk folders, even to people I have sent emails (successfully) to before. I don't appear to be on any blacklists (although was unaware of them before reading the thread). Email is below (also had some previous exchanges as part of the text) and any help or pointers very much appreciated.
Hi xxxxx
Any news on the transfer as I need to get a van to move the chandelier and conscious that evenings are in short supply!
Let me know when you can.
Regards
xxxx
Hi xxxxx
Any news on the transfer as I need to get a van to move the chandelier and conscious that evenings are in short supply!
Let me know when you can.
Regards
xxxx
Something to look out for also - some email filters will scan any URLs in your email and if the site has been blacklisted in any way it will block the email. E.g. our website was on shared hosting and another site was doing something naughty so the website IP got blocked. We have the website URL in our email signature and so some more zealous email filtering recipients started to block email. To me this is a very good filter as of course you want emails containing URLs with a health warning to be blocked.
silverous said:
Something to look out for also - some email filters will scan any URLs in your email and if the site has been blacklisted in any way it will block the email. E.g. our website was on shared hosting and another site was doing something naughty so the website IP got blocked. We have the website URL in our email signature and so some more zealous email filtering recipients started to block email. To me this is a very good filter as of course you want emails containing URLs with a health warning to be blocked.
Oh it gets better than that.We got put on a the Spamcop RBL because one of our users forwarded on an email sent to him by a supplier (the BSI so hardly cowboys) containing a link to the BSI online store, to another company, which passed through a spam honeypot, which flagged the BSI online store as being on a URIBL, which led to us being flagged as spammers.
The whole bounce message for me is HUGE - several pages of gobbledegook.
The return code is 550 and the link offered by google 'for more information' suggests the recipient uses gmail (altho is their own domain address) and the bounce is spam related. Sending from my own domain also, email with registrar, domain points to a google blog.
The return code is 550 and the link offered by google 'for more information' suggests the recipient uses gmail (altho is their own domain address) and the bounce is spam related. Sending from my own domain also, email with registrar, domain points to a google blog.
Gassing Station | Computers, Gadgets & Stuff | Top of Page | What's New | My Stuff