Modify ↓
Opened 13 years ago
Closed 8 years ago
#9158 closed defect (wontfix)
Ticket Subscriptions preferences doesn't work
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | AnnouncerPlugin |
Severity: | normal | Keywords: | needinfo user-preferences |
Cc: | georgy.steshin@…, Ryan J Ollos | Trac Release: | 0.12 |
Description
When I'm trying to disable the notifications in user's preferences it doesn't work. It continues to send the notifications. This is my configurations:
[announcer] default_email_format = text/html email_enabled = true email_sender = SmtpEmailSender mime_encoding = base64 smtp_enabled = true smtp_from = ******** smtp_from_name = Bot smtp_password = ******* smtp_port = 2525 smtp_replyto = ***** smtp_server = ******* smtp_subject_prefix = [Trac] smtp_user = bot@syntomo.com ticket_subject_template = #$ticket.id: $summary ticket_email_header_fields = owner, reporter, milestone, priority, severity use_public_cc = false use_short_addr = false use_threaded_delivery = true use_tls = true
Attachments (0)
Change History (4)
comment:1 Changed 12 years ago by
Cc: | Ryan J Ollos added |
---|---|
Keywords: | user-preferences added |
Owner: | changed from Robert Corsaro to Steffen Hoffmann |
comment:2 Changed 12 years ago by
Keywords: | needinfo added |
---|
Any chance, that we get more information here? Thanks in advance for consideration.
comment:3 Changed 8 years ago by
Owner: | Steffen Hoffmann deleted |
---|
comment:4 Changed 8 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Please upgrade to Trac 1.2, which has integrated the core of AnnouncerPlugin. Please raise the issue on the trac:MailingList if you encounter the issue with Trac 1.2.
Note: See
TracTickets for help on using
tickets.
Sorry for the long time without response.
Thanks for reporting here, so we may figure out, if its really caused by software, or by a local installation/configuration issue. In such a case I generally recommend to use the mailing-list first, and not to assume a bug right-away, if you can't prove it. It helps with visibility too, as you may have learned by sitting here and waiting for comments to this ticket.
Only recently the previous author agreed to hand-over this plugin for maintenance. I'm already busy, but to resolve this issue for/with you I'll need to know a bit more about how to reproduce it. Would you be so kind as to provide hints/describe your steps and expected vs. experienced outcome in detail, please?