| Summary | infinite mail loop with forward rule |
| Queue | Ingo |
| Queue Version | 1.0.1 |
| Type | Bug |
| State | Resolved |
| Priority | 2. Medium |
| Owners | |
| Requester | alex (at) segv (dot) de |
| Created | 04/11/2007 (6696 days ago) |
| Due | |
| Updated | 04/11/2007 (6696 days ago) |
| Assigned | |
| Resolved | 04/11/2007 (6696 days ago) |
| Github Issue Link | |
| Github Pull Request | |
| Milestone | |
| Patch | No |
Sorry for opening this bug report.
Priority ⇒ 2. Medium
New Attachment: procmail_forward.patch
Queue ⇒ Ingo
Summary ⇒ infinite mail loop with forward rule
Type ⇒ Bug
State ⇒ Unconfirmed
- Destination email is invalid, e.g. alex@segv.de; (Note the
semicolon after the email address!)
- exim generates a bounce ("alex@segv.de; malformed address: ; may
not follow alex@segv.de")
- this bounce is forwarded and bounces again. => infinite mail loop,
server goes down with out of memory after a few thousend bounces.
Possible fix: add "* !^FROM_DAEMON" to forward rule to exclude all
bounces, but that defeats the point of forwarding somewhat, if
possible important mails don't get through :/
Another idea: prevent user from entering syntactically invalid email
addresses. (What about undeliverable addresses?)
The attached patch implements the first idea.