Mail server no longer receiving external emails

After a disastrous upgrade to Lion & then a full TIme Machine restore back to Snow Leopard, I've had some mail server issues. (Web services not working but fixed with this method).   Now noticed my server is now not receiving mail from external accounts...
Lots of posts suggested DNS problems but DNS does seem to be pointing some services to my server:
- Webmail page is working but on login returns an error: Error connecting to IMAP server: localhost. 61 : Connection refused
- Mail Client log in works (but not with the 'mail.' prefix) & can send email both internally & externally.   External mail sent in to my server is returned with the error: Host or domain name not found. Name service error     type=A: Host found but no data record of requested type
I'm guessing it might be an IMAP problem but I'd be very grateful if anyone could suggest what could be happening here.
Details:
Domain & DNS Web Log Errors   postconf -n    ps U postfix .

Yikes... Time machine doesn't back up mail.
http://docs.info.apple.com/article.html?path=ServerAdmin/10.6/en/asafc284c9.html
You may be out of luck. OS X Server shouldn't be backed up using time machine unless you've configured it specifically to back up things within it's limitaitons.
Personally I use TM to back up user home folders and Shared Drives. Then use retrospect to back up Mail and OD. Lastly I use a script that runs a MySQL dump every night to take care of the web server.

Similar Messages

After upgrading to Lion from Snow Leopard, mail server does not receive incoming email

After upgrading my server last night [2011.07.20] from Snow Leopard to Lion, my mail server settings went belly up. After toying around with the server, its certificates and what-not, I was able to get it running, but it is no longer receiving any emails [neither internally nor from Gmail, Yahoo, etc.].
I can send emails via SMTP just fine [using SSL] to external email accounts [and it doesn't complain when I address an email to an internal email account, but I can't verify that it's sending it to the internal email account because it won't receive!].
The Connection Doctor says that it is indeed connecting properly to the server [incoming = IMAP, outgoing = SMTP], so there is communication between Mail 5.0 [and also Thunderbird as well] and the mail server. The problem appears to be the mail server not receiving any emails - from internal or external addresses.
Anyone else having this problem or know of a fix for it?
Thanks!

Did you find a solution to this issue? My mail server is doing the same thing. I've tried six migrations now, and have a couple of tickets open, but they all have issues. I have worked around all of them except the mail server problem.
I did some more digging; the problem appears to be that on a migrated server, it leaves all of your mail store in the old location, doesn't move it, and then doesn't appear to upgrade spam-assassin properly. The net effect is that the mail server gets the SMTP communication, tries to pass the message into spam assassin, and then it goes south.
I see errors like this littered in the logs:
Jul 31 13:53:10 mail org.amavis.amavisd[5927]: bayes: cannot open bayes databases /var/amavis/.spamassassin/bayes_* R/O: tie failed:
Jul 31 13:53:10 mail org.amavis.amavisd[5927]: bayes: cannot open bayes databases /var/amavis/.spamassassin/bayes_* R/O: tie failed: No such file or directory
Do you see anything similar?

I can no longer receive me emails from my .mac account on my iMac even though I have been able to receive it for the past number of years, I have an iCloud account and it is sending my mail to my phone but not my desktop. What gives...

I can no longer receive my emails from the icloud to my mac even though it has been doing it fine since I moved to the icloud a number of weeks now. I only get my mail if I log into icloud or I get it on my phone, it is not synching to my iMac. Can someone assist please.
Thanks
Don

I tried something similar by adding a new mail account doing the apple id etc but it worked in that it would look for mail but no mail would come even though mail still goes to my phone I was loath to delete my original account just in case the new one did not work as well. So I guess I am a little stuck now.. I hope you can help me to sort it out.
Thanks

One Exchange Mailbox not receiving external email

