Opened 14 years ago
Closed 8 years ago
#8796 closed defect (fixed)
notifications also get sent to the smtp_always_cc address
Reported by: | Brecht Machiels | Owned by: | Steffen Hoffmann |
---|---|---|---|
Priority: | normal | Component: | AccountManagerPlugin |
Severity: | normal | Keywords: | email notification private |
Cc: | Ryan J Ollos | Trac Release: | 0.12 |
Description
I have the notification/smtp_always_cc option in trac.ini set to a mailing list address so that people can easily follow ticket changes. When AccountManager is sending notifications of user registration/deletion, these are also send to the smtp_always_cc address, in addition to the address(es) specified for AccountManager notifications. However, I don't want AccountManager to send to the smtp_always_cc address.
I have tried to adjust acct_mgr/notification.py to temporarily empty the smtp_always_cc option in the configuration, but this didn't seem to work. Probably I'm misunderstanding what is going on?
Attachments (1)
Change History (10)
comment:1 Changed 13 years ago by
Keywords: | email notification private added |
---|
Changed 13 years ago by
Attachment: | trac-accountmanager-fix-always_cc.patch added |
---|
Patch to fix this issue. The implementation is based on the SingleUserNotification below.
comment:2 Changed 13 years ago by
Cc: | Ryan J Ollos added; anonymous removed |
---|
comment:3 Changed 11 years ago by
Trac Release: | 0.12 → 1.0 |
---|
this workaround worked throughout trac 0.12 but now fails in trac 1.0.1. This issue makes it impossible for a trac to be sending ticket emails to a public list since all the username notifications go there too.
comment:4 follow-up: 5 Changed 11 years ago by
nevermind, it still works in 1.0, but you guys really need to commit this.
comment:5 Changed 11 years ago by
Trac Release: | 1.0 → 0.12 |
---|
Replying to mike_mp@zzzcomputing.com:
nevermind, it still works in 1.0, but you guys really need to commit this.
Point taken. But how about joining us? I could really use help with this high-profile plugin. Furthermore you could already assist by not changing ticket properties meant to help other developers spending their voluntary time more efficiently. Thanks for consideration and taking care.
comment:6 Changed 11 years ago by
whoops, didn't mean to change the release. The patch that's already attached works as is, you can commit it. Not sure what your testing procedure is.
comment:8 Changed 10 years ago by
Status: | new → accepted |
---|
comment:9 Changed 8 years ago by
Resolution: | → fixed |
---|---|
Status: | accepted → closed |
This isn't the only notification-related issue. Please give me the chance to look at it after I've finished the currently prepared release.