Re: Email Bouncebacks - Backscattering
- To: mutt-users@xxxxxxxx
- Subject: Re: Email Bouncebacks - Backscattering
- From: Kyle Wheeler <kyle-mutt@xxxxxxxxxxxxxx>
- Date: Mon, 5 May 2008 12:51:15 -0500
- Comment: DomainKeys? See http://domainkeys.sourceforge.net/
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=memoryhole.net; h=date :from:to:subject:message-id:references:mime-version:content-type :in-reply-to; s=default; bh=6RITjjkof6kAAi3wJGpn8pBXqGo=; b=DwOq kH3pdqS5N37+C8RXvL0/uaZNr50DD4rRecEkAH05g2jhHaW1rTejgzu8744nKcv/ XaJZQerC/q7Pz7hm51cKXD44buL6zdt1PaJeqFOJtKd1Ednh0tVPciEKvRgiU1II UES6Vqm41fF+WI8fN2zfEe9/Cdu6FbASOpt492k=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=memoryhole.net; b=NjqtLbLMCWNUA0lWGJ1k5fE1JcGdGT3zGoaJKAGm5NSMPAHvhSk3sQWrq2y4n0zRpC7fdQM3O4OhS64X/5Q5IitJbiynq40n8yDkqGtEe+d02Q/OONkW00wE75/48Y0wtMF0ONO9Gq8BrCQ5T1UIsIriKpwXN6UNQiQPCK66S1U=; h=Received:Received:Date:From:To:Subject:Message-ID:Mail-Followup-To:References:MIME-Version:Content-Type:Content-Disposition:In-Reply-To:OpenPGP:User-Agent;
- In-reply-to: <20080505160807.GB11746@xxxxxxxxxxxx>
- List-post: <mailto:mutt-users@mutt.org>
- List-unsubscribe: send mail to majordomo@mutt.org, body only "unsubscribe mutt-users"
- Mail-followup-to: mutt-users@xxxxxxxx
- Openpgp: id=CA8E235E; url=http://www.memoryhole.net/~kyle/kyle-pgp.asc; preference=signencrypt
- References: <20080505160807.GB11746@xxxxxxxxxxxx>
- Sender: owner-mutt-users@xxxxxxxx
- User-agent: Mutt/1.5.17 (2008-04-09)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday, May 5 at 10:08 AM, quoth Joseph:
> There is an article on slashdot on "email bounceback" Is the solution as
> simple as including custom header and filtering it with procmail?
Wouldn't that be nice?
Putting a custom header in all your outbound emails and watching for
it in bounces is nice BUT you cannot rely on valid bounces containing
all of the headers of the email they're bouncing. For example, "out of
office" emails often contain *nothing* of the original email. The same
is true of mailing list challenges (which will have a sender, so they
count as backscatter, but aren't technically bounces). DSN emails also
frequently don't contain full headers; they may just contain the
subject line of the message they're responding to.
Valid bounces can be relied upon to contain only one piece of
information from the email they are bouncing, and that one piece of
information is the envelope address you sent from.
Since that's the only piece of your original email that you can
*guarantee* will be in a valid bounce, that's the only piece of your
original email that you can monkey around with. A good way of
monkeying around with it is BATV, but that has its own problems that
need to be worked around (e.g. subscriber-only mailing lists typically
check the envelope sender against the list of subscribers).
~Kyle
- --
To believe in God is impossible---to not believe in him is absurd.
-- Voltaire
-----BEGIN PGP SIGNATURE-----
Comment: Thank you for using encryption!
iEYEARECAAYFAkgfSRMACgkQBkIOoMqOI14s8ACg4l7dogV3uMWLA43EpeApvtef
5XUAn3vBcgeV7EEHF+VN4MdUEV7m4mOh
=DZya
-----END PGP SIGNATURE-----