Mail server is always downloading at 800K

I have a Mac OS X 10.5.6 mail server that is constantly downloading at 800K. I don't know what it is downloading, but a graph on my network monitor has it flatout at 800K.
I'm using sbl.spamhaus.org, cbl.abuseat.org, bl.spamcop.net, xbl.spamhaus.org to block junk.
I have noticed a lot more junk mail over the last few weeks.
I've tried blocking individual IP addresses, that I see in the smtp logs, hoping one of them will be the culprit but this has not helped.
I'm keen to find a fix. My mail server has downloaded 22 GB in 9 days.
I tried turning off the scan for junk mail and scan for viruses but it didn't have any effect.
I turned disabled SMTP and the problem stopped. I can't leave smtp disabled!
Any ideas about what could be causing the traffic?
Message was edited by: sp0radic

I experienced this issue with a corrupt mailbox as well. A single user had a corrupt mailbox that needed a reconstruct and when I eventually tracked down which user, their mail client was indexing and attempting to retrieve every single mailbox the user possessed repeatedly (And never finishing).
Interestingly enough, their iPhone could access everything fine at the same moment. Reconstructing the users mailbox resolved the issue of both their mail client (apple mail) accessing the folders and the corresponding net traffic.
I know this wasn't your issue but tagging it here in case anyone else experiences it and comes looking.

Similar Messages

My outgoing mail server is always offline...

I am having a nightmare with mac mail.
It has worked fine for months since started using it and for past few weeks I've been unable to send mails from the account.
It says the outgoing acct is offline.
I have rekeyed in and checked preferences and tried numerous alternatives on ports and stuff [under guidance of cleverer people than me]
I have reset my BT Home Hub. I have tried under IMAP and POP and still no mails out.
Incoming is fine and outgoing works fine when I am on someone else's [anyone else's] wi-fi...
So I expect this is something specific to do with my mac and my router... but no idea what to do?
ANy advice really gratefully received...
I just upgraded from Leopard to Mountain Lion on off chance it would sort it... it didn't!
Thanks

OS X Mail: Troubleshooting sending and receiving email messages - Apple Support

I have a new i phone 5 nad my mail is now constantly downloading, how can i stop this?

I have changed my work phone from an I phone 4s to I Phone 5. When I go to my mail it is always downloading and starts downloading emails from 2009. It takes a hours to download all the old emails and it takes hours for new emails to come through.
Then frustratingly it will do the same process all over again.
I have changed very possible setting but with no success.
The email come from my works server and is a microsoft exchange email account.
Please can someone help as this is really making life complicated.

Settings > Mail, Contacts, and Calendars > select the account > change the number of days to sync.

HT3678 If I download a .mov file from gmail, I am not able to open the file. I reinstalled QuickTime 7.6.6, still unable to open the file. If I download the same file from another mail server I have no trouble. What is gmail doing to my file?

If I download a .mov file from gmail, I am not able to open the file. I reinstalled QuickTime 7.6.6, still unable to open the file. If I download the same file from another mail server I have no trouble. What is gmail doing to my file?

Also i have reinstalled the reader9 two times and tried with reader8 also but in both the cases same problem.
it would be gr8 help if someone can help.

The past few days my Mail app has started downloading multiple copies of e-mails from all pop servers. This is only happening on my Macbook not other macs. Deleting mail from server does not help. I ran ClamXav found 2 viruses deleted problem continues

opps. Long title there... The past few days my Mail app has started downloading multiple copies of e-mails from all pop servers. This is only happening on my Macbook not other macs. Deleting mail from server does not help. I ran ClamXav found 2 viruses deleted those. Checked for software update and installed suggested downloads. Problem still contintues. Any suggestions?

Folks,
even after having repaired the inbox folder under "properties" a few times, I still had some e-mails where the contents are different from the subject line.
In other words in the inbox there are two e-mails: one with subject line "abc", and another one with subject line "def".
When I display the e-mail with the subject line "abc", the contents are from the e-mail with the subject line "def" in the in-basket.
What else can be done to correct this problem?
Thanks and best regards.
Fred Kunz-Shirzad
Chemin Ronzeures 6A
1297 Founex VD
Switzerland
[email protected]

