| Summary | Manually bounce back message |
| Queue | IMP |
| Queue Version | Git master |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | viktor (at) szepe (dot) net |
| Created | 10/8/15 (3827 days ago) |
| Due | |
| Updated | 1/13/16 (3730 days ago) |
| Assigned | |
| Resolved | 1/13/16 (3730 days ago) |
| Milestone | |
| Patch | No |
spamming yourself.
Only if you determine that a message is spam during delivery, it makes
sense to reject a message (so that senders of false positives get
notified), other than that you have nothing to gain by bouncing a
message and effectively you become part of the problem as a spam
reflector (which will attract more spam, rather than lower it).
See http://www.dontbouncespam.org/#BVR
State ⇒ New
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Manually bounce back message
Queue ⇒ IMP
Milestone ⇒
Patch ⇒ No
optionally - could be bounces back as there was no such address on the
server.
Thank you for your consideration.