https://bugzilla.novell.com/show_bug.cgi?id=342075 User chappa@washington.edu added comment https://bugzilla.novell.com/show_bug.cgi?id=342075#c11 Eduardo Chappa <chappa@washington.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |chappa@washington.edu --- Comment #11 from Eduardo Chappa <chappa@washington.edu> 2008-11-09 15:54:54 MST --- (In reply to comment #0 from Seth Chaiklin)
Perhaps this report is meaningless if 'alpine' is the way forward...
I have a filterrule that moves all incoming spam (identified by spamassassin) to a separate inbox. As part of that rule, I have an action to set the status to Delete. That rule has worked without problem for the past year with pine-4.64N-32 (openSuse 10.2).
The rule stopped working after I installed pine-4.64N-93 (openSuse 10.3) -- and started working again after 4.64N-32 was reinstalled.
Correlation is not causation -- but I am inclined to believe that the big patch integration from 21 Sep. has disturbed something.
One more observation. In the same filter rule, I was able to unset the N status, so this is further evidence that the rule can change status. But for some reason, it will not change status to Delete.
I have read this report and I still fail to see the bug. I need data to reproduce the problem. Here is what I understand from the report. * That a rule to move a message to another folder and set its status to deleted is not working. I understand that setting the delete status would be done in the target folder, not in the source folder (Pine sets the delete status in the source folder anyway). * I have tried a rule like this in a pine patched will all.patch and with no other patches and the rule works. That is, the message in the target folder is marked deleted. This is not to say that there is no problem in all.patch. I am just saying that there is not enough evidence to check that the problem exists in all.patch. For all I know the problem might be in another patch added by SuSe. In order to determine this, we need to make a few more tests and gather more information. * I need a copy of the .pinerc file that is read by pine when the problem is produced. This I need because at this moment it is possible that the problem be in all.patch but it is reproduced by settings that I do not have set. * If you are not willing to give me a copy of the .pinerc, I need to know if this problem is produced through IMAP, POP, etc. Server names are good, because I can try to test them. Settings are good because I can see how they get together to reproduce the problem. * If you are not going through IMAP, are you using maildir at all? I do remember that there was a change in all.patch between the versions that are mentioned here, but that change had to do with a change in the fillpara patch (see my web page for more details on what this patch does), and no code in all.patch had anything to do with filtering, so I find all of these problems very unlikely to have been caused by all.patch, but since we don't know, I am willing to investigate, and fix any problems in all.patch, if any. What I am saying here is that if the problem had existed in all.patch in version 10.2, it would have probably existed in 10.3. I would also try to see if there are other changed that were added by Bernhard other than mine. Another thing to look into is to see if the integration of patches was done properly. This is something that only Bernhard could have done. There may be a patch that was added incorrectly. Since I can not reproduce the problem at all, less at will, I am asking for real data that shows the problem. I would be really interested to see this to determine where the problem comes from. Thank you. -- Eduardo http://staff.washington.edu/chappa/pine/ -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.