Iphone 4s does not download emails using imap when connecting to smartermail mail server

iphone 4s does not download emails using imap when connecting to smartermail v2 mail server.
when I search - the search results show and i can view the emails, but inbox doesnt download emails - says load more messages x read..
the folders are displaying ok.
Smartermail 2 is about 10 years old ( im not upgrading as its working fine other than this issue ) imap is fine with other mail clients.
has anyone else experienced this?

Just had the exact same issue on iOS 7, SmarterMail Enterprise 6.8
https://discussions.apple.com/thread/5462200

Mail on server won't download to my inbox

Hi,
I am using a POP account, all the latest software updates, etc. When I get account info, I see all the most recent messages in the window, but when I go to get mail, it will only download messages up to a certain date (December 6th). I've tried rebuilding the mailbox, deleting the envelope index file, deleting the messagesuidownloaded file, and nothing has worked. I've ran disk utility, etc. I have two other pop accounts that are working fine. I am successfully able to download all messages from this particualr account onto my palm pda mail program, no problem. Please help!
Thanks,
Dustin

Hi Dustin.
Other mail clients such as Thunderbird appear to be perfectly capable of downloading mail in circumstances that Mail has trouble with, but I don’t know whether it’s Mail’s fault or there is really something amiss at the server and those other mail clients are just more fault-tolerant.
Sometimes messages left on the server clog up the account there, or Mail chokes on a message it cannot download and that prevents it from downloading the rest as well. What are your Preferences > Accounts > Advanced > Remove copy from server settings for this account?
You may try first removing from the server messages that have already been downloaded. Assuming there is nothing wrong with the MessageUidsAlreadyDownloaded file (or if you’ve already re-created it), you can tell Mail to remove from the server all messages already downloaded by doing Preferences > Accounts > Advanced > Remove now. Alternatively, you may remove specific messages by other means (e.g. webmail or the Account Info window).
If removing already downloaded messages doesn’t work, the next thing to try would be removing messages that Mail hasn’t downloaded yet (you may want to try to download them with another mail client such as Thunderbird first, to avoid losing them). In particular, try removing the first message that Mail appears to be choking on. Actually, if there is a message on the server that Mail has trouble with, you may be able to identify it in the Account Info window. Don’t assume that it’s junk just because Mail doesn’t display it properly in that window, though. Try looking at its contents by other means (e.g. webmail) before removing it from the server.

When I open Thunderbird it always ask mail server password required and than several times i have to enter password. I have 30 emails.

When I open Thunderbird it always ask mail server password required and than several times i have to enter password. I have 30 emails. They select email randomly.

Hey there Sharon47.
Couple of things that I see when I read this.
1 - If you have tried to reset your password (and it says that mail has been sent) my guess is that your spam or junk folder may have it on Gmail? That's assuming your old email account (earthlink) is still forwarding to your new (Gmail) account.
2 - Make sure your Firefox versions are up to date on the devices.
Also,
Here's a couple of support articles which may help you with syncing and
https://support.mozilla.org/en-US/kb/how-to-update-to-the-new-firefox-sync
https://support.mozilla.org/en-US/kb/ive-lost-my-firefox-sync-account-information
Hope this helps!

"mail has not been downloaded from the server" messages......

About 2 weeks ago I started seeing "mail has not been downloaded from the server" messages popping up when I attempt to both new mail and e-mails that I have already read. I usually don't have any problems when I first launch the program, but after a few minutes running I get this message when I try to open any e-mail.
The message from "---" <[email protected]> concerning “RE: S8-04 pps sample package” has not been downloaded from the server. You need to take this account online in order to download it.
I know that the program is running online because it continues to show me new e-mails that come in.
What should I do?

