Closed Bug 362699 Opened 19 years ago Closed 17 years ago

"Reply with Template" filter rule is broken, sent to self instead

Categories

(Thunderbird :: Preferences, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: dbrown1113, Assigned: mscott)

Details

(Whiteboard: closeme 2008-08-28)

User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 2.0.50727) Build Identifier: Mozilla Thunderbird/1.5.0.8 Rule does not go to the person's inbox it keeps on going to Google's inbox instead. Reproducible: Always Steps to Reproduce: 1. Create E-mail that says something like Not at my desk for the subject and gone for the message. 2. save the message as a temlate 3. go to tools and Message filters. 4. Click the new button on the message filters window. 5. Filter name Gone 6. Match all of the following 7. To or CC 8. Contains 9. dbrown1113@gmail.com 10. Reply with template 11. Not at desk 12. Hit OK 13. close the message filters box. Actual Results: The e-mail's would go to my gmail.com inbox instead of the recipent e-mail inbox I tested it. Expected Results: I should have seen the template message in my other accounts inboxes instead of it going to my gmail inbox. Yes.
Group: security
Summary: A rule is broken in Mozilla Thunderbird and needs to be fixed it's the filter that responds to e-mail's. → "Reply with Template" filter rule is broken, sent to self instead
I'm confused. You set the filter to reply to (your, i presume) gmail, and you still don't expect it to reply to your gmail?
Ah, sorry, misread that... ignore last comment:)
But cannot reproduce, tested on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.1pre) Gecko/20061204 Thunderbird/2.0b1 ID:2006120403
Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)
Whiteboard: closeme 2008-08-28
RESO INCO per lack of response to the last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.