I wrote a PHP e-mail code a few days ago and passed the 126 mail sending test. Later, the customer bought the enterprise post office and Netease,
I think this is not a problem with my code. Therefore, I Went To Netease's enterprise Post Office Management page to find the cause. Indeed, it was a domain name MX DNS resolution error, after configuring according to the above steps, try again the next day...
This is the first two big ones. It's too nonsense. Let's go straight to the question.
During this period, a bunch of debugging and repetition were conducted .. Repetition...
At last, I used telnet to verify the enterprise post office. I found that the enterprise post office account must use your own domain name as an account, while ordinary accounts do not need a suffix, for example, when the abc@126.com verification we will ABC base64 computation sent to the mail server for verification, and enterprise post office account for the abc@youname.com then you have to use the abc@youname.com for base64 computation sent to the mail server, on, the problem is here, Khan. This is because the code intercepts the part of the account @ and uses it as the login account. Then, you only need to remove this part and it will be OK.
When writing a mail class, the constructor can add a parameter, that is, whether the enterprise Post Office is used, which is more flexible to handle. Haha --~!~