I am sending email using cakephps email function. The email sends correctly but it is going to the spam folder.
Can anyone sugggest?
There can be many causes:
The email's content looks like spam (lots of links within a little amount of text, too much alpha-numeric gibberish, certain common spam words)
The server from which you're sending the emails has been black-listed
The email is not properly formatted (so in your case, check that you're using CakePHP's email function fully correctly)
I would try to send a good length, regular email without any links, as if you were writing to a friend, and see if it's a content issue. If the server you're emailing from has been identified as a source of spam and is black-listed by an ISP, there's not a whole lot you can change about that.
It can happen due to your mail content.
Check your mail contents that contain somethings that spam filter count.
Related
A bit of a particular question here
Let's say:
Jane emails Bill and her email ends up in spam
Then Jane emails Jebediah and her email does NOT end up in spam.
Assuming nothing changed in email setup and Jebediah got Jane's email because Jane was in his contacts:
Will the email headers in both instances look the same?
Our sysadmin team insists that they need emails from within the spam folder, but wouldn't they be identical in both cases if nothing changed on Jane's side.
While this is highly installation specific, some filtering packages do inject diagnostic headers into the email that indicates why the message was classified a particular way. These can be useful in identifying faults in delivery.
Google and Hotmail do this fairly reliably, though other services have different behaviour.
Remember, even if an email message was sent with identical headers to two different people the way the message was received can be dramatically different. The SMTP processing pipeline can be quite complicated and a number of processes can tap in, insert, remove, or otherwise manipulate headers before it ends up in the inbox.
The headers might be very similar. There are some tricks that legitimate business can use to verify their ownership of the domain (DKIM) and providence of the email itself (spf).
In the absence of these tools, systems use text-based filters to determine "spammyness". Some big email handlers (think Google, Yahoo, etc) have a large body of spam and have gotten quite good at just looking at the content to determine spammyness.
Actually I am facing a lot of problem about email sending. When I am trying to send a email using a module named phpmailer that contains an anchor tag or hyperlink as like
click here
email go to the spam folder but when i remove this anchor tag or remove the link from the body of the email its send properly and goes to inbox.
i do not get what was the problem.
i am using a shared hosting with cpanel.
please anybody help me.
For all links? Or just links to a particular site?
You might want to check that the site you're linking to isn't listed in SURBL or similar blacklist.
It's also worth inspecting headers on received messages - spam filters will often add headers telling you why it classified a message as spam.
Generally there is nothing specific you can do - if there was an obvious way to avoid spam filters then spam senders would use it and the filters would be useless. That said, almost every receiver uses entirely different spam filtering, so your results may vary enormously anyway.
Not sure if this is in the right place, but it's all stemming from a PHP email send script that isn't working.
I have an email server for my clients that exists at email.thoughtspacedesigns.com. I run multiple domains from this server (e.g. pittsburghphotography.co). I've set up SPF and DKIM for these external domains, and plain text messages are going through just fine, but anything that contains an HTML attachment (even if it's accompanied by plain text) is going directly to spam when sent to any gmail account. So for example, if I send an HTML email from contact#pittsburghphotography.co, regardless of the client I use (Mac Mail, WordPress, pure PHP script), it goes into spam. I'm not sure what I can do to circumvent this issue as I've already set up just about all of the verification factors I thought were possible. Any insight?
Emails can get sent to the spam folder for a variety of reasons. Here are some things you might look into:
Every email server has a numbered rating and that can effect how your email is delivered. Check that at senderscore.org.
Another thing you might look into is if your email server is on any "Black lists" meaning that you tanked your senders score and got put on a list as a know spammer. Don't feel bad if you are, it's easy to wind up on one. Check for that at blacklistmonitoring.com.
Also, a simple way to check for spam keywords is isnotspam.com. There are other spam checkers out there but that's the one I like.
EDIT: I also forgot to mention gmail can be a bit more fickle than other email clients when it comes to spam. It's just something in their spam filtering algorithm that is more sensitive than other applications.
Best of luck!
I'm writing an app which allows users to send out a text-only email to a bunch of recipients. I want to try and generate the subject of this email from the body of the message, to avoid the need for a subject field
Is it safe enough to do this? Are these emails likely to fall foul of spam filters?
I'm already scanning the entire email for spam words, so there won't be any in the subject
you could download the widely used spamfilter Spamassassin and search for 'SUBJ' in the *.cf files, this will give you many spamrules that trigger based on subject (like empty subject, all caps, bad words, bad encoding of non-ascii characters etc)
I would suggest that if the mail is from a trusted source then there is not a problem. On the other hand since the mailbox dosent know that the subject is generated automatically it does not matter to them. And the third thing is that you need to check the guidelines that the email filters follow. Check out some ope source mail filter.
Am trying to determine the best way to persist information from an originating email, through to a reply back.
Essentially, it is to pass a GUID from the original email (c#), whereby when the receiver replies back, that GUID is also sent back for reference.
I have tried setting the MessageID, whereby using Outlook, the In-Reply-To value is set with the original ID, however using some webclient email systems, that value is not created on reply. Is there another way to sent this info through email headers?
Some variation on VERP is probably the most reliable...
http://en.wikipedia.org/wiki/Variable_envelope_return_path
Specifically, instead of having all your replies coming to the same address, encode the information you want to persist into the From address for the email.
For example, in the case of a helpdesk ticket, you could use something like:
From: Helpdesk <support-ticket-123#example.com>
To: End User <user#example.org>
Subject: Ticket #123 - problem with computer.
That way, regardless of what the user edits in the subject or text, you know what ticket is being referred to by the receiving email address.
I don't think you'll be able to do anything that is perfectly reliable by headers alone -- the number of clients that would have to cooperate is immense.
Most systems that do this work by including something in the body of the email that is sent that allows it to identify the message, and including text instructing the recipient to include that block of text in the response. You could also try including it in the subject (and including text in the body to leave the subject unchanged). That's how some mailing list managers I've seen do it.
I stumbled upon this question, and it's been very informative. This, however, leaves me with one question: Will using VERP, or a variation of editing the 'reply-to' or 'from address', cause the messages to be locked up in spam filters?
I have read that spam senders often change the bounce address to prevent their servers from getting clogged with bad email address bounces. Is it a spam risk to assume this approach?
The most reliable way is to put the ID in the subject, which should be preserved throughout replies.
(It doesn't hurt to tell your users that they should keep the subject intact.)
RT, a popular ticketing system, does this. They use a simple subject format like "[Ticket #123]" and key off of 123.