DustinB3403 wrote:Do you have a split environment with AD onsite and Exchange hosted (It looks as though you do).I would check his AD account and see if a proper email "[email protected]" exists in the Email Address field.If it doesn't or is like "[email protected]" delete the account and recreate it.All email is on premise. He has the proper email address setup. We have 3 domains running through our exchange server, and when I set him an alias with another one of the domains, mail seems to flow properly, but only to the alias.
Viper One wrote:If it's a new user I'd just go ahead and removed the records and just recreate the account from scratch
I think I'm going to try this. Ill let everyone know how it goes.

Viper One wrote:You had a look on the Tracking Logs ???Check if you can see anything coming to that email address and what is happening with those emails.Im checking the tracking logs now. We can send email to the user internally without problems.
DustinB3403 wrote:Have you checked the settings on the account to be able to receive external email.Check herehttp://www.cryer.co.uk/brian/msexchange/exch_howto_disable_delivery.htmThere is an option on the user account to select who can send emails to this account that is likely the cause of your issues.I have checked this...
Looks good to me.
Ive set this account up just like all the others.

Exchange 2010: New Mailboxes cannot receive external email, but internal works fine. Existing Mailboxes are working properly.

Hello,
I can't seem to figure out what the problem is, but my new mailboxes cannot receive external email. The sender receives an NDR stating the following:
The error that the other server returned was: 550 550 No such user - psmtp (state 13).
Internally, the affected mailboxes can send and receive mail, and the mailboxes have no trouble sending mail out of the organization. I do not see an anti-spam solution installed on the exchange server, and I have confirmed that DNS resolved to the WAN IP
of this server.
Can anyone help me? The message tracker didn't appear to have recorded the NDR's that it sent, but it's possible I didn't view the logs correctly.
Thank you!
Paul
My environment contains two servers:
Server A: Domain Controller, Server 2008 R2, Exchange 2010 Standard
Server B: Domain Controller, Server 2008 R2

On Wed, 30 May 2012 02:01:19 +0000, Relion Support Inc wrote:
>
>
>Hello,
>
>
>
>I can't seem to figure out what the problem is, but my new mailboxes cannot receive external email. The sender receives an NDR stating the following:
>
>The error that the other server returned was: 550 550 No such user - psmtp (state 13).
>
>
>
>Internally, the affected mailboxes can send and receive mail, and the mailboxes have no trouble sending mail out of the organization. I do not see an anti-spam solution installed on the exchange server, and I have confirmed that DNS resolved to the WAN
IP of this server.
>
>
>
>Can anyone help me? The message tracker didn't appear to have recorded the NDR's that it sent, but it's possible I didn't view the logs correctly.
Is your Exchange server exposed to the Internet or do you have some
3rd-party device that does spam filtering? If you have something out
in front of Exchange that only periodically refreshes its cache of
valid SMTP addresses from the AD then you need to adjust the refresh
rate.
That "550 No such user" isn't a status code that Exchange returned.
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

I received a message telling me that I´m out of memory in my iCloud account, but its not true, but i can´t no longer receive no email, what should I do?

I received a message telling me that I´m out of memory in my iCloud account, but its not true, but i can´t no longer receive no email, what should I do?

Begin deleting data that is stored in icloud, like emails and iOS backups.

Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

Exchange server 2013 in Windows server 2012 VM
It was working fine then start the issue.
Firewall is managed externally and the last report said:
"I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
Can you verify that the mail server is set up so as to allow port 25? "
Today I was able to telnet the server from home: successfully
220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS
250-AUTH NTLM 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 XRDST
Also the receive - send connectors seems ok
Mx record point to Microsoft protection:
dualtemp-com.mail.protection.outlook.com.
Again, OWA is able to access and send/receive emails internal but never external even no bounceback just it never arrive.
Help me please. This is my first admin chaos...

Hi,
Is there any update with your issue?
If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
For more information about Exchange 2013 mail flow, here is a blog for your reference.
Exchange 2013 Mail Flow Demystified…Hopefully
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

As of 1:00pm Thursday, 3/1/12, I am no longer receiving any email, nor can I send anything out from my account. I am OS4.1.1, hoping to upgrade next week to Leopard (because my mac is not Intel-based), but in the meantime, it's non-functional.

