Open hhoffstaette opened 2 years ago
I'm just trying to understand this. At first, I thought it's a bug, but it seems more of a missing feature: you can't specify that some header HAS TO exist. The existing behaviour seems not faulty, right?
IIRC the point was that a missing Subject; also seems to affect (and disable) other headers that do exist, since they are no longer matched. It's as if a mising Subject: short-circuits everything. It's probably best to only focus on the first half of the original description; the second part was only an attempt at a workaround.
Ah ok, I see. I will investigate. :-)
I've noticed that mails with a deny-matching header (e.g. the popular
To: undisclosed-recipients:;
) but empty or missingSubject:
are not filtered and pass through. This seems like a bug. Unsurprisingly, attempts to work around this with a filter matching on Subject: have been unsuccessful, since it is not possible to match on nonexisting headers. Matching on an empty Subject - e.g. with^Subject: $
- does not seem to work either for the same reason.