Incoming mail probs on new server install

I recently installed OSX 10.4.3 on my PowerBook G4 to evaluate mail services before setting up mail services on a dedicated machine. The OS is patched with all updates from Apple. I'm new to OSX Server but not new to administering email & dns services on Linux and Windows.
When I try sending mail to myself from a mail client on the server (Mozilla Thunderbird), the message stays trapped in the mail queue. I retry sending but the server logs say something to the effect unknown account. Eventually I have to just delete the message from the queue.
I can send mail out no problem but I can not also recieve any replies back to my account on my OSX server. I have a firewall connection to the Internet and have had not trouble evaluting incoming & outgoing email with other commercial email server software. So I know I have no firewall issues or other filtering issues with my ISP.
Anyone have some insight into why I can not recieve mail?
Thanks in advance!
PowerMac G5 Mac OS X (10.4.3) PowerBook G4

1 more bit of information. The following an email Yahoo's mail server sent back to me as I tried replying to an email I sent myself from Postfix on my PowerBook. My account hosted on Yahoo is [email protected] My account tied to my Mac is [email protected] Note that Yahoo's email server say relaying is not permitted.
Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[email protected]>:
68.82.56.6 does not like recipient.
Remote host said: 554 <[email protected]>: Relay access denied
Giving up on 68.82.56.6.
--- Below this line is a copy of the message.
Return-Path: <[email protected]>
Received: (qmail 40273 invoked by uid 60001); 16 Dec 2005 01:29:32
-0000
Message-ID: <[email protected]>
Received: from [68.82.56.6] by web208.biz.mail.re2.yahoo.com via HTTP;
Thu, 15 Dec 2005 17:29:32 PST
Date: Thu, 15 Dec 2005 17:29:32 -0800 (PST)
From: Mike James <[email protected]>
Subject: Re: test from squark auth smtp
To: Michael James <[email protected]>
In-Reply-To: <[email protected]>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
got message
--- Michael James <[email protected]> wrote:
test

Similar Messages

Is there a way to reverse the order of incoming mail in the new iPad?

I want to reverse the order of incoming mail on my new iPad. I want the oldest on top. I can't seem to find where or even if I can do this. Anyone know for sure? Thanks!