Is anyone else having problems with the email? I am not receiving any emails, nor can I send anything out. Spent 30 minutes on online chat last night with someone most unhelpful, only to be told that the reason I'm not receiving anything is because my email is being forwarded to another address. I set my preferences to do that several years ago when this mac.com/me.com server began having so many issues, to ensure I was receiving email so I could check from my other address. The only comment I got was well, we no longer support 10.4.1 so there isn't anything we can do to help you. The status update says 33% of their customers are unable to migrate. So I'm pretty sure I'm not alone and that is a pretty large base of customers to no longer provide support to. Is anyone else who has not migrated to iCloud experiencing these email problems? Currently my iDisk works to transfer my larger files, but my email does not.

Hello, here's the fix I think...
I think they're slowly nudging people to switch, .mac & MobileMe are going away about July, may as well set it up now.
I understand .mac mail will still come through.
iCloud Mail setup, do not choose .mac or MobileMe as type, but choose IMAP...
IMAP (Incoming Mail Server) information:
• Server name: imap.mail.me.com
• SSL Required: Yes
• Port: 993
• Username: [email protected] (use your @me.com address from your iCloud account)
• Password: Your iCloud password
SMTP (outgoing mail server) information:
• Server name: smtp.mail.me.com
• SSL Required: Yes
• Port: 587
• SMTP Authentication Required: Yes
• Username: [email protected] (use your @me.com address from your iCloud account)
• Password: Your iCloud password

Why some mail from Comcast mail server is not received?

I am a new iMAC user (Mavericks 10.9.2). I just setup my Mail with 4 accounts using the guided setup on the MAC for the first account and then instructions from Comcast for the rest. All 4 accounts are setup for POP. All accounts are setup NOT to delete Email on the server for 1 month. Testing sending/receiving to/from the 4 accounts shows some very strange problems:
- Emails sent to any of these MAC mail accounts from a PC with Eudora (as the client) consistently arrive without any problems
- Emails sent from Comcast's webmail, from Outlook on an other PC and from the MAC itself via MAC mail end up on Comcast's server but never in the MAC's Inbox
I can see the Emails arriving on Comcast's server via Webmail from a PC. I also cc-ed myself and received all test Emals without any problems on the PC.
I called Comcast and their Email specialist said that they never heard of a problem like this one. They sent a test Email which was received on the PC but not on the MAC. They said that we should talk to Apple....
Any help would be very much appreciated.

