6.0.0-alpha14
7/3/25

[#8391] ingo generates dev/null address exclusion
Summary ingo generates dev/null address exclusion
Queue Ingo
Queue Version 1.2.1
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester johannes.grimm (at) fh-rosenheim (dot) de
Created 06/30/2009 (5847 days ago)
Due
Updated 07/01/2009 (5846 days ago)
Assigned
Resolved 06/30/2009 (5847 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
07/01/2009 08:44:10 AM johannes (dot) grimm (at) fh-rosenheim (dot) de Comment #3 Reply to this comment
i have tested a bit on the webmail interface, and i conclude the most 
likely case is an user fault. the blacklist option between undelete 
and forward could get pressed accidentally. -close-
Those users are not creating them by themselves.
This statement seems highly doubtful.  /dev/null is the action for
the discard rule.  This generated script indicates that the user
wanted all mail from that address to be discarded, a very common
filter request.
06/30/2009 05:10:46 PM Michael Slusarz Comment #2
State ⇒ Not A Bug
Priority ⇒ 1. Low
Reply to this comment
Those users are not creating them by themselves.
This statement seems highly doubtful.  /dev/null is the action for the 
discard rule.  This generated script indicates that the user wanted 
all mail from that address to be discarded, a very common filter 
request.
06/30/2009 02:54:10 PM johannes (dot) grimm (at) fh-rosenheim (dot) de Comment #1
Priority ⇒ 3. High
Patch ⇒ No
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ ingo generates dev/null address exclusion
Type ⇒ Bug
State ⇒ Unconfirmed
Reply to this comment
Ingo is creating filters like this and i don“t know why??



# Von Ingo erzeugtes procmail Script (April 15, 2009, 9:56 pm)

##### Ausgeschlossene Adressen #####

:0

* ^From:(.*\<)?obermaier\.h@fh-rosenheim\.de

/dev/null



From time to time users complain about missing mails and the reason 
is always this!

Those users are not creating them by themselves.

Saved Queries