Alexander, The patch has been approved for checkin. However, since it will only appear initially in daily it probably won't be helpful to you there. So let me know if you want me to merge the patch with a try build based on latest 115.* so you and your users can test it in real world. The primary change from the last try build is that it now handles the 4xx errors in the the response to RCPT TO and not just in MAIL FROM response. I haven't added a limit on the amount of time the SMTP connection can live or a limit on the number of messages to send on a connection other than the hardcoded 100 recipient limit that Magus added in his original patch, which I kept. Thanks.
Bug 1854567 Comment 35 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Alexander, The patch has been approved for checkin. However, since it will only appear initially in daily it probably won't be helpful to you there. So let me know if you want me to merge the patch with a try build based on latest 115.* so you and your users can test it in real world. The primary change from the last try build is that it now handles the 4xx errors in the the response to RCPT TO and not just in MAIL FROM response. I haven't added a limit on the amount of time the SMTP connection can live or a limit on the number of messages to send on a connection other than the hardcoded 100 recipient limit that Magnus added in his original patch, which I kept. Thanks.
Alexander, The patch has been approved for checkin. However, since it will only appear initially in daily it probably won't be helpful to you there. So let me know if you want me to merge the patch with a try build based on latest 115.* so you and your users can test it in real world. The primary change from the last try build is that it now handles the 4xx errors in the the response to RCPT TO and not just in MAIL FROM response. I haven't added a limit on the amount of time the SMTP connection can live or a limit on the number of messages to send on a connection other than the hardcoded 100 recipient limit (*) that Magnus added in his original patch, which I kept. Thanks. Edit: (*) To try to clarify this, you can have more than 100 recipients in messages queued in Outbox. But once messages are sent and the total recipient count exceeds 99, the current SMTP connection will be closed and a new connection established to send the remaining messages in Outbox, again with the 100 recipient limit. Example: 1000 messages in Outbox each with 1 recipient. This will use use 10 SMTP connections.
Alexander, The patch has been approved for checkin. However, since it will only appear initially in daily it probably won't be helpful to you there. So let me know if you want me to merge the patch with a try build based on latest 115.* so you and your users can test it in real world. The primary change from the last try build is that it now handles the 4xx errors in the the response to RCPT TO and not just in MAIL FROM response. I haven't added a limit on the amount of time the SMTP connection can live or a limit on the number of messages to send on a connection other than the hardcoded 100 recipient limit* that Magnus added in his original patch, which I kept. Thanks. Edit: *) To try to clarify this, you can have more than 100 recipients in messages queued in Outbox. But once messages are sent and the total recipient count exceeds 99, the current SMTP connection will be closed and a new connection established to send the remaining messages in Outbox, again with the 100 recipient limit. Example: 1000 messages in Outbox each with 1 recipient. This will use use 10 SMTP connections.