I created three new distro groups that are used both internally, and by external vendors. I created them like I have others in the past, only this time, I get complaints from vendors that they are getting NDA messages when they attempt to send messages to them. The distribution groups have been used without issue internally.
I double checked the configuration, and it looks pretty straight forward.
Mail flow settings
Message Size Restrictions: not configured
Message Delivery Restrictions:
Accept messages from = All Senders
Require that all senders are authenticated = not checked
Reject messages from = No senders
Message Moderation: not configured
All three are Mail Universal Distribution Groups, and they simply have individual users as members
There is a spam filter that is suspect but I have no control over it. So I need to make sure it isn't something I configured wrong, so I can confidently bug them to fix it.
When a vendor sends to any of the groups, they get the following error message:
A problem occurred during the delivery of this message to this e-mail address. Try sending this message again. If the problem continues, please contact your helpdesk.
The following organization rejected your message: server-4.tower-95.messagelabs.com.
Diagnostic information for administrators:
Generating server: bigfish.com
Distro1@Domain.com
server-4.tower-95.messagelabs.com #<server-4.tower-95.messagelabs.com #5.0.0 smtp;550 Invalid recipient <Distro1@Domain.com >
(#5.1.1)> #SMTP#
Original message headers:
Received: from mail21-R.bigfish.com (10.3.201.) by
AM1EHSOBE004.bigfish.com (10.3.204.) with Microsoft SMTP Server id
14.1.225.; Thu, 22 Sep 2011 09:17:03 +0000
Received: from mail21 (localhost.localdomain [127.0.0.1]) by
mail21-R.bigfish.com (Postfix) with ESMTP id 3A2802B0523; Thu, 22 Sep
2011 09:17:03 +0000 (UTC)
X-SpamScore: 1
X-BigFish: VPS1(zzc89bhc85dhzz1202hz70iz8275bh8275dhz2fh793h668hh61h)
X-Spam-TCS-SCL: 0:0
X-Forefront-Antispam-Report: CIP:162.53.;KIP:(null);UIP:(null);IPVD:NLI;H:SMTPC.CLIENT.CA;RD:none;EFVD:NLI
Received-SPF: pass (mail21: domain of client.ca designates 162.53.99 as permitted sender) client-ip=162.53.99;envelope-from=Jennifer@client.ca; helo=SMTPC.CLIENT.CA ;PC.CLIENT.CA ;
Received: from mail21 (localhost.localdomain [127.0.0.1]) by mail21
(MessageSwitch) id 131668298464274_181; Thu, 22 Sep 2011 09:16:24 +0000
(UTC)
Received: from AM1EHSMHS20.bigfish.com (unknown [10.3.201]) by
mail21-am1.bigfish.com (Postfix) with ESMTP id DF83E7D8059; Thu, 22 Sep 2011
09:16:23 +0000 (UTC)
Received: from SMTPC.CLIENT.CA (162.53.99) by AM1EHSMHS0.bigfish.com
(10.3.206) with Microsoft SMTP Server id 14.1.225; Thu, 22 Sep 2011
09:16:19 +0000
Received: from PWKREXTPR.ngco.com (10.62.18) by SMTPD.CLIENT.CA
(162.53.99) with Microsoft SMTP Server (TLS) id 14.1.2; Thu, 22 Sep
2011 04:52:54 -0400
Received: from PWKREXMPR04.ngco.com ([fe80::e0e8:d22e:251a:f3a3]) by
PWKREXTPR02.ngco.com ([fe80::30f2:8230:d57c:380%19]) with mapi id
14.01.0289.001; Thu, 22 Sep 2011 05:15:26 -0400
For testing purposes, I tried sending a message to the same distribution group from a Gmail account. It also got an undeliverable message. I was however able to send from the
same Gmail account to another existing distribution group that appears to have identical settings.
The sharp eyed among you will note the 550 Invalid Receipt that was spit out by messagelabs. According to their site:
The error message indicates that you have sent an email to an invalid address at the recipient’s domain. Please double-check the email address for any spelling errors. If you
believe the address is correct, please wait 4-6 hours and then try to resend your email. If the problem persists, please contact the recipient by other means (e.g. fax or phone) to ask for further assistance. you are trying to use me [server-x.tower-xx.messagelab]
as a relay The error message indicates one of the following issues: * Your DNS server has cached the recipient’s old MX record * You are trying to relay outbound emails through MessageLabs from an incorrect IP address * The recipient’s domain has
an incorrect MX record * The recipient’s email address contains invalid characters Please contact your administrator or your ISP to refresh your DNS server and then try to resend your email again. If the problem persists, please contact the recipient
by other means (e.g. fax or phone) for further assistance.
The e-mail used is indeed correct, and the problem continues to persist after a few days.
Any help would be greatly appreciated.
One click to automate them all!