Hi Suzy2014,
Here is a related - in a way - "weird one" for you: Ironically, I had Comcast Webmail and Macintosh Mail client problems of a weird nature, myself (on my new iMac 27": which is also running OSX Mavericks 10.9.2) - and: the issue(s) occurred THIS PAST EASTER 2014 weekend.
I had no problems w/ Comcast email forwarding, initially, after having many months ago done the initial set-up /forwarding. But for some strange reason, last Friday all my new (and older), Comcast-forwarded email to the iMac in question suddenly just evaporated off of that iMac. Something like 17 emails of all sorts from them; most since early 2014. Some involving service & changed billing costs /issues that land squarely in the lap of Comcast management
NOTE: I have lately begun having [unrelated to email] 'other problems' with Comcast - which came to light just late last week - I won't go into them here, for now, but: I wondered if Comcast could (somehow? I know it seems so unlikely; paranoid, even ... but stranger things have been proven after the fact in the computer business. Think about it...) Anyway ... could they have 'prevented' me from forwarding their emails to me; and /or screwed-up, or around, with my email - or other(?) settings, configs, etc. As an harassment tactic. Seriously - it's crossed my mind since last Thursday /Friday. Here is my email story, courtesy of Comcast /xFinity::
- The mail was there for a long time on my Mac;
- Then these other issues arose (not email related) with Comcast;
- My mail (POP acct't with them) was gone within an hour of me challenging them over the other stuff;
- I called their tech support first;
- the guy that finally came one wanted me to give him verbal "permission" to allow him to move around my iMac after I agreed to download their screen sharing app;
- I'm really fairly expert with Macs /OSX oddities, in particular; Apple refers to me as a 'sophisticated user.' Whatever. I don't want kudos, believe me: just the solutions - if they even exist.
- Anyway, the Comcast tech could not figure out why the email from them disappeared, nor why it would not re-download. Of course - it should have, as I set up forwarding it a long time ago; I assumed it would just re-download to the iMac 27. It did not.
- He eventually put me on hold - so I played devil's advocate, and quickly configured my OTHER new Mac: a MacBook Air 13 /Apple Email client to have an identically config'd Comcast account in it. Before I even finished setting it up on the Air 13 - the Account Preferences on that laptop actually 'finished setting itself up' - and POOF - *all* of the missing mail that used to be on the iMac 27 immediately downloaded into the new mailbox I'd just set up on the MB Air 13;
- Odd, I thought.
- This guy came back online; he ended up resetting my Comcast login PWD; then he maneuvered my mouse all around the iMac 27 very quickly, changing settings (one of the things I noted to him was that the Comcast smtp server had gone 'offline' as of a few hours prior, and that I could not get it to come back online). Well that didn't work.
- He was brusque; and he ended up deleting my Comcast account totally on the iMac, and I reconfig'd it (by then I took over all the tasks, as I didn't like the way he skipped around the computer like he owned it, when I was capable of doing anything necessary for him); That 'plan' did not work, either.
- He never did explain possible reasons for any of these "phenomenon;" nor did he ever get the Comcast SMTP mail server to come online, either. He told me he had no idea what was going one, and told me to call Comcast's "for pay higher level of support service" - (I refused) - or to call AppleCare (which I 'd planned to do, anyway).
- Before I ended the call I had him observe as I logged into Comcast's [horrid] Website(s) and email account pages/settings I have, like you must. Oddly - MAIL FORWARDING from my Comcast email account to my primary email acct. *had been DISABLED.* How could this have just "happened?" Well - he refused to explain anything more. In short - he was useless, as support techs go.
- This phone call to Comcast tech support next came to an abrupt end; plus - he never disengaged the screen-sharing session he had me agree to engage; that made me a bit uncomfortable too, to say the least. I ended the still-on sharing session after he hung up - right away, myself - and deleted all instances of the Comcast sharing app.
- I of course called AppleCare; ironically, while waiting for a Sr. Advisor form the CPU Division to come on - suddenly the Comcast smtp sever suddenly came online; and the mail that would not again download to my iMac 27 - suddenly did - just like it did on the first-ever /new account I set up as a test (for my own edification, and knowledge of troubleshooting such things, across "like" computers) e.g., what I set-up while on hold with Comcast, on my MacBook Air 13. Which worked perfectly. I note this too: I went into the Keychain on both of these Macs of mine: I was suddenly locked-out of viewing the Comcast entries for PWDS for [their] mail incoming /outgoiong Keychain login /PWD entries. Shocking, really, as I've done that a million times beofre; and never - as full admin of all of my computers and networks - have seen THAT. A coincidence. I dunno. I suspect ... something, though. I just don't know what - yet.
I bring this long story up (sorry for the length) - for one reason, actually. Comcast /xFinity does some spooky - even unsavory - things (not limited to email issues alone, trust me). That said : be careful with them; your networking; you Macs; your privacy, etc. I am rather suspicious of "them," now, and for several reasons, as noted.
Hope you have no more problems with them! Be well!

Cannot receive external emails

I have one account on Exchange Server 2013 that only receives internal mail, external mail gets rejected with the following error:
Reporting-MTA: dns;DUB004-OMC1S11.hotmail.com
Received-From-MTA: dns;DUB110-W4
Arrival-Date: Fri, 27 Mar 2015 02:22:32 -0700
Final-Recipient: rfc822;<email>@<Domain>.co.uk
Action: failed
Status: 5.7.1
Diagnostic-Code: smtp;550 5.7.1 Recipient rejected (R4)
The email account appears to have the same settings as the email accounts that accept both internal and external email.

