mail forwarding loop :: SPAM

2 msg	Postfix SASL Help
6 msg	Slowing down postfix
2 msg	need help deciphering a line
4 msg	Postfix SMTP server: errors from something.net[...
4 msg	2.5.0-RC and 2.6 should recognize FreeBSD 8
9 msg	Postfix not following my access file.
3 msg	postfix logs delay, delays, dsn
3 msg	Best way to shutdown postfix prior to servicing...
1 msg	the bounce process hangs a mail (?)
3 msg	messages destined for content_filter stuck in d...
2 msg	Domain in username
5 msg	missing authentication on recipient
5 msg	postfixadmin
5 msg	check_policy_service before reject_rbl_client
9 msg	MXBackup via LDAP
5 msg	header and body check exemptions
5 msg	Relay recipient maps and relocated users

mail forwarding loop :: SPAM
\ Scott Ruckh (21 Jan 2008)
. \ Justin Piszcz (21 Jan 2008)
. \ (Wietse Venema) (21 Jan 2008)
. . \ Scott Ruckh (21 Jan 2008)

3 msg	transport_maps how to match mx's
2 msg	Where/when to insert a missing Message-ID

Subject:	mail forwarding loop :: SPAM
Group:	Postfix-users
From:	Scott Ruckh
Date:	21 Jan 2008

I searched the archives for mail forwarding loops and come across quite a
few articles discussing .forward files, and other messages talking about
Delivered-To: field being changed in envelope header, but I was not sure
if I have the same issue and if there was a solution.

So I have some clown sending email from 87.88.14.31. The From: field
contains an invalid email address from my domain. The Delivered-To: field
contains my address.

I end up with a "mail forwarding loop for <my email address>" email from
MAILER-DAEMON.

As email accounts are separate from system machine accounts this is not an
issue with a .forward file. This sounds like an issue with then
Delivered-To: field being injected with bad info.

I did not find a resolution to this issue. What can I do to block these
types of emails?

Thanks.