Ticket #2774 (closed defect: worksforme)
Opened 6 years ago
Last modified 5 years ago
E-Mail notifications lost when some cc addresses are invalid
| Reported by: | Dan <trac@…> | Owned by: | eblot |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | ticket system | Version: | 0.9.4 |
| Severity: | normal | Keywords: | notification email |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
Adding invalid addresses (e.g. spelled incorrectly) in the "cc" field may cause notifications to valid addresses to be lost. The addresses lost seem to be positional. For instance, with four addresses in the "cc" (plus a valid reporter), if the first and last "cc" addresses are to incorrect users, then none of the users receive a notification. If maybe just the first "cc" address is invalid, and there are two good addresses, maybe only the reporter notification is lost.
There seem to be some various combinations of behavior as to which addresses get the notifications versus location of invalid addresses in the string.
I believe this was also a problem in earlier Trac releases.
Platform is Win XP 64, Python 2.4.2
Attachments
Change History
comment:1 Changed 6 years ago by eblot
- Keywords notification email added
comment:2 Changed 6 years ago by eblot
- Owner changed from jonas to eblot
- Status changed from new to assigned
comment:3 Changed 6 years ago by eblot
- Resolution set to worksforme
- Status changed from assigned to closed
This problem should have been fixed in 0.10:
- Notifications are now send within a single post to the SMTP server, and SMTP servers accept an email if at least one out of the specified recipients is valid.
- Previous releases (0.9) used to post one email per recipient, so the delivery might have been interupted when the first error -invalid email address- was encountered.
Please re-open this ticket if you can reproduce the issue with a recent version:trunk



Notification implementation has been slightly rewritten in 0.10, I'll try to reproduce this issue.