Your OS detail provided indicates you are running 10.4.7 and Sasso's OS detail provided is 10.3.9.
The MBOX Breaker script does not work with Tiger mailboxes which are different from the mailbox structure used with previous Mail.app versions and the link you provided includes instructions for Jaguar or Panther Mail, not Tiger Mail. And depending on the size of the mailbox with Jaguar or Panther Mail, the MBOX Breaker Script may not be required.
If you are getting this message with Tiger Mail, this indicates you upgraded to Tiger from Jaguar or Panther on this Mac.
If so and if this Sent mailbox is for a POP type account, using the Finder go to Home > Library > Mail > this POP account named folder (named by the user name and incoming mail server for the account) > Sent Messages.mbox.
List all file and folder names available within the Sent Messages.mbox folder.

Why is Mail trying to connect to an unknown mail server (and how do I stop it)?

Hi - I'm worried that someone has hacked into my system so that it tries to connect to a fake mail server (perhaps to send spam)? I usually have the activity window open when Mail is running, and noticed that it was trying to connect to an unfamiliar mail server the other day - it was shown as an IP address whereas all the mail servers in my mail accounts have names rather than IP addresses ... so I copied the IP address down and searched for it (196.201.4.6), to find that it is run by malawi.net ... in Africa. I recently upgraded to Mac OS Lion, so initially I had figured that it was showing the mail server address differently, but I couldn't think of any reason that my email servers would be in Malawi!
By now I was getting worried: I checked all my mail accounts to be sure that something had not changed, and confirmed that none of my accounts used this mail server (or mentioned the IP address); and confirmed that the "Connecting to server "196.201.4.6"" activity message only appeared when I first reconnected to the internet (i.e. now when I manually clicked on "get mail") ... which suggests to me that it is a hidden process somewhere?
I don't have a virus checker, but downloaded ClamXav and ran a check on my user folders ... but found nothing.
Any thoughts on what this might be, or - if it is something malicious or externally controlled - how I can remove it?
Thanks - andy

Hi - "display remote images in HTML messages" was already deselected, so I don't think it was an HTML message connecting.
But your response made me wonder about whether it was something else in an old email that was causing the problem - I had a search and found some emails from back in 2006 (when I did some work in Malawi for CARE) that were from the mail server (mailer.malawi.net = 196.201.4.6) that has been appearing. However, I still don't understand why (six years later) Mail is now trying to connect to this server ... I'm pretty sure that it never used to happen (and I have been a full-time Mac user since 2003), as I always have the activity window open and would have noticed, so it is only since I upgraded to Lion last week that it started. Any thoughts? I could delete/archive the old emails, but I would really like to understand what is happening?
Thanks - andy

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?

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?

New iPad 2 always downloading previously deleted emails

I am using my Verizon.net POP3 email server. On iPad mail setup Incoming I have it set to delete from serer when removed from Inbox. My interpretation of that set-up is that any email I download, view and then delete (thereby removing it from my Inbox) should be deleted from the server by the iPad's OS. Those I don't delete should remain on the server. I also have an iPhone 3G running OS 4.x and it does not have this problem. Emails deleted on it are also deleted from the server so that they don't appear again when accessing new mail. The Mail settings otherwise appear identical to that of the new iPad.
This is NOT a POP3 vs. IMAP problem. It is an OS5.x problem as OS5.x is not handling the deleted emails by deleting them from the server. I want emails deleted from the iPad2 to delete from the server whereas those I leave in the iPad 2 mailbox I want to stay on the server so that I can manage those from my Win7 PC using Outlook 2010.
MBfromPlano

THANK YOU! Great solution!
Jerry
It looks like you still have your emails stored on the mail server from your Internet Service Provider. When you update to ios5, it wipes out the emails on your devices. Then when you go into the mail tools, it pulls the emails off the server again. Very annoying, I agree.
Best thing is to delete unwanted emails off the server, likely using a web based email tool from your ISP (eg Webmail from Time Warner, etc).
Hope this helps.

