-
March 6th, 2006, 06:58 PM
#1
Email Error 554, Relay Access Denied
Got an email problem to throw at you --
User tries to send email to forward@email.com that forwards email to user@email.com, but it bounces back like so:
The following recipient(s) could not be reached:
forward@email.com on 3/6/2006 9:34 AM
There was a SMTP communication problem with the recipient's email server. Please contact your system administrator.
<exchangeserver.domain.com #5.5.0 smtp;554 <forward@email.com>: Relay access denied>
Googling the 554 error, everything I've thus far read said it's a problem with the sender's SMTP settings. However, this user can send email to anyone else, just not this particular user.
I checked the settings on the server that handles email forwarding, and all that's configured as it should be -- forward@email.com is indeed configured to pass email along to user@email.com.
-
March 6th, 2006, 07:19 PM
#2
Can you send an email to the second one OK, without forwarding it?
-
March 6th, 2006, 08:23 PM
#3
Sounds like someone may have some sort of recipient filtering enabled on their SMTP server or within Exchange (especially if it's 2003). Is forward@email.com an object that is in Active Directory?
-
March 6th, 2006, 08:45 PM
#4
Using a special "tech support" account we set up through their exchange server, I tried sending a test message to the forwarding account. I received the same bounce back message myself. I just tried sending it directly to the actual email account, and have yet to get a bounce message.
Note this is sending mail as an entirely different user on the same Exchange server.
-
March 6th, 2006, 09:51 PM
#5
Ok the so you can send a mail direct to the user with out going via the forwarding address, thats a start!
Can you be more specific on how you are configuring the forwarding - as it would seem that this is where the problem is!
-
March 6th, 2006, 09:57 PM
#6
On the SMTP server is a program called Rocklife MailSite that handles the forwarding. I go into Mail Site Console --> SMTP server name --> Domains --> email.com --> Mailboxes, then run a search for the user name. In the SQL mailbox properties for this user, the "Forward mail to:" field is set to user@email.com.
It works for all the other users, so it looks to be configured properly.
-
March 6th, 2006, 10:37 PM
#7
oookay, maybe some kind of filter on the recipients end that is blocking the forwarded (is that a word??) mails??
Can you post any headers?
-
March 6th, 2006, 10:48 PM
#8
(Again, I've only changed user and domain names.)
Microsoft Mail Internet Headers Version 2.0
From: postmaster@publishingconcepts.com
To: tech_support@publishingconcepts.com
Date: Mon, 6 Mar 2006 13:41:13 -0600
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="9B095B5ADSN=_01C640D8F002D48E00000FA9exchange01.publi"
X-DSNContext: 7ce717b1 - 1194 - 00000002 - 00000000
Message-ID: <37cfJiY9Z00000097@exchange01.publishingconcepts.com>
Subject: Delivery Status Notification (Failure)
--9B095B5ADSN=_01C640D8F002D48E00000FA9exchange01.publi
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01C640D8F002D48E00000FA9exchange01.publi
Content-Type: message/delivery-status
--9B095B5ADSN=_01C640D8F002D48E00000FA9exchange01.publi
Content-Type: message/rfc822
Received: from mail pickup service by exchange01.publishingconcepts.com with Microsoft SMTPSVC;
Mon, 6 Mar 2006 13:41:12 -0600
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_001_01C64155.EC54F2FD"
Subject: Test Message
Content-Class: urn:content-classes:message
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Date: Mon, 6 Mar 2006 13:41:11 -0600
Message-ID: <B987BCFC6DA0134F812E3ADD55C79247C270AD@exchange01.publishingconcepts.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Test Message
thread-index: AcZBVwmChDBg8nGZQC+D+KVBeOqzog==
From: "PCI Tech Support" <tech_support@publishingconcepts.com>
To: <forward@email.com>
X-OriginalArrivalTime: 06 Mar 2006 19:41:12.0480 (UTC) FILETIME=[ECA37A00:01C64155]
------_=_NextPart_001_01C64155.EC54F2FD
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
------_=_NextPart_001_01C64155.EC54F2FD
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
------_=_NextPart_001_01C64155.EC54F2FD--
--9B095B5ADSN=_01C640D8F002D48E00000FA9exchange01.publi--
-
March 7th, 2006, 12:07 AM
#9
Hi
Did the email have an attachment, if so, some carriers may have files size limitations, and you may need to split the attachment or check with the carrier to increase the size....
PC Registered user # 2,336,789,457...
"When the water reaches the upper level, follow the rats."
Claude Swanson
-
March 7th, 2006, 12:10 AM
#10
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|