邮件发送，用户电子邮件作为发件人 [英] Mail sending, with users email as sender
问题描述
我的网站上的用户使用电子邮件形式通过电子邮件联系。
邮件正以您的用户电子邮件作为发件人发送！ / p>
如何防止邮件结束在垃圾邮件文件夹？
特别是Hotmail喜欢将邮件发送到垃圾邮件文件夹。
我的主机具有Reverse DNS和SPF保护，我已经阅读了一些。
但是当我发送电子邮件时，用户将电子邮件作为发件人
解决方案的简单方法是不要这样做
不幸的是，改进电子邮件可交付性的真正解决方案涉及更多。
SPF 是发件人政策框架，其基本上允许电子邮件主机明确指定哪些服务器被授权从从给定域的地址发送电子邮件。由于垃圾邮件和网络钓鱼攻击的地址欺骗，这变得越来越普遍。如果您尝试使用SPF向用户的电子邮件地址发送，那么最好的情况是这些邮件将垃圾邮件发送给垃圾邮件，而更有可能的结果是（垃圾邮件标记的）电子邮件或默默地取消了一个大警告完全掉下来
rDNS 通常用于显示电子邮件发件人的IP和域之间的有效关系。 （如果您从发送用户，那么您没有有效的关系。）
这些事情将表明您的电子邮件不可靠，因为您声称自己不是从特定的域发送。
不要发送从这些用户，使用代表标头和/或回覆标题。
只有这样，这不会让你脱离垃圾邮件文件夹。除了正确使用电子邮件标题外，您需要做什么以确保可交付性如下：
-
从您的域中的地址。通常情况下，这是一个非受监控的帐户，配置为丢弃所有传入的消息或解析它们以进行退回，并相应更新系统。
-
配置SPF，DKIM和您的电子邮件中的域密钥。这将增加您的电子邮件不会被标记为垃圾邮件的可能性。
-
成为符合CAN-SPAM的。这样既能提高垃圾邮件的分数，又可以方便用户选择退出，您可以减少报告为垃圾邮件标志，这样可以帮助您避免黑名单。
-
在垃圾邮件黑名单中监控您的IP地址，因为这样会发生。与个别提供者合作以获得移除。监控黑名单状态的一个受欢迎的地方是 mxtoolbox.com
-
耐心等待许多大电子邮件托管公司对垃圾邮件非常积极。通常，他们使用内疚直到被证实无辜的方式，意味着人们必须将垃圾邮件从垃圾邮件中提取出来，从灰色主义者到白名单，您可以遵循以下步骤获得白名单通常情况就是逐案。
另一种选择是使用为您管理1-5的中继服务，但需要付费。个人来说，我有一个专门的IP解决方案， sendgrid.com ，因为管理电子邮件这些天是一个真正的麻烦。除了作为客户，我与sendgrid没有任何关系。
The users on my site contact each other by e-mail using an e-mail form.
The mails are being sent with thee user email as sender!
How do I prevent the mails from ending up in the spam folder?
Especially hotmail likes to throw the mail sent in the spam folder.
My host has features like "Reverse DNS" and "SPF Protection", which I have read a bit about.
But are they applicable when I am sending e-mails with the users e-mail as sender?
The simple way to fix it is don't do that!
Unfortunately the real solution to improving email deliverability is much more involved.
SPF is "Sender Policy Framework" which basically allows an email host to explicitly specify which servers are authorized to send email from an address at the given domain. This is becoming increasingly common due to from address spoofing by spam and phishing attacks. If you are attempting to send from a user's email address with an SPF your best case these days is email in the spam with a more likely result being a big warning on the (spam flagged) email or getting silently dropped altogether.
rDNS is generally used to show a valid relationship between the ip and the domain of the email sender. (if you are sending from a user then you don't have a valid relationship.)
Both of these things will indicate that your emails are not trustworthy because you are claiming to be sending from a particular domain when you aren't.
Don't send "from" those users, use the on-behalf-of header and/or the reply-to header.
That alone won't keep you out of the spam folder though. Beyond using email headers correctly, What you need to do to ensure deliverability is the following:
Send from an address in your domain. Typically this is a non-monitored account either configured to drop all incoming messages or parse them for bounces and update your system accordingly.
Configure SPF, DKIM and possibly Domainkeys on your email. This will increase the likelihood that your email won't be flagged as spam.
Be CAN-SPAM compliant. This will both improve your spam score, and by making it easy for people to opt-out, you get less "report as spam flags" which will help keep you from getting blacklisted.
Monitor your IP address in spam blacklists as it will happen anyway. Work with individual providers to get removed. One popular place to monitor your blacklist status is mxtoolbox.com
Be patient. Many big email hosting companies are very aggressive about spam. Often they employ a "guilt until proven innocent" approach meaning people have to take your email out of spam an unspecified number of times before you go from 'greylisted' to 'whitelisted.' Some hosts have a procedure you can follow to get whitelisted but often it's a case by case basis.
The alternative is to use a relay service that manages 1-5 for you, but at a cost. Personally I have a dedicated IP solution with sendgrid.com because managing email these days is a real hassle. I have no relationship with sendgrid other than being a customer.
这篇关于邮件发送，用户电子邮件作为发件人的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