Need to have mail1 play nice with upstream mail server....

Switched to new mail server and hitting a problem. We have a debian linux box doing SPAM filtering further upstream from the mail server and then sending down to the new leopard mail1 box.
On the debian box we're seeing:
2009-04-03 09:14:08 H=216-174-222-148.atgi.net (email.wdcsc.org) [216.174.222.148] F=<[email protected]> temporarily rejected RCPT <[email protected]>: remote host address is the local host
2009-04-03 09:14:08 1Lpfar-0004fh-Ku ** [email protected] R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<[email protected]>: host nescosrv.nesco.ee [194.204.28.195]: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in local recipient table
And mail isn't piping thru to the mail1 box. Here's the main.cf
sh-3.2# cat main.cf
# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.
# SOFT BOUNCE
# The soft_bounce parameter provides a limited safety net for
# testing. When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#soft_bounce = no
# LOCAL PATHNAME INFORMATION
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
queue_directory = /private/var/spool/postfix
# The command_directory parameter specifies the location of all
# postXXX commands.
command_directory = /usr/sbin
# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
daemon_directory = /usr/libexec/postfix
# QUEUE AND PROCESS OWNERSHIP
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes. Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM. In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
mail_owner = _postfix
# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#default_privs = nobody
# INTERNET HOST AND DOMAIN NAMES
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld
# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#mydomain = domain.tld
# SENDING MAIL
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# [email protected].
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#myorigin = $myhostname
#myorigin = $mydomain
# RECEIVING MAIL
# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on. By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
# Note: you need to stop/start Postfix when this parameter changes.
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4
# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain.
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
# mail.$mydomain, www.$mydomain, ftp.$mydomain
# REJECTING MAIL FOR UNKNOWN LOCAL USERS
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
# - You define $mydestination domain recipients in files other than
# /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
# For example, you define $mydestination domain recipients in
# the $virtual_mailbox_maps files.
# - You redefine the local delivery agent in master.cf.
# - You redefine the "local_transport" setting in main.cf.
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
# feature of the Postfix local delivery agent (see local(8)).
# Details are described in the LOCAL_RECIPIENT_README file.
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a [email protected] address.
#local_recipient_maps = unix:passwd.byname $alias_maps
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =
# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
unknown_local_recipient_reject_code = 550
# TRUST AND RELAY CONTROL
# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix. See the smtpd_recipient_restrictions parameter
# in postconf(5).
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network. Instead, specify an explicit
# mynetworks list by hand, as described below.
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host
# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table
# The relay_domains parameter restricts what destinations this system will
# relay mail to. See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
# subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace. Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#relay_domains = $mydestination
# INTERNET OR INTRANET
# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
# If you're connected via UUCP, see also the default_transport parameter.
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]
# REJECTING UNKNOWN RELAY USERS
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a [email protected] address.
#relay_recipient_maps = hash:/etc/postfix/relay_recipients
# INPUT RATE CONTROL
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# Specify 0 to disable the feature. Valid delays are 0..10.
#in_flow_delay = 1s
# ADDRESS REWRITING
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.
# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.
# "USER HAS MOVED" BOUNCE MESSAGES
# See the discussion in the ADDRESS_REWRITING_README document.
# TRANSPORT MAP
# See the discussion in the ADDRESS_REWRITING_README document.
# ALIAS DATABASE
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
# It will take a minute or so before changes become visible. Use
# "postfix reload" to eliminate the delay.
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases
# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi". This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#recipient_delimiter = +
# DELIVERY TO MAILBOX
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user. Specify
# "Maildir/" for qmail-style delivery (the / is required).
#home_mailbox = Mailbox
#home_mailbox = Maildir/
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail
# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception: delivery for root is done as $default_user.
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus
# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf. The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =
# The luser_relay parameter specifies an optional destination address
# for unknown recipients. By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
# luser_relay works only for the default Postfix local delivery agent.
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for
# non-UNIX accounts with "User unknown in local recipient table".
#luser_relay = [email protected]
#luser_relay = [email protected]
#luser_relay = admin+$local
# JUNK MAIL CONTROLS
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.
# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
# For details, see "man header_checks".
#header_checks = regexp:/etc/postfix/header_checks
# FAST ETRN SERVICE
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
#fast_flush_domains = $relay_domains
# SHOW SOFTWARE VERSION OR NOT
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)
# PARALLEL DELIVERY TO THE SAME DESTINATION
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter. The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.
#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20
# DEBUGGING CONTROL
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
debug_peer_level = 2
# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain
# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
# debugger_command =
# PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
# echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
# >$config_directory/$process_name.$process_id.log & sleep 5
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
# debugger_command =
# PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
# -dmS $process_name gdb $daemon_directory/$process_name
# $process_id & sleep 1
# INSTALL-TIME CONFIGURATION INFORMATION
# The following parameters are used when installing a new Postfix version.
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
sendmail_path = /usr/sbin/sendmail
# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
newaliases_path = /usr/bin/newaliases
# mailq_path: The full pathname of the Postfix mailq command. This
# is the Sendmail-compatible mail queue listing command.
mailq_path = /usr/bin/mailq
# setgid_group: The group for mail submission and queue management
# commands. This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
setgid_group = _postdrop
# html_directory: The location of the Postfix HTML documentation.
html_directory = no
# manpage_directory: The location of the Postfix on-line manual pages.
manpage_directory = /usr/share/man
# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
sample_directory = /usr/share/doc/postfix/examples
# readme_directory: The location of the Postfix README files.
readme_directory = /usr/share/doc/postfix
mydomain_fallback = localhost
message_size_limit = 52428800
myhostname = mail1.stanwood.wednet.edu
mailbox_transport = cyrus
mydomain = stanwood.wednet.edu
mailbox_size_limit = 0
enable_server_options = yes
inet_interfaces = all
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
smtpd_use_tls = yes
smtpd_enforce_tls = no
smtpd_tls_cert_file = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpd_tls_key_file = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpd_sasl_auth_enable = yes
smtpd_use_pw_server = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_pw_server_security_options = gssapi,cram-md5,login,plain
content_filter = smtp-amavis:[127.0.0.1]:10024
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
owner_request_special = no
recipient_delimiter = +
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
# 02/02/09 Server Checkup by Alex
bounce_queue_lifetime = 6h
delay_warning_time = 6h
maximal_queue_lifetime = 2d
# Topicdesk Frontline Defense
disable_vrfy_command = yes
smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_rbl_client zen.spamhaus.org, permit
smtpd_helo_required = yes
smtpd_helo_restrictions = permit_sasl_authenticated, permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access, reject_non_fqdn_hostname,reject_invalid_hostname, permit
smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_non_fqdn_sender, permit
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination,permit
smtpd_data_restrictions = permit_mynetworks, reject_unauth_pipelining, permit
virtual_transport = virtual
virtual_mailbox_domains =
sh-3.2#