The Mail app only supports having the most recent at the top. You could see if any third-party email apps support it, or access your account via a browser (you can create a Safari shortcut on your iPad's homescreen for your login page).

Some incoming mails are totally unreadable after installing 10.6

Some, about 20%, of incoming mails are totally unreadable gibberish after I installed Snow Leopard on my Desktop MacPro. The same mail reads fine on my MacBook Pro (also now running 10.6). An example of such a weird mail is here:
ha sa S 7 s i ssho sb s s as s osg s h s skowassi wo sMag ssi s Ma s
Oiga sM ssag ... and so on and on.
If I copy the unreadable message and paste it into TextEdit it converts to other unreadable characters and numbers. If copied into a MS Word doc it appears as perfectly readable text.
Has anybody seen something similar?

OK, I think I have found a workaround for the problem. It is indeed a font issue... (thank you, William Lloyd, to point me in that direction!)
If you get an unreadable message switch to "Reply" or "Forward" and you will be able to read the message (make sure your own mailbox font or message font - set under Preferences>Fonts - is anything except Courier or Chicago) and you will be able to read your mail. Select the message text and go to Format>Go Fonts and switch to several other fonts. As far as I can see all fonts work OK except Courier and Chicago. Obviously Courier is a popular mail font, so all mails written with it arrive garbled. If I use Courier or Chicago as my Message List font in the preference settings, all mail windows become unreadable!
When I write a text in "TextEdit" and switch to Courier or Chicago - it will become unreadable. Possibly this happens in other applications as well...
However - this only occurs on my desktop PowerMac, not on my MacBook, which makes this glitch especially puzzling. I have not yet tried to re-insall OS 10.6.
Thomas

Moving mail to a new server

In my case, it is somewhat simple because I have only one account. But, in general, how do you move mail from one server to another? I have tons of messages still in the imap server that somehow need to get other to the new server.
The other sticking point is I have only one license. So I can't run both imap servers at the same time. In fact, I pretty much have to shutdown the current server just to work on the new server.
Thanks

hi - i just did this - found a script called imapsync (http://www.linux-france.org/prj/imapsync/). you can run it using this bash script:
#!/bin/bash
USER=$1
PASSWORD=$2
1MAILSERVER="";
2MAILSERVER="";
/usr/bin/imapsync "Junk|Deleted\ Messages" --host1 $1MAILSERVER mail server> --user1 $USER --password1 $PASSWORD --host2 $2MAILSERVER --user2 $USER --password2 $PASSWORD --syncinternaldates

Very low Incoming Mails on OS X Server 10.6.2 macmini Server

I have set up my Mailserver, i have the Reverse DNS, since two days after i let the miniserver online, the mail incoming was drasticly low, all my mail goes out. Sometimes when i send the test mail it arives 1h later, not everytime just sometimes.
in the Hostin Tab for Mailservice i have localhost and two other Domains as Alias inthere. Is somwhere on the Net a Test page for this thing, i just want to know is the Configuration Ok.
Thx for Help

Thanks, i think this is it.
Only the Thing that are not so much Spam like before, account was on ISP Server, but i dont know what Spam filter they have.

Exchange Server 2010: Incoming mail not delivered

I have an Exchange Server 2010 Standard with all recent patches and updates.
-It has been in service for 3 years without any issues.
-There is plenty of hard drive space for the logs and the data (over 100GB in each)
-The current size of the mail database is 150GB
-There is no registry entry in place limiting the size of the database ([url="http://technet.microsoft.com/en-us/library/bb232092.aspx"]Database Size Limit in GB as outlined here[/url]
Starting a few days ago, incoming mail is reaching the server but not being delivered to user mailboxes. Internal mail works fine when this happens. Looking at the Queue Viewer doesn't show anything abnormal. The Submission Queue shows nothing.
It is only after I reboot the Exchange Server that the Submission queue will show all the messages waiting to be delivered and they will all be delivered successfully after the reboot. The event logs do not show any error messages.
The server will continue to run fine for a few hours and then the problem starts all over again.
What could be causing this?

Any 3rd party antivirus/anti-spam software installed on the server? If so, disable and test.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Incoming mails get stucked

Everytime i start the mail program to get my new mails, the activity bar get stucked at the same spot of incoming mails.
all incoming mails left still the server of my provider (he sees zero mails there). so the 29 new mails are already on the way to my mac and therefore my provider can nothing do for me.
Any hints how to get rid of this bug mail number 2 or 3 of 29 on the way from cyberspace to my mac inbox which make my activity bar stuck ? thanks.

Hi and welcome to the discussions
I am curious about something in your post. If your mail download gets stuck on message 2 of 29, it follows that messages 3 to 29 have still not been downloaded from the mail server so I can't understand how your provider sees zero mails there. You might want to clear that up with him.
Normally my solution to this problem is to go to your ISP's webmail service and manually delete mail no. 2 from the list, and try retrieving your mail again via Mail.app.

New server installation SBS 6.5

We will be installing a new server with NSBS 6.5. Our old server has
been upgraded since the days of Netware 3.12. I am thinking about
installing NSBS 6.5 from scratch from our CD's and then patching to get
it up date, then bringing the data over from the old machine.
If this is workable, can I install just the most recent patch(es), or
do I have to install all the service packs since the beginning ?
Kevin
girbeaud

Just got a email from Dell that our server shipped. Almost 2 weeks
ahead of schedule. So now I need to plan everything out. What I am
thinking about doing is going from everything on the old server to:
OLD SERVER:
- Keep it running NSBS 6.5
- Keep certain volumes such as the CDSERVER (a hard drive containing
CD installation files for software programs, drivers, etc.), online
archives, etc. - things that we have multiple backups of which don't
need redundancy or frequent access to.
- Keep the PowerVault SDLT Tape Drive & Arcserve running on this
server. Our existing tape drive works fine, but may not be
compatible inside the new server. It currently has the capacity for
all of our files. If ever the new server actually fills up before we
need to replace it, we may need another backup solution for the new
server one day.
NEW SERVER:
- Install another installation of NSBS 6.5
- Install SYS, PROJECTS, and MAIL volumes, as well as any other
volumes necessary (Bordermanager cache, Web logs, etc)
- Run most services from the new server, including Bordermanager,
Groupwise, GWAVA, etc.
If this scenario would work, would I just do a fresh installation of
Netware on the new server, installing the products from the products CD
afterward as if we were installing NW for the very first time ? Then
we would simply copy data and settings to the new server & once things
were up and running, remove them from the old server ? Based on our
situation, I didn't think that migration utilities, etc were applicable
to keeping the old server in use... Thanks!
girbeaud

Can access mail on home IMAP server from work, but not at home

At home I have an Xserve running Snow Leopard Server with IMAP service enabled. This runs all my personal email. Even Gmail and iCloud accounts have their incoming mail forwarded to that server, because I prefer to house my own data. I have dynamic DNS with an MX record. The Xserve also runs DNS and resolves "imap.myip.net" to the internal IP address of the Xserve, and, when I am and work, "imap.myip.net," through the dynamic DNS service, resolves to the outside IP address I have through my ISP. My router forwards external requests on Port 993 to the Xserve internally.
Until recently, I could move my MacBook Pro between home and work and access my email without problems in either place. It appears that since the 10.8.2 update, I can no longer access my email from home, where I am on the same subnet as my IMAP server. When at home, Mail accesses external email servers (Gmail and my work account) without problems. For the accounts on my home IMAP server, the Mail Connection Doctor states that the IMAP server could not be contacted.
However, I can clearly ping it from my MacBook Pro, which means that it is reachable and that my internal DNS is working.
I just fired up my work VPN, and, sure enough, messages that Mail hadn't been able to collect are trondling into my Inbox. In other words, when making Mail access my mail server through the Internet there is no problem.
Even before the Mountain Lion update I found that I had to relaunch Mail when I returned home from work, or Mail couldn't connect to the mail server. It seemed like Mail cached the resolved IP address it had gotten at work, which is the external IP address of my home network, and failed to re-resolved the address of the IMAP server once I woke up the computer, after getting back home. Quitting Mail and relaunching it did resolve that, but it was annoying.
I have never worked with Little Snitch, but it might provide some answers as to what Mail is attempting to do, when it is failing to access the server. Do any of you agree or recognize this issue and have a solution?

It looks like a simple reboot fixed the problem.
Mac OS X is, by and large, so stable that I don't even consider rebooting as a troubleshooting step. There have been a number of application glitch that required a quit and re-launch to fix them, but that didn't do the trick with Mail. Very possibly reconfiguring everything from scratch had something to do with the fix, but in a way that required it to be combined with a reboot.

Using Yosemite My incoming mail server changes by itself and means I can't access my email. When I go to preferences the new incoming mail server is greyed out. I then have to remove the accounts and get new ones.

Using Mail with Yosemite 10.10.2.The incoming mail server keeps changing by itself and means I can't access my mail. I go to preferences and find that the new incoming server is greyed out . I then have to remove the accounts and then add them again with the correct server. The incoming server which is greyed out is imap.gmail.com

Try Mail/Preferences/Accounts - select the account, then go to Advanced and deselect "Automatically detect and maintain account settings".

Hi, I am new to Mac and i managed to install and configure all the services. Now my issue is when i sending mail using the local server to internal, mail are not receiving. Mail queue showing Connection refused error. Please help me

I am new to Mac and i managed to install and configure all the services. Now my issue is when i sending mail using the local server to internal, mails are not receiving. Mail queue showing Connection refused error. Please help me
Thanks
GIRI

Try this -> http://support.apple.com/kb/TA38632?viewlocale=en_US

New Edge server fails with DNS lookups - incoming mail stuck in queue

I just setup an Edge server, together with 2 Ex2013 servers with DAG. Sync works fine, however incoming mails are stuck at the edge server. The queue looks like this:
451 4.4.0 DNS query failed. The error was: DNS query failed with error ErrorRetry
Checking the logs, it also shows errors like this:
2014-07-12T16:32:06.599Z,08D16C05D02E2774,SMTP,"ex2.internal.contoso.com,ex3.internal.contoso.com,ex4.internal.contoso.com",>,DNS server returned ErrorRetry reported by 0.0.0.0. [Domain:Result] = EX2.internal.contoso.com:ErrorRetry; EX3.internal.contoso.com:ErrorRetry; EX4.internal.contoso.com:ErrorRetry;
2014-07-12T16:32:06.599Z,08D16C05D02E2774,SMTP,"ex2.internal.contoso.com,ex3.internal.contoso.com,ex4.internal.contoso.com",-,"Messages: 0 Bytes: 0 (The DNS query for 'SmartHostConnectorDelivery':'ex2.internal.contoso.com,ex3.internal.contoso.com,ex4.internal.contoso.com':'e01d6f93-e25b-4e36-9f2f-c1c7c73889ae' failed with error : ErrorRetry)"
Now the network is a little special, as the edge server is not in DMZ, but simply in a workgroup in the same LAN as the other Exchange servers. The edge server NIC's are configured to use the internal AD DNS servers, and the edge server is able to lookup
all the other exchange servers (ie. ex2.internal.contoso.com).
So I wonder why the edge servers logs DNS lookup errors as long as the server it self can lookup the internal hostnames for Exchange.
Any help would be great, as all incoming mail is now stuck at the edge server.

This is from the Edge server:
[PS] C:\Windows\system32>Get-SendConnector | fl
AddressSpaces                : {smtp:*;100}
AuthenticationCredential     :
CloudServicesMailEnabled     : False
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled            : True
DomainSecureEnabled          : True
Enabled                      : True
ErrorPolicies                : Default
ForceHELO                    : False
Fqdn                         :
FrontendProxyEnabled         : False
HomeMTA                      :
HomeMtaServerId              :
Identity                     : EdgeSync - MyCity to Internet
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
MaxMessageSize               : 100 MB (104,857,600 bytes)
Name                         : EdgeSync - MyCity to Internet
Port                         : 25
ProtocolLoggingLevel         : Verbose
RequireOorg                  : False
RequireTLS                   : False
SmartHostAuthMechanism       : None
SmartHosts                   : {}
SmartHostsString             :
SmtpMaxMessagesPerConnection : 20
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {}
TlsAuthLevel                 :
TlsCertificateName           :
TlsDomain                    :
UseExternalDNSServersEnabled : False
AddressSpaces                : {smtp:--;100}
AuthenticationCredential     :
CloudServicesMailEnabled     : False
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled            : False
DomainSecureEnabled          : False
Enabled                      : True
ErrorPolicies                : Default
ForceHELO                    : False
Fqdn                         :
FrontendProxyEnabled         : False
HomeMTA                      :
HomeMtaServerId              :
Identity                     : EdgeSync - Inbound to MyCity
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
MaxMessageSize               : Unlimited
Name                         : EdgeSync - Inbound to MyCity
Port                         : 25
ProtocolLoggingLevel         : Verbose
RequireOorg                  : False
RequireTLS                   : False
SmartHostAuthMechanism       : ExchangeServer
SmartHosts                   : {--}
SmartHostsString             : --
SmtpMaxMessagesPerConnection : 20
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {}
TlsAuthLevel                 :
TlsCertificateName           :
TlsDomain                    :
UseExternalDNSServersEnabled : False
This is from the Hub/CAS/MBX server:
[PS] C:\Windows\system32>Get-SendConnector | fl
AddressSpaces                : {SMTP:*;1}
AuthenticationCredential     :
CloudServicesMailEnabled     : False
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled            : True
DomainSecureEnabled          : False
Enabled                      : False
ErrorPolicies                : Default
ForceHELO                    : False
Fqdn                         : mail.va-world.com
FrontendProxyEnabled         : False
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : EX3
Identity                     : outgoing SMTP
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
MaxMessageSize               : 151.6 MB (158,965,760 bytes)
Name                         : outgoing SMTP
Port                         : 25
ProtocolLoggingLevel         : Verbose
RequireOorg                  : False
RequireTLS                   : False
SmartHostAuthMechanism       : None
SmartHosts                   : {}
SmartHostsString             :
SmtpMaxMessagesPerConnection : 20
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {EX4, EX3}
TlsAuthLevel                 :
TlsCertificateName           :
TlsDomain                    :
UseExternalDNSServersEnabled : False
AddressSpaces                : {smtp:*;100}
AuthenticationCredential     :
CloudServicesMailEnabled     : False
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled            : True
DomainSecureEnabled          : True
Enabled                      : True
ErrorPolicies                : Default
ForceHELO                    : False
Fqdn                         :
FrontendProxyEnabled         : False
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : Edge01
Identity                     : EdgeSync - MyCity to Internet
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
MaxMessageSize               : 100 MB (104,857,600 bytes)
Name                         : EdgeSync - MyCity to Internet
Port                         : 25
ProtocolLoggingLevel         : Verbose
RequireOorg                  : False
RequireTLS                   : False
SmartHostAuthMechanism       : None
SmartHosts                   : {}
SmartHostsString             :
SmtpMaxMessagesPerConnection : 20
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {Edge01}
TlsAuthLevel                 :
TlsCertificateName           :
TlsDomain                    :
UseExternalDNSServersEnabled : False
AddressSpaces                : {smtp:--;100}
AuthenticationCredential     :
CloudServicesMailEnabled     : False
Comment                      :
ConnectedDomains             : {}
ConnectionInactivityTimeOut : 00:10:00
DNSRoutingEnabled            : False
DomainSecureEnabled          : False
Enabled                      : True
ErrorPolicies                : Default
ForceHELO                    : False
Fqdn                         :
FrontendProxyEnabled         : False
HomeMTA                      : Microsoft MTA
HomeMtaServerId              : Edge01
Identity                     : EdgeSync - Inbound to MyCity
IgnoreSTARTTLS               : False
IsScopedConnector            : False
IsSmtpConnector              : True
MaxMessageSize               : Unlimited
Name                         : EdgeSync - Inbound to MyCity
Port                         : 25
ProtocolLoggingLevel         : Verbose
RequireOorg                  : False
RequireTLS                   : False
SmartHostAuthMechanism       : ExchangeServer
SmartHosts                   : {--}
SmartHostsString             : --
SmtpMaxMessagesPerConnection : 20
SourceIPAddress              : 0.0.0.0
SourceRoutingGroup           : Exchange Routing Group (DWBGZMFD01QNBJR)
SourceTransportServers       : {Edge01}
TlsAuthLevel                 :
TlsCertificateName           :
TlsDomain                    :
UseExternalDNSServersEnabled : False
I should note that all the Exchange servers are behind the same public IP, I just use NAT in my firewall to seperate the ports (50636 and 25 into the Edge server, 80/443 into the CAS/MBS server).

Trouble with Email after Update - Help - No Incoming Mail Server

I updated my iPad 2 to the new IOS 5 software and have been unable to use the mail function. I have tried deleting the account re-installing, turning on and off the iPad, etc. but it always prompts me with the same message;
The IMAP server, "apple.imap.mail.yahoo.com" is not responding. Check your network connection and that you entered hte correct information int eh "Incoming Mail Server" field.
All the rest of the Network functions seem to be working correctly. One additional detail - for some reason it does not seem that the "Incoming Mail Server" field downloaded during the update because there are no options (or maybe I do not know how to get to it) on how to change the incoming mail server information. This is true for both my iPad and iPhone 4.
Any suggestions or help?

I updated my iPad 2 to the new IOS 5 software and have been unable to use the mail function. I have tried deleting the account re-installing, turning on and off the iPad, etc. but it always prompts me with the same message;
The IMAP server, "apple.imap.mail.yahoo.com" is not responding. Check your network connection and that you entered hte correct information int eh "Incoming Mail Server" field.
All the rest of the Network functions seem to be working correctly. One additional detail - for some reason it does not seem that the "Incoming Mail Server" field downloaded during the update because there are no options (or maybe I do not know how to get to it) on how to change the incoming mail server information. This is true for both my iPad and iPhone 4.
Any suggestions or help?

Error in setting icloud mail on iMac - 'incoming mail server'

I created a new mail account in icloud and cannot edit this account in Mail Preferences on my iMac. Everytime I try to save my changes i get the following error:
"The incoming mail server filed cannot be empty."
Of course the field is automatically filled in and greyed out so it is not changable.
I have tried various fixes, deleting, setting up again, setting up the iCloud and Mail/etc. in System Preferences...
Help!

Hi Suebadu,
Welcome to the Apple Support Communities!
I know that it can be frustrating when an email account, such as your Gmail accounts, are not working as you would expect. In this situation I would recommend reading over and working through the attached article. The Connection Doctor may provide some further information as to what is causing the errors.
OS X Mail: Troubleshooting sending and receiving email messages
Best regards,
Joe

TS3988 The correct information in the email address, Full name and Incoming mail server panes are greyed out, and I can get no further in bring my iCloud a/c online. Any ideas? Thanks.

I've just updated and installed Mountain Lion. I've clicked for iCloud for Mail. The correct information in the email address, Full name and Incoming mail server panes are greyed out, and I can get no further in bring my iCloud a/c online. Any ideas? Thanks.

They are grayed out because they are automatically set up whey you check Mail in System Preferences. If you didn't do that, go back and do so and your iCloud email account will be set up automatically.

Incoming mail probs on new server install

Similar Messages

Maybe you are looking for