I looks like the 12759 defect is what we are seeing. What we were seeing previously and expected to see was the validation of the username as an email and then continued use forward. Looking at it, it looks like I will have to be broken until I can figure out a quick way to patch or until we get a 1.2.2 release with the fix in it. This is only of the few instances where I did this hot and I have a reasonably grounded belief that with the DB update that I can't roll back (too many new tickets in the system). Lesson learned; validate before rolling forward next time.
Any assistance on a quick way to get back up and running would be greatly appreciated. Matthew On Tuesday, April 11, 2017 at 12:19:36 PM UTC-4, Matthew Lavigne wrote: > > 1.2.1, just upgrade on 4/4 and within 24hrs this started to occur. Going > to look at those bugs now. > > On Tuesday, April 11, 2017 at 12:14:09 PM UTC-4, RjOllos wrote: >> >> >> >> On Tue, Apr 11, 2017 at 9:11 AM Matthew Lavigne <[email protected]> >> wrote: >> >>> All, >>> >>> I just upgraded a trac 1.0x instance that was an upgrade from .10 a long >>> time ago. We auth via ldap which is our business email address. >>> >>> Since the upgrade to 1.2 we have noticed that there is a level of >>> randomness to whether or not a user gets an email when they submit a ticket >>> or any followup on the ticket. >>> >>> in the trac.ini I have the following: >>> >>> >>> smtp_always_bcc = [email protected],[email protected], >>> [email protected] >>> >>> and if my user ([email protected]) does not have an email address set >>> in preferences then I see this in the log file (currently running in DEBUG): >>> >>> 2017-04-11 11:59:24,864 Trac[api] DEBUG: Adding ([email protected] >>> [1]) for 'always' on rule (AlwaysEmailSubscriber) for (email) >>> 2017-04-11 11:59:24,864 Trac[api] DEBUG: Adding ([email protected] >>> [1]) for 'always' on rule (AlwaysEmailSubscriber) for (email) >>> 2017-04-11 11:59:24,865 Trac[api] DEBUG: Adding ([email protected] >>> [1]) for 'always' on rule (AlwaysEmailSubscriber) for (email) >>> 2017-04-11 11:59:24,865 Trac[mail] DEBUG: EmailDistributor has found the >>> following formats capable of handling 'email' of 'ticket': text/plain >>> 2017-04-11 11:59:24,866 Trac[mail] DEBUG: EmailDistributor was unable to >>> find an address for: [email protected] (authenticated) >>> 2017-04-11 11:59:24,885 Trac[mail] DEBUG: EmailDistributor is sending >>> event as 'text/plain' to: [email protected], [email protected] >>> 2017-04-11 11:59:24,891 Trac[mail] INFO: Sending notification through >>> SMTP at localhost:25 to ['[email protected]', '[email protected] >>> '] >>> >>> >>> The problem is that the ticket system in secondary to all the rest of >>> the work that is going and and getting 300+ people to go in and 'fix' their >>> preferences is much more painful then one would like to guess. >>> >>> >>> I have looked through all the documentation and I do not have a good >>> place to start looking to figure out how to get back to the desired >>> behavior, which is to email the username (which has to be valid to be able >>> to log on to the system). >>> >>> Any thoughts/suggestion would be appreciated. >>> >>> Matthew Lavigne >>> >> >> Might be related to: >> https://trac.edgewall.org/ticket/12759 >> https://trac.edgewall.org/ticket/12658 >> >> Are you running Trac 1.2 or 1.2.1? >> >> - Ryan >> > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/trac-users. For more options, visit https://groups.google.com/d/optout.