Hello,
Good Day...
Request you to please follow the below steps
5.7.1
A very common Exchange 2010 NDR, the cause is a permissions problem. For some reason the sender is not allowed to email this account.
Perhaps an anonymous user is trying to send mail to a distribution list.
Alternatively, a user may have a manually created email address that does not match a System Policy.
Check SMTP Virtual Server Access Tab. Try checking this box: Allow computers which successfully authenticate to relay.
Check the outgoing SMTP logs.
Check: Mailbox – <Mailboxname> – Properties – Mail Flow Settings – Message delivery restrictions.
Try disabling Windows-Integrated-Security. Instead allow only standard authorization on the SMTP receiver on the Exchange 2010 server.
Check Attachment filtering on the Edge server.
Also you can follow the below steps
Add the user/aliases affected by this to the User List
Found under Management tab > User Management
Change the Unknown Users setting
Found under Management > Inbound Filtering
> Spam Handling Settings > Unknown Users
NOTE: BLOCKED is the recommended option
Cause : When Unknown Users is set to block and the user is not listed in the Control Panel, then email to that user is rejected.
For More Info: http://www.techrid.com/exchange-server-2010/mailflow/exchange-server-mail-flow-troubleshooting-with-list-of-exchange-2010-ndr-codes-2/
Regards,
Praveen
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts @ Techrid.com

Exchange 2013 stops receiving external email after about 8 hours

Hello,
Just installed 2013 excahnge server 3 days ago. We noticed after the first night that we did not receive any external emails throughout the night. I could not find anything wrong with receive connectors. Telnet works internally when this
happens but NO access from public side testing with telnet. After I reboot the exchange server everything functions just fine and normal for about 8 hours until it happens again.
I dont know what to check or look for at this point. Very new to exchange 2013. Any kind of advice would be helpful at this time.
It is not a firewall issue. Same firewall and set of rules that we use for other/old mail servers. We only have 1 exchange server that has all roles.
Lead Pusher

