netstepinc
Verified User
Some of my clients are experiencing problems when receiving mail from
@verizon.net or @hotmail.com addresses.
I have one example where a friend of mine tried to send a message to one of my clients on the SpamBlocker protected server. The message was bounced back to her, then she tried to forward it to me and bounced again.
"forged verizon mail" is given as the reason, but it's not forged.
I noticed Yahoo is in the X-mailer line, but the sender is not
consciously using any sort of Yahoo product/system.
I need to prevent false positives like this.
Do you have any ideas?
NOTE: NAME, USERNAME, MY-IP and SB_server.com have been substituted for real email addresses and IPs to protect the innocent.
------------------------------ SECOND BOUNCE WHEN SENT TO ME---
72.3.MY.IP does not like recipient.
Remote host said: 550 Forged Verizon Mail, not sent from your account.
Giving up on 72.3.MY.IP.
------------------------------ REJECTION MESSAGE BELOW-----------
Return-Path: <[email protected]>
Received: (qmail 32205 invoked by uid 60001); 3 Oct 2007 00:35:03 -0000
X-YMail-OSG: ML1LT.MVM1nED3Y.zAesQGjY9nP2LwBcJrNHXEi2WfqjAedO
Received: from [71.121.149.199] by web84106.mail.mud.yahoo.com via HTTP; Tue, 02 Oct 2007 17:35:01 PDT
X-Mailer: YahooMailRC/651.50 YahooMailWebService/0.7.134
Date: Tue, 2 Oct 2007 17:35:01 -0700 (PDT)
From: NAME <[email protected]>
Subject: Problem with email
To: NAME <username@SB_server.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-477425170-1191371701=:31984"
Message-ID: <[email protected]>
--0-477425170-1191371701=:31984
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
@verizon.net or @hotmail.com addresses.
I have one example where a friend of mine tried to send a message to one of my clients on the SpamBlocker protected server. The message was bounced back to her, then she tried to forward it to me and bounced again.
"forged verizon mail" is given as the reason, but it's not forged.
I noticed Yahoo is in the X-mailer line, but the sender is not
consciously using any sort of Yahoo product/system.
I need to prevent false positives like this.
Do you have any ideas?
NOTE: NAME, USERNAME, MY-IP and SB_server.com have been substituted for real email addresses and IPs to protect the innocent.
------------------------------ SECOND BOUNCE WHEN SENT TO ME---
72.3.MY.IP does not like recipient.
Remote host said: 550 Forged Verizon Mail, not sent from your account.
Giving up on 72.3.MY.IP.
------------------------------ REJECTION MESSAGE BELOW-----------
Return-Path: <[email protected]>
Received: (qmail 32205 invoked by uid 60001); 3 Oct 2007 00:35:03 -0000
X-YMail-OSG: ML1LT.MVM1nED3Y.zAesQGjY9nP2LwBcJrNHXEi2WfqjAedO
Received: from [71.121.149.199] by web84106.mail.mud.yahoo.com via HTTP; Tue, 02 Oct 2007 17:35:01 PDT
X-Mailer: YahooMailRC/651.50 YahooMailWebService/0.7.134
Date: Tue, 2 Oct 2007 17:35:01 -0700 (PDT)
From: NAME <[email protected]>
Subject: Problem with email
To: NAME <username@SB_server.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-477425170-1191371701=:31984"
Message-ID: <[email protected]>
--0-477425170-1191371701=:31984
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
