Yes, I guess that's one way, kind of like including debug statements in code, but rather tedious as you say.
I think I may have hit on what's going on but I'll wait a while for some more list traffic to come in and then report back if I turn out to be right. poc On Mon, Jul 22, 2013 at 4:00 PM, Andy <[email protected]> wrote: > It would be helpful if Gmail had a debugging option to trace exactly which >> filters were triggered by a given message, but I don't know if such a thing >> exists. >> > > You could do some debugging yourself, though I realize it could be tedious > if you have many. Maybe there's an XML editor that could make it easier. > I'm thinking you could duplicate all of your filters; then have the first > one assign a new label "filter1", and so on. Then you could see which > filter was responsible. > > Andy > > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Gmail-Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/gmail-users/_XKMxq3Fn_0/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/gmail-users. > For more options, visit https://groups.google.com/groups/opt_out. > > > -- You received this message because you are subscribed to the Google Groups "Gmail-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 http://groups.google.com/group/gmail-users. For more options, visit https://groups.google.com/groups/opt_out.
