• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 760
  • Last Modified:

Email getting bouced to one particular user in a company - why?

Hi,

One particular user in a company cannot receive emails from an external party. Other people in the company can, but this one particular person cannot and it's been going on for sometime.

I got the external sending party to forward one of the rejection messages which is shown in the code snippet window.

I do notice it looks like the external sender is actually going through google mail (although their main email address is not a Google email address).

If the same external person emails another person in the company of the person not receiving emails, the email makes it through fine.

The receiving party has an exchange server behind a barracuda spam firewall, but the barracuda shows no sign of the email ever making it to the company (it logs all that it rejects).

What could be causing this?
Thanks



From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>
Date: 2008/11/18
Subject: Delivery Status Notification (Delay)
To: SenderOf@OriginalEmail.com
 
This is an automatically generated Delivery Status Notification
 
THIS IS A WARNING MESSAGE ONLY.
 
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
 
Delivery to the following recipient has been delayed:
 
    Recpiant@Email.com
 
Message will be retried for 2 more day(s)
 
Technical details of temporary failure:
Unspecified Error (SENT_RCPT): Connection timed out
 
  ----- Message header follows -----

Open in new window

0
afflik1923
Asked:
afflik1923
  • 7
  • 6
  • 3
2 Solutions
 
Jian An LimSolutions ArchitectCommented:
This is not very handful
do you have more .. something like it give up and not going to send?

0
 
Jian An LimSolutions ArchitectCommented:
what email systems you are using?
exchange?
0
 
CutshallCommented:
To me, this sounds like you may have an integrity problem with that users mailbox.  Have you tried rebuilding the mailbox? I would probably have that user download all of his email into a PST then I would delete the mailbox, rebuild it, make sure it's in Active Directory, have the user log back in then try to receive the mail from outside.  Another thing you can do is telnet into your exchange server via port 25 and try to send the user a piece of email right from your port.  This will help isolate the issue.  To send the user a piece of email via the port, do the following:

Telnet [exchange server ip] 25
helo
mail from:[email address of distance user]
rcpt to:[email address of user having problems]
data
[type a sentence here]
.
.

the two periods at the end are important.  After you do this, you should be able to see if the message made it or not.


Another option is to turn on tracking and find out what's happening to the email being received.
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
CutshallCommented:
Those commands will work with sendmail server also.  It must use the SMTP protocol to get this to work.  Port 25 is used for smtp type mail.
0
 
afflik1923Author Commented:
Yes, the lack of detail was frustrating. It took the usersages to get me this information but before that I was just told, "I'm not receiving emails from party A - sort it". The lack of appreciation for us IT folks.

Yes we are using Exchange servers. Exchange Server 2003, which is behind a Barracuda firewall. Did mention that but I guess did not make it clear.

Anyway, the good news is from the email I sent I have now managed to recreate the problem. Using a gmail account, sending to the member of staff who had a problem I do indeed get a rejection message back. However I send an email to another account and it goes through OK.

See the error message below which gives much more detail.
This is an automatically generated Delivery Status Notification
 
Delivery to the following recipient failed permanently:
 
    Recipiant@Email.com
 
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 503 503 This mail server requires authentication when attempting to send to a non-local e-mail address. Please check your mail client settings or contact your administrator to verify that the domain or address is defined for this server. (state 14).
 
  ----- Original message -----

Open in new window

0
 
afflik1923Author Commented:
Actually easier to read in a non code window so here is error again:
***************

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    Recipiant@Email.com


Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 503 503 This mail server requires authentication when attempting to send to a non-local e-mail address. Please check your mail client settings or contact your administrator to verify that the domain or address is defined for this server. (state 14).

  ----- Original message -----
0
 
CutshallCommented:
This issue sounds local and not remote.  It appears the mailbox you are trying to send to is having a problem especially if others can receive the email but this user can not.
0
 
afflik1923Author Commented:
Now looking at the user in active directory one thing I notice about the account that can't receive and my account on the network which can receive emails from gmail.

The one that cannot receive under "E-mail Addresses" still has

username@domainname.local
friendlyname@domainname.local
as well as the external email addresses.

Where as my account (which does receive gmail) does not have the .local entires.

Looking around user accounts randomly and I notice that generally some accounts do have the .local and others do not.

Of the users who I know have received gmail happen to not have them but maybe this is a coincidene?

Any thoughts?

Thanks for input so far.



 I do notice the member of staff who is having a problem has extra entrthe following entries in
0
 
CutshallCommented:
That is a great find.  Yes, it is important to ensure that these are correct.  Your template for users probably needs to be updated and you will probably have to go though the mailboxes to ensure that these items are correct.
0
 
afflik1923Author Commented:
However, note that I just added the .local to my own account and then emailed myself from gmail and it still went through.

Maybe that's different or maybe I have not given it time to take effect.

Any other wise words of wisdom and is it safe for me to delete the .locals from the staff member who cannot receive the email?

Thanks
0
 
CutshallCommented:
Here is the MS Exchange 2003 Deployment Guide.
http://www.microsoft.com/downloads/details.aspx?FamilyID=77B6D819-C7B3-42D1-8FBB-FE6339FFA1ED&displaylang=en

Here is the MS Exchange 2003 Administration Guide.
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=98E45481-1458-4809-97D6-50D8AEEBD8A1

They go into more detail concerning the local domain, message transfers and configuration.  I am also looking at some emails I've written for Exchange 2003 to see if I've seen this problem before.
0
 
Jian An LimSolutions ArchitectCommented:
i wont thinking to remove the .local
they are there for purpose...

try to do a telnet <servername> 25
mail from: <validinternalemailaddress>

RCPT to: <theaffecteduseremailaddress>

DATA

This is line one.
.


this is to test whether it works internally


http://www.cs.cf.ac.uk/Dave/PERL/node175.html
0
 
CutshallCommented:
As I understand it, the .local helps the exchange server determine local mail for the message transfer agent.
0
 
CutshallCommented:
here is some good info on exchange for you.  

http://www.christensen-software.com/support/config_exchange_2003.htm

In this example, the user Christensen.  Like you can see, after installing our Exchange Server from scratch only our AD domain "Christensen.local" was listed as accepted SMTP address. But emails from the Internet will be coming in addressed to "@mycompany.com" and not Christensen.local!
0
 
afflik1923Author Commented:
Thanks for all theinpt on this matter. After all my research it turns out I received some incorrect information which invalidates some comments.
It turns out the entire company cannot receive emails from the external party and not the individual user as originally reported.
I will close this thread and start a new one. I will post a link to the new thread once I have made it.
0
 
afflik1923Author Commented:
In the end on this one the problem was incorrectly raised without the correct details. Points awarded anyway for useful suggestions and input that helped resolve anyway.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 7
  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now