View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020532 | mantisbt | public | 2016-01-20 07:57 | 2016-05-04 17:55 | |
Reporter | rbrinkma | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | unable to reproduce | ||
Product Version | 1.2.17 | ||||
Summary | 0020532: Mail cron job will stop on an unknown mail adress on Exchange Server | ||||
Description | We use cron job to send out mails on a 5 minute interval schedule and mails are send to an Exchange server. It appeared that two (expired) email accounts were removed on the Exchange Server that still were in Mantis configured as administrator. Cron Mail job got stuck because the Exchange Server sends back an <SMPT Error user unknown> which resulted in a stall of the email cron job. Mantis should skip unknown mail adresses on Exchange Server to continue Cron Job | ||||
Steps To Reproduce |
| ||||
Additional Information | AUTOSIGNUP MAIL ERROR LOG 2016-01-17 23:16 CET mail Server not responding for 5 seconds, aborting SMTP server error: 5.1.1 User unknown 2016-01-17 23:21 CET mail Server not responding for 5 seconds, aborting SMTP server error: 5.1.1 User unknown | ||||
Tags | No tags attached. | ||||
Fixing this would probably require patching email API. That being said, it is also your responsibility to monitor the send queue and take necessary corrective action when you see it grow indefitely. Currently, email_send() only returns a true/false status and logs any errors to the logs. Assuming that PHPMailer returns some significant, standard error code (or throws a specific exception), we could improve the error handling to deal with this situation. However, what I don't want to do is make server-specific changes. Since I don't have an exchange configuration to test, it would be helpful if you could provide a var_dump() of the phpmailerException $e in the catch() block around line 1077 in this situation. |
|
Unfortunately we could not reproduce this issues, because of some unknown configuration change on de Exchange Server last week. We are in the proces of finding out what change was made. |
|
OK, let us know. |
|
rbrinkma, You did not provide any feedback; I am therefore resolving this issue as "unable to reproduce". Feel free to reopen the issue at a later time and provide instructions to reproduce the issue . |
|