I'm the Admin, what can I do to fix this? Login Home Knowledge Base News Tickets Community Back to Community Threads 1 AOL Email Users can not send email to Smartermail. You may get a better answer to your question by starting a new discussion. Wayne Howe June 18, 2015 at 8:20 AM Edit Delete It's not a SmarterMail issue. weblink
See error message: -------------------------- Action: failed Status: 4.4.2 Diagnostic-Code: X-Outbound-Mail-Relay; lost connection with mail.lobstertrap.com[18.104.22.168] while receiving the initial server greeting ------------------------------------------------------- I have run tests from third party web sites such This can result in a 4.x.x code being sent back. Cancel Delete Help Desk Software powered by SmarterTrack 12.2 © 2003-2016 SmarterTools Inc. Why you got a non-delivery report with error code 4.4.7 When Exchange Online attempts to deliver a message, the mail server that generated the error might be unable or unwilling to
This should not happen, unless you somehow have your domain misconfigured. One user is probably using an Alternate Recipient with the same email address as a contact. 5.4.7 Delivery time-out. Isn't that more expensive than an elevated system?
Changing ssl cert/dns names can cause you some grief though, they need to match. Why did I get a non-delivery report? How to cope with too slow Wi-Fi at hotel? 2048-like array shift Are there any saltwater rivers on Earth? Close Login × Not Logged In You must be logged in to perform this action.
Maybe an Outlook client replied to a message while offline. 5.1.2 SMTP; 550 Host unknown. Wayne Howe June 18, 2015 at 1:34 PM Edit Delete × Ban User Are you sure you want to ban this user? If you're experiencing this issue, please make sure you're running at a minimum SmarterMail 12.4. http://answers.microsoft.com/en-us/outlook_com/forum/oemail-osend/unable-to-send-emails-error-code-442-bad/f9ff9e76-1aa7-4a61-89b1-3985db77a861 of course, if you could get mail admin on other side to read his logs or tell you whats up or find the common denominator between those domains that reject you,
Cancel Delete 0 Bruce Barnes RepliedJune 19, 2015 at 7:01 AM Mark As AnswerMarked As Answer You can upgrade to the latest version of any owned product without paying for major A tracert to their outbound mx ip may prove interesting. We are now telling our customers that we can no longer guarantee delivery to any AOL hosted account. NO.
We upgraded his SmarterMail 11, thenremoved an inadvertently blacklisted AOL IP address, and mail from AOL was successfully received. Wayne Howe June 22, 2015 at 11:17 AM Edit Delete × Ban User Are you sure you want to ban this user? Help, please × Report Abuse Offensive LanguageWrong CategorySpam Cancel Send Report First of all a 4.x SMTP response code should not result in a bounce. Wayne Howe June 18, 2015 at 1:40 PM Edit Delete Ran MTU testing on our routers and all test at 1500 with max payload of 1472.
RFC 821 VERB Verbose. have a peek at these guys Generated Sun, 09 Oct 2016 23:47:04 GMT by s_ac15 (squid/3.5.20) Home Only a Few domains give 421 4.4.2 Connection dropped error but not Blacklisted by Struble9401 on Jun 5, 2014 at I must have somehow ended up with just one. Any other feedback?
I was trying to trace to mtaomg-mbe02.mx.aol.com × Report Abuse Offensive LanguageWrong CategorySpam Cancel Send Report × Ban User Are you sure you want to ban this user? If you used the wizard it SHOULD be right, but if it's really badly or even partly wrong, you'd see lots of errors not just one. Here's what your server responds: 220 mail.lobstertrap.com ehlo testing 250-mail.lobstertrap.com Hello [70.redacted] 250-SIZE 83886080 250-AUTH LOGIN CRAM-MD5 250-STARTTLS 250-VRFY 250 OK When I do the same with SmarterTools (or http://strongboxlinux.com/email-error/email-error-450-4-1-2.php Those were the only two issues I've seen recently - but glad you are not plagued by them.
But we can send email to AOL. You get this NDR when you make a typing mistake when you manually try to send email via telnet. Cancel Delete Please leave this box unchecked Reply to Thread TagsSmarterMail Related Community Threads0x800CC13: Cannot connect to the network. - Outlook 2013 / Windows 10 / ActiveSync / SM 14.1 EntProblem
we switched to a full hybrid configuration with O365 and don't have that issue anymore but, never did figure it out. Possibly the user was moved to another server in Active Directory. But he also discovered that a IP range we had blacklisted for spewing spamcontained part of the AOL subnet. The server doesn't reject the message with a 5.
Text Quote Post |Replace Attachment Add link Text to display: Where should this link go? Set up SMTP logging. 5.5.2 Possibly the disk holding the operating system is full. Cancel Ban User × Ban IP Address Are you sure you want to ban this IP Address? this content VRFY Verify.
AOL users can not send to us. Still need help with error code 4.4.7? Here's a listing of some of the MTU testing tools which are available, both online, and for download: https://www.google.com/search?q=mtu+test+tool&ie=utf-8&oe=utf-8 Here's a good explanation of MTU and why it can cause Secondly, AOL is a mess and I wouldn't believe anything they said.
You don;t say which domains are affected, so I can't help much, but two things you may have wrong: 1. For some reason the sender is not allowed to email this account. For example, when trying to send an email to [email protected] nonexistantdomain.com. [Example kindly sent in by Paul T.] 5.1.3 Another problem with contacts. Check where the expansion server is situated. 5.3.0 Problem with MTA, maybe someone has been editing the registry to disable the MTA / Store driver. 5.3.1 Mail system full.
Try checking this box: Allow computers which successfully authenticate to relay User may have a manually created email address that does not match a System Policy. 5.7.2 Distribution list cannot expand Address field maybe empty. Check limits, System Policy, connector, virtual server. 5.3.5 Multiple Virtual Servers are using the same IP address and port. Jun 5, 2014 at 3:42 UTC Struble9401 wrote: wccc is actually our domain.Then you could start by fixing your SPF record: it has a double quote hanging at the end, which