Related bug #40357 and bug 40358 If a user specifies an invalid MoveToFolder message filter destination, when the filter fires that message is lost instead of being retained in the Inbox. (This bug similar to bug #45693 where destination is unauthenticated.) Previously, I assumed we would take invalid destinations from the MoveToFolder destination folder dropdown, but the bugs calling for removal of News and Account Level destinations from the dropdown were moved to a future release. So I'm logging the results of using thes items if they're left in the choice list. (Will we be able to move to AOL or Netcenter folders?) Steps to reproduce: 1. Go to mail window in profile with an IMAP account and a news/nntp account with a subscribed newsgroup. 2. Edit|Message Filters. Select the IMAP acount in the filter ui dropdown and set up a simple message filter which will use the action of MoveToFolder and select the newsgroup as the destination of the move. Confirm OK out of filters ui. 3. Send a message to the first account which will meet the filter criteria. 4. Get messages for the mail account. 5. Check the mail account's inbox for the filtered message. It is not there. 6. Select the newsgroup specified as the (invalid) destination folder and notice the filtered message is not there either (didn't expect it to be). 7. Check the mail Inbox again. Message is not there. 8. Exit and relaunch, get mail messages, check inbox again. Message is not there, it is lost. Result: Message is lost if an invalid destination is specified for MoveToFolder. Expected: Message should remain in the mail account inbox if it cannot be successfully moved to the destination account.

nothing to do with filters - plain ol user move/copy has this problem too.

I guess I'll fix this one too.

this should be fixed - I fixed the move case.

for the record, marking nsbeta3+

Using aug15 commercial m18 build, linux rh6.0, mac OS 9.0: Message is still lost -- never appears in INBOX.

No, the message is not lost at all. It's in your inbox. But you will never see this until you get rid of your bogus filter, or run with a different client without the bogus filter, because everytime you get new mail, your bogus filter runs and tricks us into trying to move to a newsgroup, which will fail. Also, you should not be allowed to setup a filter that moves a mail message to a newsgroup! (that would be a bug for Alec).

For all practical purposes to a 6.0 user, it appears lost. I know I can retrieve the message in 4.x. There is already a bug(s) logged against alec for invalid destinations being able to be selected, but the freakin' powers that be have decided to future it! Ref bug #40343 and bug #40357 and bug #40358. (And of course, there's the one about invalid destination as a result of renaming or deleting a folder.)

I have a fix for the case of non-existant imap folders or attempts to filter to a newsgroup or server.

fix checked in to disable filters to folders that can file messages (e.g., newsgroups and servers) and to folders that don't exist.

OK using sep08 commercial build with linux rh6.0 and NT 4.0. Waiting for today's mac build.

OK using 2000-09-08-20 m18 commercial build mac OS 9.0. In some instances I saw an error "mailbox does not exist" when the filter fired the first time, but mail message always appeared in inbox and filter was disabled.