You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we add an e-mail to the queue with a "bad" (does not comply with RFC 2822) address, this results in an error in the log:
app.CRITICAL: An exception occurred. {"exception":"[object] (Swift_RfcComplianceException(code: 0): Address in mailbox given [##form_email##] does not comply with RFC 2822, 3.6.2. at /home/public_html/contao4-managed/vendor/swiftmailer/swiftmailer/lib/classes/Swift/Mime/Headers/MailboxHeader.php:345)"} []
But the e-mail in the queue does not change the status to "error", it is still "queued".
That means, all future mails never get processed - even if there address would is ok.
We tested this in the "reply-to" field, but i assume it also happens with the sender, to, cc, bcc, etc. fields
Is it possible, that you could check the address and if it is not ok or catch the error that lands in the log and change the status to "error" so the queue doesn't get blocked by a single message?
The text was updated successfully, but these errors were encountered:
If we add an e-mail to the queue with a "bad" (does not comply with RFC 2822) address, this results in an error in the log:
But the e-mail in the queue does not change the status to "error", it is still "queued".
That means, all future mails never get processed - even if there address would is ok.
We tested this in the "reply-to" field, but i assume it also happens with the sender, to, cc, bcc, etc. fields
Is it possible, that you could check the address and if it is not ok or catch the error that lands in the log and change the status to "error" so the queue doesn't get blocked by a single message?
The text was updated successfully, but these errors were encountered: