Home > Email Error > Email Error 5.1.2

Email Error 5.1.2

If senders who are outside of your domain receive this NDR when they send mail to recipients within your domain, try the following. Remove a single recipient Choose New mail. Could be Virtual Server SMTP address. 5.4.1 No answer from host. Anti Spam Articles Authors Blogs Books Free Tools Hardware Hosted Exchange Links Message Boards Newsletter Services Software Tips Webinars White Papers About Us : : Product Submission Form : Advertising Information navigate here

The next time you open the mailbox, you'll be using the light version of Outlook Web App. All rights reserved. However, with the proliferation of the spam, error 5.1.2 is also often encountered by automatic “out-of-office” replies to junk mail because the domain names used by junk mail are often bogus Here's what backscatter is: Spammers often falsify the From address of spam by using email addresses they’ve collected from the Internet instead of their own address. https://social.technet.microsoft.com/Forums/exchange/en-US/cf6b703a-269f-42c4-a585-dff3119cf4ea/when-user-send-mail-getting-ndr-512-invalid-email-address?forum=exchangesvrclientslegacy

Check the recipient's mailbox. 5.2.2 Sadly, the recipient has exceeded their mailbox limit. 5.2.3 Recipient cannot receive messages this big. Forum Software © ASPPlayground.NET Advanced Edition MenuExperts Exchange Browse BackBrowse Topics Open Questions Open Projects Solutions Members Articles Videos Courses Contribute Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Such an NDR is useless rubbish because it creates the false impression that you did something wrong. Our server tried ehlo, the recipient's server did not understand and returned a 550 or 500 error.

Thanks 0 Message Author Closing Comment by:plokij50062011-05-12 Good answer but didn't explain how to edit the cache file so a bit incomplete. 0 Write Comment First Name Please enter a Log off, and close your web browser. Check your Sent folder for any messages that you know you didn’t send. In summary: most SMTP error 5.1.2 conditions are caused by misspellings of the domain name part of a recipient email address.

If not, can you send e-mails to other users in that domain? 3. They’ll have to resolve the issue in order to prevent NDR 5.1.x errors. To return the mailbox to Outlook Web App, choose Options > Outlook Web App version, uncheck Use the light version of Outlook Web App, and then choose Save. this You might not need to try all of them to get the message sent successfully.

If an error is found, correct it in contacts list or address book for next time.It is possible that the domain is temporarily inactive. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Any other feedback? The recipient exists at the domain, everyone else can send.

Does the NDR generate by your Exchange server or the recipient’s server? If all the recipients email addresses check out as regards the domain part of the email addresses, then one of the servers on the way to the recipient(s) has a DNS Solution 1: Make sure the recipient's email address is correct    This is the most common issue that causes 5.1.x errors. How can we improve it?

Join our community for more solutions or to ask questions. http://csimonitoring.com/email-error/email-error-553-5-3-0.php Said differently: one of the servers on the way to the destination, including your server or your ISP, has a DNS problem or, possibly correctly, does not like one of the Check if there’s a current service issue in Office 365 affecting the user's account. Best regards, Serena Thursday, October 28, 2010 9:10 AM Reply | Quote 0 Sign in to vote Please find my answers: 1.

Microsoft Customer Support Microsoft Community Forums Home Company Services Hosted Services News Support Clients Partners Home Knowledgebase Status Submit a Ticket Remote Support Login Remember me Lost password Knowledgebase (11)proFilter (70)outmail Sometimes running RUS (Recipient Update Service) cures this problem. Check with your domain registrar or DNS hosting service to verify the MX record for your domain is correct. his comment is here Prolateral makes all reasonable efforts to verify this information.

It was in as a 'Mail to:' address instead of a SMTP address so even though it was spelled wrong it could not be sent. Note: Updates to a domain's DNS records can take up to 72 hours to propagate to all DNS servers on the Internet. If the person does have such a rule, they will have to either correct the email address or remove the rule in order to prevent NDR 5.1.x errors.

Is the user you cannot send e-mail to him in the same domain with you? 2.

Only that particular user is not able to send mail, others in my domain able to send. 3. Go to Solution 3 Comments LVL 4 Overall: Level 4 Exchange 2 SBS 1 Outlook 1 Message Accepted Solution by:evgeny_f312011-05-12 Try to delete recipient address from outlook autocomplete cache, and Address field maybe empty. Server or connector limit exceeded. 5.2.4 Most likely, a distribution list or group is trying to send an email.

Use the Down Arrow and Up Arrow keys to select the recipient, and then press the Delete key. Microsoft doesn’t support using more than one MX record for a domain that's enrolled in Exchange Online. Your message was routed to the wrong email server. http://csimonitoring.com/email-error/email-error-554-5-7-1.php Subject: touch base Sent: 10/20/2010 8:27 AM The following recipient(s) cannot be reached: David Thompson (user Email id) on 10/20/2010 8:27 AM The message could not

Hope it helps. Remove all recipients Choose File > Options > Mail. NDR below: Your message did not reach some or all of the intended recipients. Verify that you have only one MX record configured for your domain.

Please try the request again. This NDR is generated for this user only and happens whether we send via DNS direct from Exchange, or via the ISP's mail gateway. If you don’t see any suspicious messages, it’s likely that the NDR you received is backscatter. Join & Ask a Question Need Help in Real-Time?

If you have a hybrid topology, the solution might also be related to the on-premises mail transfer agent. If the spelling looks correct, contact provider and if necessary, contact the recipient another way (e.g., phone or text message).5.1.2: Official Definition[RFC3463] (Standards Track) from the The Internet Engineering Task Force Any trademarks referenced in this document are the property of their respective owners.