Right, what was happening is that it was a big loop. We had to modify our DNS and some other settings on the spam bucket... but... wondering if there's another solution...
mail1:~ admin$ postconf -n
alias_maps = hash:/etc/aliases,hash:/var/mailman/data/aliases
bouncequeuelifetime = 6h
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
delaywarningtime = 6h
disablevrfycommand = yes
enableserveroptions = yes
html_directory = no
inet_interfaces = all
localrecipientmaps = proxy:unix:passwd.byname $alias_maps
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
maximalqueuelifetime = 2d
messagesizelimit = 52428800
mydestination = $myhostname,localhost.$mydomain,localhost,mail1.stanwood.wednet.edu,stanwood.we dnet.edu
mydomain = stanwood.wednet.edu
mydomain_fallback = localhost
myhostname = mail1.stanwood.wednet.edu
mynetworks = 127.0.0.0/8,172.16.0.0/17,169.204.240.0/25,172.29.1.22,169.204.240.2
newaliases_path = /usr/bin/newaliases
ownerrequestspecial = no
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
recipient_delimiter = +
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdclientrestrictions = permitsaslauthenticated, permit_mynetworks, rejectrblclient zen.spamhaus.org, permit
smtpddatarestrictions = permit_mynetworks, rejectunauthpipelining, permit
smtpdenforcetls = no
smtpdhelorequired = yes
smtpdhelorestrictions = permitsaslauthenticated, permit_mynetworks, checkheloaccess hash:/etc/postfix/helo_access, rejectnon_fqdn_hostname,reject_invalidhostname, permit
smtpdpw_server_securityoptions = gssapi,cram-md5,login,plain
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpdsenderrestrictions = permitsaslauthenticated, permit_mynetworks, rejectnon_fqdnsender, permit
smtpdtls_certfile = /etc/certificates/mail1.stanwood.wednet.edu.crt
smtpdtls_keyfile = /etc/certificates/mail1.stanwood.wednet.edu.key
smtpduse_pwserver = yes
smtpdusetls = yes
unknownlocal_recipient_rejectcode = 550
virtualmailboxdomains =
virtual_transport = virtual
mail1:~ admin$

