| To: | qmail@list.cr.yp.to |
|---|---|
| Subject: | Re: Qmail and Bounce Message Spamming |
| From: | "Matthew R. Dempsky" <mrd@alkemio.org> |
| Date: | Sun, 1 Apr 2007 23:33:28 -0500 |
| Delivered-to: | sp-com-lists@consult.net |
| Delivered-to: | gmail-qmail@securepoint.com |
| Delivered-to: | sp.com.list@gmail.com |
| Delivered-to: | mailing list qmail@list.cr.yp.to |
| In-reply-to: | <461079A5.1080606@sdudley.com> |
| Mail-followup-to: | qmail@list.cr.yp.to |
| Mailing-list: | contact qmail-help@list.cr.yp.to; run by ezmlm |
| References: | <46106596.90105@sdudley.com> <20070402032112.GA7004@discworld.dyndns.org> <461079A5.1080606@sdudley.com> |
On Sun, Apr 01, 2007 at 08:33:57PM -0700, Scott Dudley wrote: > I'm troubled Charles because these messages are not bounced messages > originated from this qmail server. Instead, they originate elsewhere > with the deliberate attempt of exploiting this functionality to SPAM. I > found several posts describing this very issue yesterday. If receiving bounce messages concern you so much, add a blank line to /var/qmail/control/badmailfrom. However, realize that in doing so you're blocking legitimate bounce messages notifying you of message delivery failures. A more cynical suggestion would be to block incoming TCP connections on port 25 because there are deliberate attempts of exploiting that functionality for spam as well. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Qmail and Bounce Message Spamming, Scott Dudley |
|---|---|
| Next by Date: | Re: tai64n date format, Kyle Wheeler |
| Previous by Thread: | Re: Qmail and Bounce Message Spamming, Scott Dudley |
| Next by Thread: | Re: Qmail and Bounce Message Spamming, Charles Cazabon |
| Indexes: | [Date] [Thread] [Top] [All Lists] |