- 论坛徽章:
- 0
|
邮件服务器是qmail做的,搭建在公司内网的,通过NAT 隐射了25 80 110到该服务器上。163将我的邮件服务器认成了内网的ip地址,以前是正常的,非常郁闷,这样的问题有兄弟遇到过吗?如何解决
退信内容如下:
你发送到sea@xxx.cn的邮件由于以下原因被退回:sea@xxx.cn SMTP error, RCPT TO: 550 See http://spf.pobox.com/why.html?se ... 00.1&receiver=0 (#5.7.1)
0 rejected a message claiming to be from ae88978@126.com.
0 saw a message coming from the IP address 192.168.100.1; the sender claimed to be ae88978@126.com.
However, 126.com has announced using SPF that it does not send mail out through 192.168.100.1. That is why the mail was rejected.
If you are ae88978@126.com:
126.com should have given you a way to send mail through an approved server.
If you are using a mail program instead of webmail, you may need to update the SMTP server configuration setting according to your ISP's instructions. You may also need to turn on authentication, and enter your username and password in your mail program's "Preferences".
If you run your own MTA, you may need to set a smarthost or relayhost. If you are mailing from outside your ISP's network, you may also need to make your MTA authenticate SMTP using SASL. Ideally your server should listen on port 587 as well as port 25.
If your mail was correctly sent, but was rejected because it passed through a forwarding service, you can either mail the final destination address directly (it should be shown in the bounce message) or you ask the forwarder to implement SRS. If neither of these suggestions is practical, change your "-all" to "?all" until a more comprehensive approach to sender authentication involving cryptography solves the forwarding problem for good. For more information on this problem, see pages 15-16 of the SPF Whitepaper.
You can also try emailing your recipient at an alternative email address.
Please contact your ISP for further assistance; ask them for help in configuring outbound SMTP email.
If your company needs further help, we provide a full range of consulting services to help you resolve these problems quickly.
If you are confident your mail did go through an approved server:
The system administrator for 126.com may have incorrectly configured its SPF record. This is a common cause of mistakes.
Here's what you can do. Contact the system administrator responsible for 126.com and tell them that they need to change its SPF record so that it contains 192.168.100.1.
For example, they could change the record to something like
v=spf1 ip4:220.181.12.0/22 ip4:202.108.5.0/24 ip4:192.168.100.1 -all
If you can show this web page to your system administrator, they should be able to solve the problem.
If you did not send the message:
SPF successfully blocked a forgery attempt; someone tried to send mail pretending to be from you, but the message was rejected before anybody saw it. If you received a bounce message, you can delete it. This means SPF is working as designed. |
|