TROUBLESHOOTING TIPS RE: iCLOUD MAIL SERVER DROPOUT

Here's what I learned throughout this and I will post a discussion in a separate thread for the rest of the folk out there.
MYTHS AND FACTS RE: iCLOUD MAIL SERVER DROPOUT- WHAT I'VE LEARNED
Hopefully this troubleshooting helps everyone that has had or having issues, for now and for the future...
Firstly, the Apple system status is a bit of a myth. Because it is a global community of people using iCloud, it does not always update in real time. The Apple techs check this when there is issues, as do the public, so odds are unless every single person is having issues around the globe, then it won't reflect an issue. http://www.apple.com/au/support/systemstatus/
Apple technicians work in territories. For example, I live in Australia so I had to deal with a tech supervisor who looks after Australasia and who is based in Singapore. They don't get a notification if a group of people in Canada are having problems, even if they are identical to mine, unless as above, the whole world is having issues.
CHECK THESE FORUMS as a first step measure to work out if the problem seems to be just you and your account, or a wider community. Particularly before you make any major change to your email accounts, passwords, computers or phones.
If you get an issue in the next week or so (and keep in mind for the future) Error Message: "MY NAME" returned the error "[AUTHENTICATIONFAILED] Authentication failed." Your username/password or security settings may be incorrect. Would you like to try re-entering your password?" and this happens multiple times when you know the password is correct, then odds are that the server is down and you are best to wait it out. Try checking your mail via iCloud to test. If you can send it through there, odds are that the glitch has nothing to do with your password or issues with your account and rather than make changes, try and wait it out.
If all of your folders in your email disappear, if they are IMAP folders, then log into iCloud mail in your web browser to check that they are still there. It just means that your mail client (Mac Mail, Outlook for Mac etc) can't access the IMAP folders via the server. Don't panic until they are gone from every device you use your email on.
Be wary of deleting ANYTHING from your computer unless you are backing it up first. For example, I had a tech guy on the first day of the server drop out, who gave me the wrong advice of deleting EVERYTHING from my keychain. This resulted in me having massive security issues for web browsers and thus, I couldn't log into my iCloud mail in my browser. Not only did I have to re-install my OS Maverick to fix it (which took 10 hours) but I could have muddled through this mess by continuing to work using web mail.
If everyone seems to be having a mail server problem based on online community discussions, then you are not alone and TELL your Apple tech this. Send copies of the links to the various conversations. Push them (nicely) to investigate internally what is going on and don't let them rely on the System support status. It also helps to put in a report to Apple down the track.
Make sure that you can get a copy of Apple tech guys email address. Thankfully, even though I was on the phone to them for in excess of 7 hours over the past two days, I could update my guy via email and also send him screen shots of things that did or didn't work using my iPhone. We would keep in contact and all I would have to do is send him an email and he would call me back straight away. No holding or dealing with any call centre issues, which is probably the only reason why I didn't lose my cool too much.
If you can get into your iCloud through your web browser, you have the options under the inbox and then the little wheel thing down the bottom (preferences) to put a vacation message, like an out of office. Put that on and explain you are having email issues and give another email address or your contact number. At least the people that you need to contact will know that things could get lost in cyberspace. I wish I had of known this earlier.
You can also forward emails emails to another email address under preferences. Also very handy.
Become friends with your tech guy rather than enemies. If you don't feel like your tech guy knows what he's talking about, politely request to speak to a supervisor. I would be having a nervous breakdown right now (small business owner, lost two days of billable hours so I am financially behind) if I didn't have a good relationship with the guy that has been helping me. We are a good team, with me updating him with the information, via these forums, to find a proper solution to the issue and to rectify the wrong information I was given by the previous Apple tech guy I spoke to.
Ask them to replicate your issue on their side of the fence to troubleshoot. For example, my tech guy Levi replicated my issue with websites by intentially removing the system certificate from his computer and he realised that was what the problem was, and thus he could quickly find out how to fix it.
Back up your stuff regularly. It might be annoying but it is peace of mind if know you are only going to lose a minimum of a week's worth of stuff.
Apple has an engineering team and tech guys raise 'tickets' to them with information on what has happened to their clients. I don't know much about this but I would assume it is having the engineering team investigate to stop this happening in future. They can only work with the feedback they get I suppose. I would also suggest doing the Apple Care survey so they also get feedback. We need to explain to them that we are asking for communication first and foremost - whilst it is inconvenient, if we all knew when and where they would be doing server upgrades (which the rumours indicate that this is what happened) then I don't feel everyone would be so frustrated.
Using your computer is like raising a child - you know when something is not right, even if you are not experienced at it yet. Sure, you may not know the lingo but trust your instincts and tell your tech guy. I have learned more in the past two days about computers and Mac's than ever before and I know when I can confidentially say that strange things were happening to my Mac and where Apple went wrong in guiding me. Don't always take a blanket or easy explanation if you don't think it is right; odds are it will result in making changes to your product that do more harm than good.
Keep a record of notes of how much time you have spent on the issue (including phone calls to Apple), what they have told you to do and at what time, changes to passwords, troubleshooting tips and the contact details (and reference numbers) of who you speak to. I'm not sure if Apple provides compensation for these issues or anything along these lines, but I certainly will be informing them so they can try and better their service to me in the future.
Anyway, I hope that helps everyone a bit - these are just things that I have learned and if anyone else has any tips please feel free to add them.

Tried port 465 but it wouldn't work.
Went to our help desk and here's the reply I got (paraphrased slightly cuz the person at the help desk was trying hard to be helpful and I don't want to get him/her in trouble):
I presented this question to the university team and then waited for a long time to get the following reply:
we do not allow relay from non-university IP addresses.
port 25 for smtp is a standard worldwide.
For the most part, that went right over my head and didn’t answer anything, but I hope it means something to you.
I called him to get more clarification, but all I really got out of it was that, if you don’t use exchange which is secure via port 443, then your other option is to use smtp. And then he said something about how relay, iron ports, and authenticated accounts work together to make it secure. I know it makes me sound a lot more inept than I am, but all that made little sense to me. What I gather, is… that by selecting SSL when configuring your client, it makes it so that your login info and mail content is safe. Sorry, I can’t provide a more cohesive and comprehensive explanation, but I think the bottom line is that they have combined a non-secure protocol with other stuff to make it secure.
So, I'm hoping that checking SSL and using port 25 somehow solves the problem to the satisfaction of our IT professionals at the University ...
Again, thanks for taking the time to educate the rest of us!

Mail server is always downloading at 800K

Similar Messages

Maybe you are looking for