Re: IDLE, read_all, and not delete - bad combination, skipping
Charles Cazabon <[email protected]> Thu, 5 Nov 2020 15:09:41 -0600
| Newsgroups | gmane.mail.getmail.user |
|---|---|
| Message-ID | <[email protected]> |
Langenxx Feld <[email protected]> wrote: > Hallo Charles: Just send to the list in future, please. Your MUA appears to be ignoring the Mail-Followup-To: header; I don't need extra copies of list messages. > Another thing I wanted to ask before leaving this mail business in despair > is: > > IDLE, read_all, and not delete - bad combination, skipping > > I know that you are not using IDLE, but it is a nice thing nevertheless, and > I would like to keep it, so I thought it is worth asking at least once. > > I was being careful and testing with "delete_after = 14", instead of "delete > = true". > > Are those 2 options not more or less equivalent, at least as far as IDLE is > concerned? At least in a way, so that this restriction could be lifted if > delete_after is given. I think you're over-thinking this. The solution to your problem is to unset read_all; you can use that with delete_after all you want and not get the above error message. Charles -- ----------------------------------------------------------------------- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ -----------------------------------------------------------------------