OK... Did alot of testing and spent some time with Microsoft's support on the phone.
I believe there is actually two problems going on in this thread.
1. Exchange 2013 Admins that have changed the default receive connectors are experiencing a conflict on the scope settings. Make sure that none of the receive connectors are using the same ports, and that you have not modified the security settings in anyway
unless you really know what you are doing.
If you are unsure of what the settings should be after you have change them, the only suggestion I have right now, (as I have not taken the time to do screen shots or write down all the default settings) is to install Exchange 2013 on a virtual machine and
look at them, then change back the settings that do not match.
2. The Malware Agent has a flaw that is causing the the Microsoft Exchange Transport service to endlessly wait on the Malware Agent to process a message that it just can't handle. (Two reboots of the entire server may be needed to clear this, or sometimes
you can get away with restarting the Microsoft Exchange EdgeSync service.)
The Microsoft technician had me perform a sequence of steps that highlighted this. To see if this is infact your problem you can perform the following steps.
A) Once the Exchange server stops processing messages, figure out the rough time it stopped processing messages.
B) Open the event viewer.
C) Under "Windows Logs", right click "Application", select "Filter Current Log...", check "Warning" and "Error", then click "OK".
D) Scroll down the log to the rough time that your Exchange Server stopped processing messages. You are looking for a slew of errors about the same time from "MSExchange Extensibility" (1051), "MSExchange Transport" (9201), "MSExchange
Transport" (9201), "MSExchange Extensibility" (1056), "MSExchangeTransport" (10003), and "MSExchange Common" (4999).
It is the "MSExchangeTransport" (10003) that I believe is the real problem. The Microsoft technician agreed. He did not want to spectulate as to exactly what was going on, but it seems to me that since he had me disable the "Malware Agent"
for now, that it is indeed the problem.
E) So.... Open the Exchange Management Console and type "Disable-TransportAgent", followed by enter. It will prompt "Supply values for the following parameters:". Enter "Malware Agent", press enter again. Type "A",
for yes to all.
or
http://technet.microsoft.com/en-us/library/jj150526.aspx"
F) Go to run, enter "services.msc". On the window that opens, find "Micorosoft Exchange Transport" and restart it.
I know this is NOT a fix, but a work around that is less than desired as the Malware Agent is a filter to keep unwanted emails out. I highly recommend running some sort of 3rd party spam/Malware filter that has been fully tested to run with Exchange
2013 if you do this.
Microsoft is to contact me back once they can figure out why this is happening, and I believe in the end a patch for Exchange 2013 will be produce to correct the problem.
In the mean time.... don't waste your money on paying Micorosoft for support, as I have already done this.
For the individuals who say they are not experiencing trouble, I am going to go out on a limb here and say that either you have a 3rd party software program that is filtering the mail before it reaches the Malware Agent, you have disabled the Malware Agent,
or you are using another mail server to forward email to your Exchange 2013 server. With either of these cases you are much less likely to see this problem.
One last issue that a few people may be experiencing, is Exchange 2013, running on Server 2012 that is a VM. Several VM setups have a bug with the VM NIC management interface and Windows Server if you are using the same NIC for both. For example Xen
Server 5.6 and XEN XCP both have this bug. There is an patch for XEN Server 5.6, but so far nothing for Xen XCP.
I have spent many hours trying to figure my problems with Exchange 2013 and I will not swear that my entire post is correct, but I have gotten very much closer to a stable mail server after much work. If you feel that anything is incorrect, please reply
back and let me know why, so that we may all benifit.
P.S. Sorry for the mis-spellings and what not, I am very tired at the moment, and was forced to use explorer, because this site is not liking Chrome at the moment. (Will not let me login)

Mail server no longer accepting incoming mail

