Closed Bug 301808 Opened 20 years ago Closed 15 years ago

Mail Filter Forward To: produces a 'Send of Mail failed' Alert (when Filters for "Local Folders". No Enigmail)

Categories

(MailNews Core :: Filters, defect)

Product:
MailNews Core
Component:
Filters
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(blocking-thunderbird3.1 -)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
blocking-thunderbird3.1 --- -

People

(Reporter: skthornber, Unassigned)

References

(Depends on 1 open bug)

Details

(Keywords: qawanted, Whiteboard: Open separate bug if Enigmail is used, please.)

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.0.3705; .NET CLR 1.1.4322) Build Identifier: Mozila - version 1.0+ (20050712) I have created filters for multiple accounts that take inbound mail to the local inbox then filters here to sort and file as required. I saw the new filter line in the A2 version and realised it would be good for me to reforward appropriate mail to my work account. All other features seem to work still following upgrade to A2. I am using IE6 XPSP2 and majority of the new Security features of XPSP2. Reproducible: Always Steps to Reproduce: 1.Created multiple accounts - set a filter here as From isnt gibberish@gibberish.com and set move to folder: Inbox on Local folders this works fine and moves all accounts mail to the local inbox. I then have a set of filters enabled that run on the local inbox which copy move label as required this too works fine at this stage. 2.I have then gone into a couple of these Filters and ticked the forward to: making the assumption that the Move to folder: can remain ticked. I have set the email address to a ligitimate account. 3.I have checked that I can manually forward mail and this works fine including multiple seletions being sent. Actual Results: As soon as I run the filter an Alert box is issued with the 'Send of Mail failed' Expected Results: I would expect the software to select my SMTP outbound mail account and automaticaly forward a copy of the mail to the selected outbound address. At the same time I would expect the original mail to have been left in the inbox or moved to: as required. I am saying this is a minor loss of feature wit a work round because I can manually forward messages. However it is / will be a very useful feature for me when it works as I work away from home and the ability to re-forward specific mail to my work account is magic ---- Keep up the good work. Stephen
I believe this will be fixed by the fix for bug 299982
Depends on: 299982
Version: unspecified → Trunk
skthornber@dsl.pipex.com, could you grab one of the latest builds and see if you're still seeing this? http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/
This occurs on the latest nightly build still.
Looking further - it creates the sent message, but never actually sends it.
I'm unclear on a few things: 1. Are the messages coming from a pop3 server, and then getting filtered as they arrive into the local folders inbox? 2. Is the forward action happening when the filters automatically run on incoming mail, or are you running the filter manually, after the fact?
Assignee: mscott → bienvenu
Status: UNCONFIRMED → NEW
Ever confirmed: true
David, > Are the messages coming from a pop3 server, and then getting filtered as > they arrive into the local folders inbox? Yes, they are. In this case, I have two POP3 accounts going to local folders, with the filter forwarding it to one of my IMAP accounts (so SpamAssassin can run on them, FWIW). > Is the forward action happening when the filters automatically run on > incoming mail, or are you running the filter manually, after the fact? I've tried both ways. In the course of trying to pin down exactly what doesn't work, I've come up with these observations. 1) if I define a filter for the mail account, rather than for Local Folders, the rule triggers just fine when mail is received and the message is sent (and received) successfully. 2) however, the error message occurs for every message when you try to run the filters manually. 2.5) running the rule manually via Tools->Run Filters On Folder only invokes the Local Folders rules, not the per-account ones, but I'm sure you knew that 3) defining the forward rule under Local Folders did NOT work, I was sure, for incoming mail - but all of a sudden, it did, after I'd done the per-account checking. Mail is successfully forwarded upon arrival. 4) Repeating the test for #3, i.e. blank inbox, sending mail to self to run filter, caused a TB crash - reported via talkback with a reference to this bug #. 5) The crash in #4 stuffed the account - it can no longer download mail, and leaves TB in a state where you can't access other mail, bring up the message filter list, etc, etc. It needs to be process-killed and the message deleted via other means. 6) Trying to access the message filters screen after #5 has occurred crashes TB - reported again. At this point, I rolled back to the release version :)
And my final two points (yes, I'm a glutton for punishment): 7) rolling back to release, deleting the 'forwarding' mail filters, and rolling forward again fixes the stuck account problem. 8) recreating the filters leads straight BACK to the stuck account problem again. TB sits there saying "Downloading message 1 of 1" and pretty much doesn't work again.
Last notes in the filter log (why can't I copy and paste it?): Applied filter "Forwarding 1" to message from Damian Glenny <xxx@xxx.com> - test at 2005-10-29 16:20:17 Action = Forward Applied filter "Forwarding 1" to message from Damian Glenny <xxx@xxx.com> - test at 2005-10-29 16:20:17 Action = Delete Applied filter "Forwarding 1" to message from Damian Glenny <xxx@xxx.com> - test at 2005-10-29 16:20:14 Action = Delete I particularly like how it went backwards in time.
Depends on: 314471
(In reply to comment #0) > User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET > CLR 1.0.3705; .NET CLR 1.1.4322) > Build Identifier: Mozila - version 1.0+ (20050712) > > I have created filters for multiple accounts that take inbound mail to the > local inbox then filters here to sort and file as required. I saw the new > filter line in the A2 version and realised it would be good for me to reforward > appropriate mail to my work account. All other features seem to work still > following upgrade to A2. I am using IE6 XPSP2 and majority of the new Security > features of XPSP2. > > > > Reproducible: Always > > Steps to Reproduce: > 1.Created multiple accounts - set a filter here as From isnt > gibberish@gibberish.com and set move to folder: Inbox on Local folders > this works fine and moves all accounts mail to the local inbox. I then have a > set of filters enabled that run on the local inbox which copy move label as > required this too works fine at this stage. > 2.I have then gone into a couple of these Filters and ticked the forward to: > making the assumption that the Move to folder: can remain ticked. I have set > the email address to a ligitimate account. > 3.I have checked that I can manually forward mail and this works fine including > multiple seletions being sent. > > Actual Results: > As soon as I run the filter an Alert box is issued with the 'Send of Mail > failed' > > Expected Results: > I would expect the software to select my SMTP outbound mail account and > automaticaly forward a copy of the mail to the selected outbound address. At > the same time I would expect the original mail to have been left in the inbox > or moved to: as required. > > I am saying this is a minor loss of feature wit a work round because I can > manually forward messages. However it is / will be a very useful feature for me > when it works as I work away from home and the ability to re-forward specific > mail to my work account is magic ---- Keep up the good work. Stephen > In my experience: Nonworking filter: "From is abc@xyz: Forward to def@uvw." Working filter: "All apply: To is ghi@rst, From is abc@xyz, Forward to def@uvw." That To check seems to be what it needs even though the filter is under the ghi account. Just a bit of a glitch in an otherwise fine program.
In reply to comment 9 - I just tried again on 1.5.0.2, including a check for the To field, and I get the same results as in comment 6. Thunderbird requires a process kill, and I need to manually delete the email from the POP3 queue before it will work again.
Following is my test result with SeaMonkey trunk-2006092308/Win-2K. (1) Account definitions (No Global Inbox environment) account1 : Default account. Dummy POP3 server. SMTP1 for main&only identity(mail_addr_1) account2 : Normal POP3 server. SMTP2 for main&only identity(mail_addr_2) (received mails have "X-Account-Key: account2") account3 : Dummy POP3 server account. SMTP3 for main&only identity(mail_addr_3) (SMTP3 is dummy SMTP server, then fails if try to connect) Local Folders (2) Copy a mail received by account2("X-Account-Key: account2") to Inbox of account3 and "Local Folders". (3) Create filter rule of "Forward Message To" for the copied mail in message filter for account3 and for "Local Folders". (4) "Run Filters on Folder" of Inbox of account3 => "Send of Mail failed" message with saying "error on SMTP3". This indicates that SMTP is not chosen from "X-Account-Key:", account definition instead. (5) "Run Filters on Folder" of Inbox of "Local Folders" => "Send of Mail failed" only message(no other information). (6) Compose of "New Message" while "Local Folders" is selected => From: is set as mail_addr_1 (Default account's one) (7) Reply to the mail copied from account2 while "Local Folders" is selected => From: is set as mail_addr_2 (account2's one. Gotten from X-Account-Key:) Test result (4) indicates that: - When action of "Forward Message To" of message filter, Thunderbird tries to find SMTP server thru mail.account.accountP.identities & mail.identity.idQ.smtpServer where accountP is currently chosen account. (Not default account, nor account in X-Account-Key: header) (This means Bug 327713 is already resolved if message filter :-)) If "Local Folders", mail.account.accountP.identities is not defined. (mail.account.accountP.server only when "Local Folders") Then there is no way to find mail.identity.idQ.smtpServer thru mail.account.accountP.xxx for "Local Folders" account. This seems to be cause of error when "Local Folders". David, is it right?
*** Bug 327445 has been marked as a duplicate of this bug. ***
QA Contact: general
This is still not working in TB 2.0.0.4 "Sending of message failed. Please verify that your Mail & Newsgroups account settings are correct and try again." The outgoing server is set correctly and I have a filter that matches two subject criteria (ie. "Subject contains Emailing AND Subject contains .pdf" to address recent spam to be forwarded to spamcop) Then I have a "forward to" action followed by a delete action. If I remove the delete action, it doesn't work either.
I can report this bug for 2.0.0.5 / Windows XP, too.
(In reply to comment #13) > This is still not working in TB 2.0.0.4 (In reply to comment #14) > I can report this bug for 2.0.0.5 / Windows XP, too. To J.M.Roth & buelter@kennziffer.com : (Q1) Do you use Global Inbox? (Q2) Is account who owns the Global Inbox "Local Folders"? (Q3) Is filter rule that has action of "forward to" defined in message filter for "Local Folders"? If all answers is "Yes", (Q4) Can following be a workaround? - Move the filter rule in message filter for "Local Folders" to message filter for hidden account(who uses Inbox of "Local Folders" as Global Inbox)
> (Q1) Do you use Global Inbox? No, I use an IMAP account, for which you cannot use Global Inbox.
(In reply to comment #16) > No, I use an IMAP account Oh IMAP case, instead of "Local Folder" case in Comment #0 and Comment #6. To J.M.Roth: Do you enable quarantine option?
(In reply to comment #17) > (In reply to comment #16) > > No, I use an IMAP account > Oh IMAP case, instead of "Local Folder" case in Comment #0 and Comment #6. Is that a question? > Do you enable quarantine option? You mean anti-virus quarantine? Usually yes. However now, I tried running a filter manually to forward some mails with quarantine off (if that is an accurate test case), it doesn't change anything (still not working).
(In reply to comment #18) To J.M.Roth: Do you use "offline use" option? (Properties/Offline of Inbox)
I changed account/server number for "Local Folders" from 1 to 999(for ease of edit of prefs.js), and added identity of id999 for "Local Folders", and set to "Use default SMTP server". > user_pref("mail.account.account999.identities", "id999"); <= Added > user_pref("mail.account.account999.server", "server999"); <= Number changed > user_pref("mail.server.server999.name", "Local Folders"); <= Number changed > user_pref("mail.identity.id999.smtpServer", ""); <= Added > user_pref("mail.smtp.defaultserver", "smtp1"); > user_pref("mail.smtpserver.smtp1.hostname", "smtp.server"); > user_pref("mail.smtpserver.smtp1.realhostname", "smtp.server"); When filter action of of "Forward to" is executed for Inbox of "Local Folders", send error message for "smtp.server" was displayed, instead of error message without SMTP server name. This test result indicates that my guess of comment #11 is not wrong. And this result also indicates that above can be a workaround of this bug. (Sorry but I don't know side/bad effect of adding identity to "Local Folders".)
Workaround when "Global Inbox": "Inbox for different account", instead of "Global Inbox(Local Folders Account)"
(In reply to comment #19) > (In reply to comment #18) > To J.M.Roth: Do you use "offline use" option? (Properties/Offline of Inbox) > No
To J.M.Roth: adding next 3 lines in user.js(or prefs.js) will change situation? (account1 is account for "Local Folders" usually) > user_pref("mail.account.account1.identities", "id999"); > user_pref("mail.identity.id999.smtpServer", "smtp1"); > user_pref("mail.identity.id999.useremail", "xxx@yyy.zzz");
I have now quickly checked a few things. If I use a POP3 account (NOT in Local Folders/Global Inbox) it gives me the same error message than stated previously with the IMAP account. If I use a POP3 account with LocalFolders, then it doesn't give me any error at first, but it doesn't forward either. When I then try to run the filter manually, it just says "Sending of message failed." (not more!)
(In reply to comment #23) > To J.M.Roth: adding next 3 lines in user.js(or prefs.js) will change situation? > (account1 is account for "Local Folders" usually) > > user_pref("mail.account.account1.identities", "id999"); > > user_pref("mail.identity.id999.smtpServer", "smtp1"); > > user_pref("mail.identity.id999.useremail", "xxx@yyy.zzz"); > What you suggested here adds lots of strange stuff to LocalFolders->Server Settings (including Port=-1 etc.) in the Account Settings menu. Not sure if that belongs there. It doesn't even fit entirely in the window (that you can't resize, duh). It however tries to connect to my default SMTP server (good) but it fails for some reason (probably some settings are not read correctly), because after a few minutes it comes back with "couldn't connect" or so. I'm not sure if hacking prefs.js is an appropriate fix for this issue, but thanks anyway for looking into it. Ehm, why don't you try these hacks on your box? ;-)
(In reply to comment #25) > It however tries to connect to my default SMTP server (good) mail.identity.id999.smtpServer is used while forwarding by filter when IMAP in your environment. This indicates that pseudo account of "Local Folders" is used. But why "Local Folders" when IMAP in your environment? > What you suggested here adds lots of strange stuff to LocalFolders->Server > Settings (including Port=-1 etc.) in the Account Settings menu. This is simply one of many very bad side effects of adding id999 to "Local Folders". And, because above three lines are incomplete identity definition, many unwanted error may occur. And, because mail-address specified in it is invalid one, server may reject it. Please remove them after test.
It is really strange. Even after I now removed the entries from prefs.js it still continues to work, for IMAP too. (Yes, I have done it right: Closed TB, edited the prefs.js file, then restarted TB)
(In reply to comment #27) > It is really strange. > Even after I now removed the entries from prefs.js it still continues to work, for IMAP too. > (Yes, I have done it right: Closed TB, edited the prefs.js file, then restarted TB) I think you did lot more while your problem determination process - at least viewing of account settings and saving of it. Some inconsistencies in definition in prefs.js is corrected/resolved by logic in "Account Settings" UI. And you apparently did check at least "Server Settings" of psuedo account of "Local Folders" and saved it. I can't imagine other reason, because you simply added id999 and removed it from prefs.js.
I think scenario is as follows. 1. m_rootFolder == "Inbox" of "Local Folders" 2. null is set in "server" when "Local Folders", because no identity exists for pseudo account of "Local Folders". m_rootFolder->GetServer(getter_AddRefs(server)); 3. because server==null, send error in next call for forwarding, and no SMTP server name in error message. ForwardMessage(forwardStr, m_msgToForwardOrReply, msgWindow, server); When "Local Folders" as Global Inbox owner account for other POP3 accounts, X-Account-Key: is already written because the mail has been downloaded. So, I think identity determination(then From: addr, SMTP, FCC folder etc.) thru X-Account-Key: is a solution for major cases when "Local Folders" as Global Inbox owner. I can't say nothing on next cases. - "Run filters on folder" on a mail folder of "Local Folders", and filtered mail is sent mail (no X-Account-Key:) - "Run filters on folder" on a mail folder of "Local Folders", and filtered mail is mail copied from IMAP account(no X-Account-Key:). http://lxr.mozilla.org/seamonkey/source/mailnews/local/src/nsParseMailbox.cpp#2071 > 2071 // this gets run in a second pass, after apply filters to a header. > 2072 nsresult nsParseNewMailState::ApplyForwardAndReplyFilter(nsIMsgWindow *msgWindow) > 2073 { >(snip) > 2078 for (i = 0; i < m_forwardTo.Count(); i++) > 2079 { > 2080 if (!m_forwardTo[i]->IsEmpty()) > 2081 { >(snip) > 2084 rv = m_rootFolder->GetServer(getter_AddRefs(server)); >(snip) > 2086 { >(snip) > 2088 if (compService) > 2089 rv = compService->ForwardMessage(forwardStr, m_msgToForwardOrReply, msgWindow, server); > 2090 } > 2091 } > 2092 } >(snip) Similar logic for replyTemplate follows
Summary: Mail Filter Forward To: produces a 'Send of Mail failed' Alert → Mail Filter Forward To: produces a 'Send of Mail failed' Alert (when Filters for "Local Folders")
I can confirm this bug for TB 2.0.0.6 (German version). I had a filter with automatic forward running fine with my TB 1.5. Only when I upgraded to 2.0.0.6 the same filter started to deliver error messages (German equivalent to 'Send of Mail failed') instead of forwarding the mail. The filter log however noted no error. The entries there looked like the forward was successful ('forwarded'), which in fact it wasn't. Deleting the filter and creating a new filter with the same rules did not help either.
I've encountered this bug too, as have several other people. See my post at http://forums.mozillazine.org/viewtopic.php?p=3065287#3065287 and this thread from a Mac user: http://forums.mozillazine.org/viewtopic.php?t=583142&start=0&postdays=0&postorder=asc&highlight=
I could solve the problem adding the following line to prefs.js: user_pref("mail.account.account1.identities", "id1"); where id1 is the already existent id being used for my actual account. IOW, I simply copied and slightly modified the following existent line: user_pref("mail.account.account2.identities", "id1"); This fix is basically WADA's original suggestion (comments # 20, 23), slightly improved taking in consideration WADA's own comment # 26: "because above three lines are incomplete identity definition, many unwanted error may occur." It seems if you provide a well-formed id (i.e., created using the GUI), then it works fine. Kudos to WADA.
(In reply to comment #33) > I could solve the problem adding the following line to prefs.js: > user_pref("mail.account.account1.identities", "id1"); > where id1 is the already existent id being used for my actual account. > I simply copied and slightly modified the following existent line: > user_pref("mail.account.account2.identities", "id1"); Please don't corrupt prefs.js manually. account1 is usually account definition of "Local Folders" which is automatically (and internally) created on first account definition. And account2 is an account you defined first. By your change, both account1("Local Folders") and account2(usual account) points same identity definitions which is identified by name of id1(=all of mail.identity.id1.xxxx entries). Your change affects UI of "Account Settings" also. See Account Setting of "Local Folders". Corruption of mail.identity.id1.xxxx entries may occur, and much worse problem may occur due to double booking of "id1". Please note that my manual change of prefs.js is problem determination purpose only and it never be my suggestion. Removed added "user_pref("mail.account.account1.identities", "id1");" Currently available workaround : (A) When "Global Inbox": (A-1) Define filter rule of action=forward in message filter for each account, instead of "Local Folders" (A-2) "Inbox for different account", instead of "Global Inbox(Local Folders Account)" (B) When "Run Filter On" on mail folder of "Local Folders" Don't use action=forward on mail folder of "Local Folders" (A-2) is similar action to your mail.account.account1.identities=id1, but (A-2) will never produce double booking of id1. - No mail.account.account1.identities=idX (for "Local Folders") - Proper account identified as accountN Proper mail.account.accountN.identities=idX Proper mail.identity.idX.xxxx entries (no double booking)
Needless to say, (A-2) will not corrupt UI for pseudo account of "Local Folders", because "no mail.account1.identities" status is kept. Felipe G. Nievinski, I recommend you to remove mail.account.account1.identities line from your prefs.js ASAP.
I tried both workarounds (A-1) and (A-2) proposed by WADA under comment # 34: (A-2) works fine; (A-1), unless I'm misunderstanding it, does not solve the problem -- see details below. (A-2): - I've created a brand new profile. - During the New Account Setup, I've _unchecked_ the option "Use Global Inbox". - Finally, I've created a filter with the "Forward to" rule, *for the user-defined account*, not "Local Folders". - Upon running the filter I get no error message; furthermore, the forwarded message shows up in the Sent folder. (A-1): - I've created a brand new profile. - During the New Account Setup, I did leave the option "Use Global Inbox" _checked_. - Finally, I've created a filter with the "Forward to" rule, *for the user-defined account*, not "Local Folders". - Upon running the filter I still get the same "Sending of message failed" error message. In both cases, I've setup up the SMTP server and verified it was working fine, sending a message manually. Workaround (B) does not apply to the original bug, i.e., to avoid using the "Forward to" rule is not a workaround for somebody who wants to use that feature. Please correct me if I'm misunderstanding something.
(In reply to comment #36) Thanks for testing of workarounds. > (A-1): >(snip) > I've created a filter with the "Forward to" rule, *for the user-defined account*, not "Local Folders". > Upon running the filter I still get the same "Sending of message failed" error message. It seems that filtering is executed under Global Inbox Account("Local Folders" in your test) even when message filter is defined for account. Probably my misunderstanding. Can you execute additional test? 1. Define next rule in filter for an account (hidden one. not "Local Folders") Rule-1: If (a condition), Add Tag-1, then forward 2. Define next rule in filter for "Local Folders" (same condition as Rule-1) Rule-2: If (a condition), Add Tag-2, then forward Will Tag-2 be added? Will error message appear twice? What will be written in message filter log? For (B): Workaround of (B) implies; Do "Run Filters On" at other account than "Local Folders", if required. i.e. Copy or move mail to mail folder of usual account(or dummy POP3 account), then execute filter of action=forward at the non-"Local Folders" account, if manual run of action=forward is required. Workaround of (A-2) automatically does do this workaround of (B).
Workaround (A-1) is based on description of 1) in Comment #6 on 2005-10-28(2 yeas ago). Behavior of Thunderbird 2.0.0.x may be different from it.
I tested additional test case in my comment #37 with Thunderbird trunk 2007/10/05 build. (Account setting) account2 : POP3 Server Setting/Advanced : "Global Inbox(Local Folders Account)" SMTP server of main identity : bbb.bbb.bbb (dummy SMTP server) account1 : "Local Folders". No identity is defined for "Local Folders" Default SMTP server : aaa.aaa.aaa (dummy SMTP server) (Message Filter) 1. Define next rule in filter for account2 (hidden one. not "Local Folders") Rule-1: If (a condition), Add Tag-1, then forward 2. Define next rule in filter for "Local Folders" (same condition as Rule-1) Rule-2: If (a condition), Add Tag-2, then forward (Test result) (1) Both Tag-1 and Tag-2 were added. (2) Error message which refers to SMTP server of "bbb.bbb.bbb" appeared twice. When trunk, identity selection when forward by filter seems to have been already changed to "identity selection based on X-Mozilla-Account-Key:". (X-Mozilla-Account-Key: points account who downloaded the mail)
Thanks for the new test, WADA. So, proposed workaround (A-1) really doesn't work, either with "Local folder" or actual account, right? So this bug was narrowed down to the case in which the profile has a Global Inbox, right? I.e., workaround (A-2) demonstrated that in the case of no Global Inbox the filter works fine as long as it's defined for an account other than Local Folder. I know that what I'm going to say is not very detailed, but I had that filter with the "forward to" rule working fine in a profile with Global Inbox before. Then at some point it stopped working.
(In reply to comment #40) > So, proposed workaround (A-1) really doesn't work, either with "Local folder" > or actual account, right? I don't think so, and I still think that 1) in Comment #6 is applicable to Tb 2.0.0.x, although I think that I'm not understand Tb 2.0.0.x behavior properly. > So this bug was narrowed down to the case in which the profile has a Global > Inbox, right? I.e., workaround (A-2) demonstrated that in the case of no Global > Inbox the filter works fine as long as it's defined for an account other than > Local Folder. You are almost right, but partially wrong. (A-2) demonstrate that action=forward works well even when Global Inbox, as far as "Local Folders" is not used. Cause of problem is that; (a) "Local Folders" doesn't have identity, (b) And, Tb 2.0 or before doesn't care about fact that "Local Folders" doesn't have identity, (c) And, Global Inbox owner is defaulted to "Local Folders", then many users use "Local Folders" as Global Inbox owner. If any of above three conditions is not satisfied, no problem will occur. - Your "adding of mail.account1.identities=id1" made condition (a) false. - Trunk nightly seems to have resolved problem of (b). - Workaround (A-2) makes condition of (c) false. > I know that what I'm going to say is not very detailed, but I had that filter > with the "forward to" rule working fine in a profile with Global Inbox before. > Then at some point it stopped working. No. It didn't start at some point. It existed since initial, because pseudo account of "Local Folders" and "Local Folders as account of Global Inbox" existed before start of "Forward by message filter" support.
Thanks for directing me to comment # 6 -- it's very useful. So, re-stating what's known: - to test the filter you must get new mail from your server; that's the only way to run the filters for all accounts, both actual and the "Local Folders" pseudo-account. If you try to manually run the filter defined for an actual account you'll either get a "Sending of messsage failed", if ran from the Message Filters window, or no message at all, if ran from the Tools menu. - to stay on the safe side, never define a filter for the "Local Folder" pseudo-account, no matter whether you're using Global Inbox or not. That's because sometimes it works, sometimes it doesn't -- today I've experienced both cases (sorry, I couldn't replicate it to pinpoint the exact conditions that produce them). Damian Glenny reports the same inconsistency under point # 3 in his comment # 6. Would you agree with that?
After reading the recent comments I changed the apllication of the filter from "Local Folder" to a "real" account. It seemed to work Magic - the filter worked! But only for that very day. The next day I was back to square one and got the same old error messages.
(In reply to comment #43) > The next day I was back to square one and got the same old error messages. To Daniel AJ Sokolov: Did you disable all filter rules which has action=forward in message filter for pseudo account of "Local Folders"? (or move such filter rules from message filter for "Local Folders" to message filter for real=hidden account)
Yes, I disabled all filter rules in my "Local Folders" - it's just one rule.
(In reply to comment #43) To Daniel AJ Sokolov: When you encountered the problem even after you moved action=forward to real account(=hidden one), what smtp sever name is mentioned in error message? What kind of error? Connection error? Or such as "5.7.1 relaying denied"? When action=forward is defined for "Local Folders", Tb can't find SMTP server because "Local Folders" doesn't have related identity(then no pointer to SMTP server), so error message can't point any SMTP server. But when real account, at least one identity is defined, and if error is a kind of connection error, SMTP server name is usually mentioned in error message. Is SMTP server setting of all identities of all accounts set appropriately?
To Daniel AJ Sokolov: Do you enable quarantine option? > Tools/Options/Anti Virus/Allow Anti-Virus clients quarantine individual incoming messages"
(In reply to comment #46) > (In reply to comment #43) > To Daniel AJ Sokolov: > When you encountered the problem even after you moved action=forward to real > account(=hidden one), what smtp sever name is mentioned in error message? > What kind of error? Connection error? Or such as "5.7.1 relaying denied"? No. There is no SMTP mentioned in the error messages. There is also no relaying denied or anything - there is a popup message (alert box) that says "Sending of message failed." (In my case in German, but it has the same meaning.) This messag pops up for very single mail that should be forwarded. > When action=forward is defined for "Local Folders", Tb can't find SMTP server > because "Local Folders" doesn't have related identity(then no pointer to SMTP > server), so error message can't point any SMTP server. This can't be true, because it worked fine with a filter defined for "Local Folders" in TB 1.5 and in rare cases it even works for TB 2.0. In 98% of cases it does not work, but sometimes, suddenly, the filter was applied correctly and the messages were being forwarded. Yes, with the filter set in "Local Folders". It's just that I can reproduce it on demand. >But when real account, > at least one identity is defined, and if error is a kind of connection error, > SMTP server name is usually mentioned in error message. > Is SMTP server setting of all identities of all accounts set appropriately? Yes, the SMTP server is set correctly for all identities.
(In reply to comment #47) > To Daniel AJ Sokolov: Do you enable quarantine option? > > Tools/Options/Anti Virus/Allow Anti-Virus clients quarantine individual incoming messages" Not until know. I have now turned it on, but it didn't change anything. The error is the same.
The bug could be caused by the Enigmail-extension. A user with the same problem and I have both removed the Enigmail-extension from our Thunderbird and now the AutoFWD works just fine! What about the others? Do you have the Enigmail-extension installed as well?
Yes I have Enigmail installed.
Nope, I don't have Enigmail. The bug occurs without any plug-ins installed.
Yes, I had Enigmail installed. I removed it and now it works great.
Nope, I don't have Enigmail.
I have the same problem here. Running Thunderbird 2.0.0.9, and Vista. No add ons, except for talkback. Please advice when this bug is fixed. For now I will have no choice but to go back to Pegasus, since I need to forward lots of incoming email using filters.
Assignee: bienvenu → nobody
Component: General → MailNews: Filters
Product: Thunderbird → Core
QA Contact: general → filters
Version: Trunk → unspecified
Turns out there are differences in the behavior for rules on IMAP and RSS accounts. The following rule (from msgFilterRules.dat) fails when used on a password-protected RSS feed, but works when applied to an IMAP account: name="Stuff given away" enabled="yes" type="1" action="Forward" actionValue="jdoe@example.com" condition="AND (subject,contains,give away)" Note: - Tested with 2.0.0.12 on Windows XP. - The test was performed on the same message, that is, I copied the message from the RSS channel to the IMAP inbox and ran the filter in both. - Changed the email address, but I did receive the email from the IMAP folder at the target address when testing.
(In reply to comment #56) > Turns out there are differences in the behavior for rules on IMAP and RSS accounts. Thanks for advanced test/check for RSS/IMAP cases. RSS case is perhaps similar to "Local Folders" case because no corresponding identities when RSS too. (perhaps no problem when IMAP because IMAP has identities) But this bug is for problem when pseudo account of "Local Folders" only. Victor Engmark, please open separate bug for RSS case (and for IMAP case if problem exists too), in order to avoid confusion, and for ease of problem analysis, with xref-ing to this bug, please.
(In reply to comment #57) > Victor Engmark, please open separate bug for RSS case (and for IMAP case if > problem exists too), in order to avoid confusion, and for ease of problem > analysis, with xref-ing to this bug, please. Filed bug 426507 for the RSS case. No problem found with IMAP.
This bug exhibits itself in Thunderbird 2.0.0.12 with Enigmail installed (either enabled or disabled) on an up-to-date Fedora 8 system. I have two Thunderbird accounts defined: "Home Account" and "Local Folders." The filter that attempts to forward messages--as well as all other filters--is only defined for "Home Account." There are no filters defined in "Local Folders." There is one SMTP server defined for "Home Account" that works in all non-filter circumstances.
I confirm this bug for TB 2.0.0.14, WindowsXP, no AddOns active.
I noticed this problem with TB 2.0.0.14 on Mac OSX (Tiger). I had a rule to match a "To or cc", with a single action to forward the message to another email address. I only have one account, and have not used nor touched the Local Folders since I installed TB first. I read the comments about Enigmail, and so I disabled the extension. After restarting TB, the filter worked fine via Tools>>Run Filters on Folder with the Inbox of my account selected (not the Local Folders because I do not use them). I have the latest version of Enigmail installed (0.95.6). I have a feeling this is a compatibility issue between Enigmail and TB.
(In reply to Comment #50, comment #59, and comment #61) To Daniel AJ Sokolov, Andrew Piziali and Andres Valloud: Thanks for making "Non Local Folders" case clear. As bug summary and many former comments, comments for test result, comments of "filter in non Local Folders was workaround", say, this bug is for problem when "Local Folders" where no problem with "Non Local Folderes". "Problem even with non Local Folder when Enigmail is used" is different problem from this bug, even if similar issue is involved in it. Please open separate bug for ease of analyzing of problem, tracking of problem, and solving of problem.
I just tried setting up a forwarding filter (to my txt message email address) and immediately ran into this bug. I've read through the comments here but don't fully understand them since I'm not a software guy. It looks like after about three years, no one has identified the root cause of the bug, much less fixed it. It isn't even assigned to anyone, which is not encouraging. Is this bug in the TB 3 alpha releases? If so, will it be fixed there? Thanks!
(In reply to comment #63) > > Is this bug in the TB 3 alpha releases? If so, will it be fixed there? > > Thanks! > This bug is not in the alpha release. To encourage attention to it, vote for it and nominate it for blocking-thunderbird3
I'm still experiencing this bug in 2.0.0.16, on XP sp3. Occurs on Local Folders filter and on specific account filter. No errors are generated in the Filter Log.
Product: Core → MailNews Core
Happens for me too on 2.0.0.16, not only on local folders but on folder on any account, with Enigmail installed. Disabling Enigmail solves this issue for me.
Also happens in 2.0.0.19 (20081227) with the Inbox of one of my POP accounts, on openSUSE 11.1. Thunderbird came with Enigmail version 0.95.7 (20090108) installed.
To some extent, I think Enigmail is not necessarily related to this problem. I think the real issue is the burst of message sends to the SMTP server. I made the observations below because at times I use Thunderbird on my laptop to download email while I am not at home. When I come back, I copy the email folders to my main computer's Thunderbird profile (with Thunderbird shut down). Then I restart Thunderbird, it picks up the folders, and so I can move all the email I downloaded in the laptop to the inbox. After cleaning up the folder I copied from the laptop, I just run the filters in the inbox. Case 1. Numerous emails to be forwarded in the inbox. The first few are sent (as per the Sent folder). Eventually however a send fails. I think this is the SMTP server complaining about either too many concurrent connections, or too many emails sent in too short a period of time. In other words, the usual SMTP server has a send burst limit, and running the filters like that blows past it. As such, sends fail. Case 2. Fewer emails to be forwarded in the inbox. Then it works, most likely because the SMTP server's burst limit is not exceeded. Case 3. Getting new emails every few minutes. Then it works, most likely because getting new email every few minutes hardly ever produces enough emails to be forwarded sitting in the inbox at once to trip the SMTP server send burst protection. From this, what I would suggest is that the forwarding filter puts an email to be sent out in the Outbox, rather than sending it immediately. Then, all forwarded emails will be sent out in an orderly fashion when email gets sent.
(In reply to comment #66) > Happens for me too on 2.0.0.16, not only on local folders but on folder on any > account, with Enigmail installed. Disabling Enigmail solves this issue for me. (In reply to comment #67) > Also happens in 2.0.0.19 (20081227) with the Inbox of one of my POP accounts, > on openSUSE 11.1. Thunderbird came with Enigmail version 0.95.7 (20090108) > installed. Enigmail & filter of non-"Local Folders" case is different from original problem of Comment #0 (problem in different condition, even though same symptom). Read bug summary, and read Comment #50, comment #59, comment #61, and comment #62, please. If problem with Enigmail can be reproduced easily, open separate bug with sufficient data such as NSPR log, after bugzilla search for already opened bug, please (I don't know someone opened bug for it or not).
happens to me with thunderbird 2.0.0.21 on linux, no add-ons i propose to remove the feature from thunderbird if it's not working because it took me half an hour to try the feature, become desperate, search in bugzilla and realize it's a four year old bug in a very basic feature! removing the forward-option would be a lot easier and stops thounsands of people to get annoyed by thunderbird.
I don't use Enigmail. This inability of forwarding with a filter is frustrating. I moved to TBird after Eudora 7 became unsupported. I'm tempted to move back!
Flags: blocking-thunderbird3?
To all "still occurs" or "me too" reporters for Tb 2.0.0.xx: As I wrote in Comment #39, and as written in Comment #64, this bug's problem on "Local Folders" doesn't seem to occur on Tb trunk(next Tb 3). Please check with latest trunk nightly build(currently pre Tb3.0b4) which can be obtained at site pointed by Comment #72, before add comment of "still occurs".
I'm seeing no confirmation that this is still an issue in the TB 3 builds. Therefore adding qawanted to try and get some feedback on that. We're not going to block Thunderbird 3 on this as essentially it is unconfirmed there (much has changed since TB 2), and there is a reasonably easy work around. We will however reconsider for the next release after Thunderbird 3 or if someone can confirm it still exists.
Flags: blocking-thunderbird3?
Flags: blocking-thunderbird3.1?
Flags: blocking-thunderbird3-
Keywords: qawanted
I am building the latest Thunderbird 3 on my Fedora 8 system and will report results of attempting to reproduce this bug.
I was unable to reproduce this failure in TB 3.0pre, running on a Fedora 8 system. This is a log of my attempt to reproduce the problem: * Built using instructions from https://developer.mozilla.org/en/Simple_Thunderbird_build: # Get the source hg clone http://hg.mozilla.org/comm-central/ cd comm-central python client.py checkout # Setup a basic .mozconfig file echo 'ac_add_options --enable-application=mail' > .mozconfig echo 'mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/objdir-tb-release' >> .mozconfig echo 'mk_add_options MOZ_MAKE_FLAGS="-j4"' >> .mozconfig # Build make -f client.mk * version 3.0pre * Enigmail and Lookout plugins not loaded * Indexing all folders (!) o Took a LONG TIME (>6 hours) * Change filter "Texans CU" from: [From] [contains] [texanscu.org] to [Subject] [contains] [texanscu.org] in order to test these actions: [Forward Message to] [email address] [+] [-] [Move Message to ] [Texans CU on Local Folders] [+] [-] * Mailed message with the subject line "texanscu.org (1)" from andy@piziali.dv.org to andy@piziali.dv.org. * Pressed [Get New Messages] button * Message was stored in "Texans CU" local folder and forwarded to <email address without error.
Not blocking - no one has reported this as still being broken in 3.0, so I'd close this as incomplete/wfm if no one reports an issue with 3.0
blocking-thunderbird3.1: --- → -
Flags: blocking-thunderbird3.1?
I could not reproduce the problem in Thunderbird 3.x either.
I am using Thunderbird 3.0.1. I still have the problem ***IF*** I have Enigmail installed and enabled. If I disable Enigmail, the problem goes away. If I reenable Enigmail, it comes back. My workaround is to leave Enigmail disabled most of the time. If I need to encrypt or decrypt an email, I enable Enigmail, deal with the email, and then disable it. I'd love to see it fixed, but it's not a showstopper for me.
Tim what version of enigmail you use? (see menu-->openpg-->about openpg)
I am using Enigmail 1.0.1
(In reply to comment #79) > I am using Thunderbird 3.0.1. I still have the problem > ***IF*** I have Enigmail installed and enabled. (In reply to comment #82) > I am using Enigmail 1.0.1 Tim Jacob, please read thru this bug well and understand at least Comment #69(and comments pointed in it) and Comment #81 well, before posting additional enigmail related comments. Should we put "never add enigmail related comments any more" in bug summary and/or whiteboard of this bug?
this seems to be WFM, then, if the issue is in Enigmail. Thx for the response. If it turns out to be that Enigmail is exposing an issue in TB, then we can re-open.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Summary: Mail Filter Forward To: produces a 'Send of Mail failed' Alert (when Filters for "Local Folders") → Mail Filter Forward To: produces a 'Send of Mail failed' Alert (when Filters for "Local Folders". No Enigmail)
Whiteboard: Open separate bug if Enigmail is used, please.
I have the problem currently in 3.1.4. I think it started in 3.1. The filter has worked for many years prior to that. My filter forwards certain messages to several email addresses. When it's run manually its fine. When it's run automatically it trashes attachments.
It works fine in 31.1.0 release!
You need to log in before you can comment on or make changes to this bug.