#9: new test ticket --------------------+---------------------- Reporter: mattdm | Owner: Type: task | Status: closed Priority: normal | Milestone: Future Component: --- | Resolution: invalid Keywords: | --------------------+---------------------- Changes (by mattdm):
* resolution: => invalid * status: new => closed
On 01.04.2014 15:26, cloud wrote:
#9: new test ticket --------------------+---------------------- Reporter: mattdm | Owner: Type: task | Status: closed Priority: normal | Milestone: Future Component: --- | Resolution: invalid Keywords: | --------------------+---------------------- Changes (by mattdm):
- resolution: => invalid
- status: new => closed
Is there a reason why these mails don't have a visible recipient? This basically bypasses my filter. If the target is the mailing-list then its address should be put into the "To:" header.
Regards, Dennis
On Tue, Apr 01, 2014 at 06:21:53PM +0200, Dennis Jacobfeuerborn wrote:
Is there a reason why these mails don't have a visible recipient? This basically bypasses my filter. If the target is the mailing-list then its address should be put into the "To:" header.
Ouch. "Something stupid in trac", I'm afraid. I'll figure it out / make sure someone figures it out.
But, for the record -- filter mailing lists on "List-Id:" to avoid all sorts of problems along these lines.
On 01.04.2014 20:59, Matthew Miller wrote:
On Tue, Apr 01, 2014 at 06:21:53PM +0200, Dennis Jacobfeuerborn wrote:
Is there a reason why these mails don't have a visible recipient? This basically bypasses my filter. If the target is the mailing-list then its address should be put into the "To:" header.
Ouch. "Something stupid in trac", I'm afraid. I'll figure it out / make sure someone figures it out.
But, for the record -- filter mailing lists on "List-Id:" to avoid all sorts of problems along these lines.
Did not know that header existed so thanks for pointing that out. I shall go a do some filter editing :)
Regards, Dennis