Re: Multidrop retrievers: run filter before sorting ?
Charles Cazabon <[email protected]> Mon, 16 Aug 2021 13:07:01 -0600
| Newsgroups | gmane.mail.getmail.user |
|---|---|
| Message-ID | <[email protected]> |
Bigaunti - Arcor <[email protected]> wrote: > > What the filter is doing: [...] > - searches in the remaining header for occurances of the sequence " > for<[email protected]> " Hrm - you're looking for "for <email-address>", not just the email address itself? Are you looking this in Received: headers or something else? It sounds like you're basically guessing at who the envelope recipient address might have been. It's not ideal, but getmail has the MultiGuesser destination class for this. It will look at the recipient info header fields (outlined in doc) until it finds a match, else it will fall back to a default recipient config. I think you should be using that. > > This is a huge red flag. > > Indeed I worded it clumsy Not quite what I meant. I mean you seem to be doing your fake-a-recipient-header bit to cause getmail to set %(recipient) when invoking MultiSorter, which is deliberately disabling a critical "safety circuit" in getmail. %(recipient) is deliberately not set in this case; MultiSorter is intended only to be used with a domain mailbox, which you no longer have. You haven't provided your getmailrc file or your header-munging script, so I can't be precise in how you might shoot yourself in the foot trying to do that. Your proposed solution is potentially dangerous, so I'm not interested in changing getmail to support it. Charles -- ----------------------------------------------------------------------- Charles Cazabon GPL'ed software available at: http://pyropus.ca/software/ -----------------------------------------------------------------------