Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
Mailchimp, the online service for sending newsletters, has an statistics about how many people marked email you sent as spam. Does anybody know how this works? I am asking because I was thinking about how to implement this into my CMS which sends newsletters as well. Thanks for replies!
It's called FBL (feedback loop) and means that you register your MTAs (email sending servers) at the ISPs that supports FBLs (Yahoo, Hotmail etc.)
All you have to do is to sign up for every available FBL via their forms and then they will send you an email every time someone mark email sent from those servers as spam (spam complaints).
Then you'll have to parse those emails to get the information from it.
Have you checked Mailchimp Support?
http://kb.mailchimp.com/article/how-spam-filters-think
An abnormally high bounce rate is another indicator. Look through your hard bounces, and read the SMTP replies. Spam filters sometimes leave little clues about why they blocked your campaign (See: http://kb.mailchimp.com/article/why-did-my-email-bounce-smtp-replies).
Related
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
I'm working on a app which sends notifications emails. I know this is stereotypical for spam servers. I know the first question ist "How can I ensure what my server will not be listed as a spam server?" However I believe I should monitor my mailserver to ensure what every customer becomes his mails.
So the question: How can I check/monitor whether my server is listed as a spam server?
I really appreciate your help.
MXtoolbox (disclosure: I hold no relation to this site) has a great blacklist checking tool that checks all the major blacklists.
As for staying off them, make sure all your e-mails are opt-in and have an unsubscribe link within the e-mail body of every notification sent. Keep a record of all clients opting in, some hosting companies will charge you a small fortune if you get their IPs blacklisted.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I found some methods on filtering spam, one of these is Bayesian technique.
It tells about evaluating content, evaluating word in "content", not the mime info.
I want to ask,
are the mails spam, which is written by human and posted by programs automatically?
Here is a misundertanding. What is spam?
Even if the email is composed by humans, if it is unsolicited and sent in bulk it is spam.
Spam is unsolicited bulk e-mail.
If it is something you did not ask for end sent in bulk it is spam.
Your aunt writing to you (even if it's unsolicited) is not spam since it is one-on-one communication.
Receiving a newsletter you signed up for (even if sent in bulk) is not spam since you requested it.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 12 years ago.
Improve this question
I'm sending out a notification email every day to our customers, when new data in our service becomes available. No, it's not spam, it's a notification that customers have asked for, and can be turned off - just in case you were wondering. :)
I noticed that some websites have a noreply#domain.com address which they use to send all the notifications?
Why not just use an email address that is an alias to the support email. That way, if somebody replies to a notification (meaning they have a question) it goes directly to support. Why even bother explaining that "BTW, this email is not supposed to be used for support, please don't reply - use something else instead" when you could just have both pointing to the same inbox anyway? Or is there some other reason that I'm missing?
Maybe they don't want to read all the vacation and failure notices.
Small web sites probably do that, but eBay would be getting 10's of thousands of support emails per day (more than already) if that were the case. They could implement an automated filter of the noreply email address to find some that might need answering.
I guess it also comes to down to the fact that sending you an email from a noreply#* address isn't actually instigating a conversation. If they send you an email to which they want or need a response, or are responding to an email you've sent them, of course it makes no sense to use such an address.
So I don't think it's particularly down to technology, and more about expectations and conforming to people's existing mental models of how conversations and general sales pitches work.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
We use Google Apps (Gmail) to send and receive all of our email. Our application, which has grown in popularity over the years, sends email to its users per their request. It's not spam, it's important email they ask for.
Gmail (rightfully so) restricts the number of emails you can send. We get around this by queuing our mail and sending it at a slower pace, which works most of the time. We also use multiple email addresses to allow ourselves to send more than the 100-500 email limit.
Is there a way we can send email from our own SMTP server and follow all the proper rules and etiquette to not get flagged as SPAM? This way we can avoid GMail's restrictions.
Are there any good guides for setting up your own email SMTP server to send mail to avoid being flagged as SPAM?
Also, before anyone suggest that I use a 3rd party email sender, I need to be able to send these emails using Java.
(if this question is more appropriate on serverfault, I'm happy to move it)
I'd recommend http://sendgrid.com
It's quick to set up, well-priced, and they do much of the work to ensure your mail is deliverable (assuming you aren't sending spam in the first place, of course).
Oh and just to clarify, while Sendgrid is a 3rd party service, it's essential just a SMTP server in the cloud, so you should be able to switch from gmail to sendgrid by simply pointing at sendgrid's SMTP server instead of gmail's.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I am working on an email program and I want to add a basic way to detect spam based on the domain/sender of the mail. One service that I was looking at was gossip (http://gossip-project.sourceforge.net/) but I don't want to go to the hassle of setting up a dedicated Gossip server. I know that there are a lot of email blacklists (DNSBL's) and stuff out there that can give you an estimate of whether or not an email is spam based on the domain it was sent from. I'm wondering if anyone knows of one that I can just query from within a program by passing it the sender's domain and having it return the likelihood that the email is spam. I don't want a service that requires me to set up a server for it.
Anti-Spam Blacklists do list only IPs not domains. They can't list domains (of the sender) as the sender address can be (and usually is) forged.
So you can either lookup an IP in a DNSBL from where the mail was originating. Or you have to determine the probability of spam by analyzing the mail content. The latter is "expensive" in CPU cycles and other resources. In both cases you do not need a special server for that.
The better solution to prevent spam is at the server level. Block the mail before it enters your mail system. Then you don't have to mess with mail filters.