First off, let me just say that yes, I broke it. This is on an iMac G4 with Server 10.4.11.
So here's the problem. I am by no means a qualified Server Administrator, but since I am a relatively knowledgeable computer geek, my boss plugged me into this position while my department is slow. I've been tasked with figuring out a few nagging problems with slow mail delivery, among other things.
I did some serious Googling on the issue of slow mail delivery, messages getting stuck in queue, etc. I determined that the issue was with spam filtering and anti-virus. Following some great documentation from osx.topicdesk.com, I updated and configured clamav, amavisd, and spamassassin. Miraculously, this actually solved the problem, and everything was working great.
Until today. Today I noticed a log entry that reverse DNS lookup of the server's IP (192.168.1.1) had failed. Googled again and found some info on setting up DNS on the server, which I did.
There was a secondary goal for doing this. We are a small company that hosts our own email and a tiny web server on a machine at our corporate office. Our remote locations have always been able to get email from the server via POP3 using the FQDN mailman.mycompany.com, which has a public IP address. Our router is configured to forward traffic to that IP to the private IP 192.168.1.1. However, all users at the corporate office had to be set up to use server IP 192.168.1.1 to get their mail because there was no way to resolve the FQDN into an IP that was visible on the private network. Or maybe there was/is, but I don't know about it. Anyway, we have a couple mobile users that work at multiple locations. They are set up to use the server's FQDN, but every time they come to our corporate office, they'd have to change their mail setup if they wanted to get mail, because once they're behind the router, the FQDN doesn't work. I think that makes sense.
The Server is also the DHCP server for this site. Prior to this morning, it was distributing our ISP's DNS IPs. Once I'd set up DNS on our Server, I changed it to distribute its own IP as the primary DNS server, and per someone's post, I modified named.conf to include our ISP's DNS IPs. The server name I set up is 'server' and the domain is 'mycompany.com'. I also set up an alias of 'mailman' and set it as a mail server. I then went to a couple of workstations in the building and did a Lookup on server.mycompany.com and mailman.mycompany.com, both of which returned an IP of 192.168.1.1. I did a lookup on the IP and it resolved back into server.mycompany.com.
Figuring I'd accomplished enough for the first half of the day, I went to lunch. When I got back, I was bombarded with complaints that mails were being bounced when sent from inside the building, and a few people had received phone calls that mails sent to them had been bounced back to their senders. The error given is:
554 554 <[email protected]>: Relay access denied (state 14).
(This came from Google. The wording varies from person to person but it's always SMTP 554, relay access denied.)
In a panic, I un-did everything I'd done this morning, turning off DNS server, telling DHCP server to begin distributing our ISP's DNS IPs again, but I'm still having the same problem. I didn't see how this could be the cause, but did it just as a precaution.
I doubt I've provided enough information, but does anyone have any initial guesses as to what's going on here?
ARM

Thanks for the quick, easy fix. I'm curious if you know what I might have done to cause this to happen. I don't recall changing any Mail settings.
Sometimes Server Admin "forgets" settings.
Also, apparently something I did wiped out our IMAP mail store. I had a backup thankfully but wondering how I might have done that?!
Wiped out at the file level as in no contents in /var/spool/imap/user?

Can I set my iCloud email as the outgoing mail server for my google apps email account in Mac Mail?

I have a google apps email account from an old client, all my work emails have been going to it for years. As I'm no longer affiliated with this client I'd like to make a transition to using my iCloud account for work. I asked people to use my iCloud address but as they've been using my google apps address for years it's what automatically comes up when they type my name.
I figure the easiest way to make a transition is if I reply to all the emails that arrive at my old address from my iCloud address and gradually they will start using my new address without realising it. But I can't find a simple way to do this.
In Mac Mail preferences > accounts > Google IMAP (my old account name) > Account information > Outgoing Mail server (SMTP) I'd like to set my iCloud SMTP server. But although my iCloud account uses its own outgoing mail server for its own account , it is not in the server list when I select my google account. I've tried to add it to the server list as smtp.mail.me.com but it caused my whole iCloud account to give me error messages until I force quit Mail...
Any ideas?

In iCloud/Mail, have you tried going to Preferences (select with gear at lower left)/Composing and setting a Send from address there?

Mail will no longer receive on Entourage, only on my iPhone. Help!!

I've just got an iPhone and have recently got a new Macbook.
I use entourage to collect my business emails, and have set my iPhone up to also recieve them. Mail is coming through find on the iPhone, but not on the Mac through Entourage. It gives me an error stating it is "In Use" and "Mailbox Locked".
How to I amend this so I can receive the mail on both?

Sounds like this account is a POP account an if so, you cannot have two email clients checking the incoming mail server for a POP account at or near the same time. You can't have both email clients launched and running actively checking the incoming mail server for a POP account at the same time.
Although it is possible to access a POP account with more than one email client, a POP account is really designed to be accessed with one email client only.
This is not a problem with an IMAP account.

ICal Server sends invitations via external email but no RSVP

I have set up a fresh install of Mavericks Server (10.9.3) running DNS and OD Services and now enabled iCal Server.
I setup invitation of external users via an external email address and invitations get sent and delivered via email just fine so I guess plus-addressing must be supported by the mailserver.
However the invitations do not show the RSVP requests and do not automatically get picked up by Calendar.app.
The server sits behind a NAT router and runs its own Split-DNS setup for the same local domain myserver.xyz.com that the router also redirects to the internal IP address of the server for external access to the iCal Server (so, FQDN is working for the server). The email account used for invitations is hosted on an external mailserver that runs on the same domain (mail.xyz.com).
Did I miss anything in my setup?
Thanks for any input.
Pete

Okay, got this figured out. Appears that the email server my client's company uses is terminating the connection when the Xserve tries to do anything. I setup a test Gmail account and used those settings instead and everything worked just fine.

Mail server no longer receiving external emails

Similar Messages

Maybe you are looking for