Mail not finding new imap mailboxes
Hi
I have multiple devices Mac, iPhone, iPad and run multiple email accounts. If I create a new mailbox folder on any device other than my MacBook Pro then the mail app on that won't see the new folder - and I can't find a way of making it do so short of completely removing the mail account and adding it. Quitiing mail, asking it sync etc does nothing.
On other apps, e.g. Thunderbird, you can go to Subscribe to find folders that haven't been picked up
I am in OS X 10.9.2 and Mail 7.2 (1874)
Thanks
Similar issue here I think. Certainly started about the same time.
I have multiple (IMAP) emal accounts.
All email accounts with my one host have the same issue -- after tunring on the computer, or after a long sleep (don't know exact cut-off, but shorter sleeps don't seem to cause the issue) it can take a long time before all the error symbols disappear (sometimes the account will still receive, even before the error symbol goes away).
Our accounts with my ISP (also IMAP) work as expected, as do our GMAIL accounts.
These same symptoms occur on all 3 of our macs (all running Lion), and all worked fine before sometime in March. The same accounts all work fine on our iOS devices.
Keep wishing the issue will suddenly go away (like it suddenly appeared).
Similar Messages
-
Mail not showing new messages on 10.8.3
Mail not showing new messages on 10.8.3, but messages show just fine on iPhone. Nothing changed to make this happen, not sure where to start. Thanks.
Back up all data.
Select the problem mailbox in the mailbox list, then select
Mailbox ▹ Rebuild
from the menu bar. -
Hi all, I am in full migration from Exchange 2007 to Exchange 2013 and everything went correctly.
I have migrated several mailboxes and are working well. But a few days ago, when I try to migrate a mailbox I get the following error and can not migrate:
"Could not find a valid mailbox migration for this organization"
Do you know that you can be?
regards
Microsoft Certified IT Professional Server AdministratorHi,
From your description, the issue should be related to the migration mailbox. I recommend you check if the following account is existed in ADUC.
Migration.8f3e7716-2011-43e4-96b1-aba62d229136
If this account does not exist, you need to run setup /prepareAD and then enable this migration mailbox to check the result.
Hope this can be helpful to you.
Best regards,
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Amy Wang
TechNet Community Support -
All, Im stumped. In fact I have been on the phone with Apple Support and this has been escalated to the top engineers, as I think its got them too..
Anyway, here is my problem..
I'm running an Mac Mini with OS X 10.7.4 Server. I have had mail running on it for 2 months or so, without any issues. The mail was actually migrated from 10.6 in March, and It actually went smoothly. I have 3 domains which all recieve mail and they all work (or did up until 2 weeks ago)..
So the story is this.. I can send mail from my domains, without issue. imap and dovecot must be working.. cause all the stored mail, can be read with the mail IMAP client.. I can even transfer mail messages from one mailbox to another with Mail client. Sending mail is a breeze, it still works and the recipients still recieve their mail. But I noticed I wasnt getting any mail at all from those mailboxes... no mail, no spam, nothing.. which is unusal. I fired up Server admin and checked out the SMTP log, and this is what it showed for every email recieved: (xxxxxx is just me hiding sensitive info)
Jul 21 14:25:20 xxxxxxxx postfix/postscreen[65857]: CONNECT from [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/postscreen[65857]: PASS OLD [17.158.233.225]:41909
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: connect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Jul 21 14:25:26 xxxxxxxx postfix/smtpd[65858]: warning: restriction `reject_invalid_helo_hostname' after `permit' is ignored
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:27 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: connect to private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: warning: problem talking to server private/policy: Connection refused
Jul 21 14:25:28 xxxxxxxx postfix/smtpd[65858]: NOQUEUE: reject: RCPT from nk11p03mm-asmtp994.mac.com[17.158.233.225]: 451 4.3.5 Server configuration problem; from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<nk11p99mm-asmtpout004.mac.com>
Jul 21 14:25:28 azathoth postfix/smtpd[65858]: disconnect from nk11p03mm-asmtp994.mac.com[17.158.233.225]
Ok, now what is odd, is these rejected messages are not even appearing in the mail queue in Server Admin. I have no idea why there are not being delivered
Ive checked my postfix main.cf file and master.cf files they both look ok.. Ive even replaced them with the main.cf.defualt.10.7 and master.cf.default.10.7 files and to no avail... same problem..
So in summary
I can send mail out
IMAP is working on the client end (thus dovecot is) exsisting stored emails can be accessed, read, moved unread etc..
mail is coming into the sever, but its being rejected. there is NO rejection email sent back to the sender.
mail is recieved by postfix, but cyrus isnt doing anything with it.. I have no idea where it goes...
Could anyone shed light on this...
my main.cf file:
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - 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,
azathoth:postfix root#
azathoth:postfix root# less main.cf
azathoth:postfix root# more main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
# The general format of each line is: parameter = value. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
# NOTE - 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, $mydomain,
# 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(5Ok 1st one. The warning restriction message relates to this line in main.cf:
smtpd_helo_restrictions = permit_sasl_authenticated permit_mynetworks check_helo_access hash:/etc/postfix/helo_access reject_non_fqdn_hostname reject_invalid_hostname permit reject_invalid_helo_hostname
The last reject occurs after the single word "permit" and is ignored.
However, that's not the problem.
I'm not exactly sure what's happening, but this might be a clue.
It would appear that either postfix is not being able to create the socket for private/policy or it's somehow created with the wrong permissions. You might need to ramp up the debug level to get a better idea.
You could check if it's being created by "netstat -a | grep private/policy" in terminal.
My guess is that it's not being created because there is no setup statement in your master.cf file, but I don't understand why postfix would be looking for it if it isn't set up. Private/policy I think relates to grey listing. Maybe gives you a hint. -
Mail not loading new gmail message
I have Apple Mail 4.3 and since 22 November it is not loading new gmail messages. New messages are appearing in gmail and iphone, but not in Mail - any ideas why this would be
I'm facing the same problem since 27 Dec 2010, can't find and fix for this problem.
I can download other mail accounts except imap.gmail.com, it just show loading and nothing happen, and it also choke up almost all my internet bandwidth.
I gave up and switched to outlook for mac and no such problem.
Hope apple can look into this problem and I'm sure there are more out there having same issue. -
Mavericks Mail not sync'ing IMAP act. (Not GMail)
I have been waiting silently to see if a fix would come on its own, but none yet. Ever since upgrading to Mavericks, Mail.app does NOT sync my IMAP accounts correctly. I have gone so far as to remove and re-add the accounts numerous times... no change. The recent "update" that was supposed to address Gmail issues had no affect on my sync'ing issues either. As others have posted, I basically have to quit and re-launch mail for it to correctly show what is on the mail server. All of my iDevices are working just fine - I can read or move an email, and all my iDevices show it correctly... but when I return to my Mac - some show as unread - some messages that I moved or deleted are still THERE (unread), etc.
Once I quit and relaunch, the inbox displays correctly - but there is no way (that I can find) to force the inbox to "refresh" correctly while the app is open. "Getting new" messages does nothing to help. Has anyone found a solution or work-around...? or is this just a "sit back and wait for Apple to fix" kind of problem...?
Thanks,
SFI have the same problem. The recent Mavericks update fixed the original Gmail problem (of not being able to get rid of mail from the in box), but this problem is there and very frustrating. Exactly the same as the original post - Mail on my Mac does not reflect the emails filed, moved, deleted etc from my iPad or iPhone. Gmail, iPad and iPhone are all in perfect sync, but the Mac is not.
The only way to force the Mac into line is to QUIT Mail and relaunch.
(By the way, I don't have any anti-virus on my machine, so it's nothing to do with that - its a Mavericks issue).
I have been looking at alternative mail clients as I have now lost all faith in Apple Mail. (I am committed to IMAP and Gmail, on 3 different email accounts).
Yersterday I tried Outlook (as I happen to have a copy with Office-2011 for Mac). I liked it apart from the fact that it won't work with iCloud contacts... so its no good for me.
I'm looking at Mailplane now.... doesn't seem to be available via App store, but I'm going to try a free 15 day trial I found online. I'd say that's how long Apple has to fix this problem as far as I'm concerned. -
As of about 4 days ago my Mail app is not displaying new e-mails. It says '19 incoming messages' but they never appear. I have tried:
- Replacing mail.plist with older version from time machine
- Rebuilding mailboxes
- Asking my web hosts if there is any problem their end - no problems there.
- Checked the 'get account info' box which displays the 19 messages with 'unknown sender' still on the server.
Any other ideas anyone?Hello jimjazzuk,
Thank you for the details of the issue you are experiencing with email on your MacBook Pro. You have already taken some good steps to isolate the issue to your MacBook Pro. I recommend following the steps in the following article to continue isolating and troubleshooting the issue you are experiencing with Mail:
OS X Mail: Troubleshooting sending and receiving email messages
http://support.apple.com/kb/ts3276
Thank you for using Apple Support Communities.
Best,
Sheila M. -
IMAP question - Sent mail not synching to IMAP server
I have several new IMAP accounts (not .mac). They sync fine for received mail. They also sync sent mail fine when I use Thunderbird. But When I use Mail (X.3 - panther), even though I have the box checked to store sent mail on the server, it does not.
--> no sent mail folder is created.
--> mail sent from apple mail does nto show up in Thunderbird
Is this a known bug?
How can I work around it?
Is it fixed in Tiger?
Thanks, I have searched the archives. no luck.
Grantno messages are ever added to it when I send from Apple Mail. The one email I sent from thunderbird does show up (in both). In another account, the one email I sent from webmail at the Madrid airport shows up, but not the hundreds I have sent in the interim.
Sorry about the confusion.
Grant -
I have had my work account setup through Mail for almost 2 years without a problem. Today it stopped retrieving new emails. I went to Window...Connection Doctor and Connection Status is green and both for incoming and outgoing it shows green. I can send emails fine, but it won't retrieve new emails that I have received. I also get emails to this account through my phone and it is getting new incoming emails.
I have tried closing the app and restarting, doesn't work.
I have tried restarting the OS, doesn't work.
I haven't changed any settings in the past day, so its not a settings issue. That is unless Mail is now changing settings on its own.
What else can I do to solve this?It does show in the bottom left that its connecting "Incoming messages..." and when it tries, it makes a tiny beep. Its not the "new email" sound, just a quiet, short beep. No idea what the sound means.
-
Mail not fetching new data every 15 with 3g turned off
I had to turn 3g off in order to improve my reception and battery life. It seems to help somewhat, however I notice that the Mail application does not fetch new mail every 15 minutes like its setup to do. It works fine in 3g mode, just doesnt do it while its on edge. (I think it also works ok on wifi.)
Perhaps your in an area with awesome 3g reception but really bad Edge. Weird huh.
-
"Faces" not finding new photo additions
I have added about 200 new photos to my Aperture library, edited them, and then gone to faces. For each face selected I get a short message that the program is looking for matches. However, it does not find any, despite the fact that all of the new photos are of my 5 grandkids, all of which have a Faces collection. How can I fix this? Thanks!
I do not work for apple and I don't know what algorithms they are using. However, I work in image processing and recognition and so I think I might add to the discussion.
Typically what is done is that you separate detection from recognition. There is a face detector that detects anything that looks like a face and a face recognizer which then tries to put a label on the face.
The detector really does two things: It finds all faces in each image and also determins their size and orientation. Usually this is done by locating both eyes. This means that only those faces are found where both eyes are visible. From the position of the eyes it can guess the size and orientation of the face.
The detector then rotates and scales the face as input to the face recognizer.
Typically, the detector is trained on faces only once and then shipped with the application. Adding more faces to the database does not improve the performance of the detector. It only improves the performance of the recognizer.
Note that his is the typical way things are done. This does not mean that apple is doing it a little bit differently.
Marcus -
Mac mail not refreshing new mail
Hey
Is anyone else having problems with mail not updating when new ones arrive? I have to hit "get mail" even though I have the preferences set to check for new mail every 5mins. I am running mail 2.1.1.
Can anyone assist?
Thanks!Hi G Money.
Go to Preferences > Accounts > Advanced. Is Include when automatically checking for new mail ON or OFF?
BTW, please put the right information in the Computer Model and Operating System fields on your My Settings’s profile (and click Save), so that this essential information automatically appears in all your posts — you cannot be running Mac OS X 10.4.1 if the version of Mail is 2.1.1. -
I use POP for Mail on my MacBook Pro. I want to be able to delete emails from my phone without deleting them from the server, so I use POP on my iPhone 5S, too.
After I finished setting up my email accounts, I noticed that after each account name, Settings says "Mail," rather than "Mail, Notes."
Will my Notes sync across devices with POP email setups?Yes, I am doing just that, but earlier when I would press START, it would give me the menu seen in the image above.
1] OVI by Nokia
2] Yahoo!
3] Gmail
4] Hotmail
.... etc.
Now I get only
1] Mail for Exchange
2] POP / IMAP
3] Lotus notes Traveler
No Yahoo, Gmail, options. So even if I fill the username and password, I can't download the mails. -
PSE 9 not finding new photos in files.
PSE 9 does not find the new photos that I add to my windows folders. Previously it had found the photos, showed me the thumbnails and then imported them. It no longer does this. I am using Vista.
This link will help you understand better:
http://helpx.adobe.com/elements-organizer/using/local-files-cds-dvds-video.html
Go to second option: Using watched folders (Windows only) -
Homesharing not finding new purchases
Homesharing worked as recent as 4/8/11. Today I can't get it to. my PC will check for purchases on the Mac, but will not find them. I have made sure that both computers has the most recent version of itunes. I have restarted both, and turned homeshareing on and off...many, many, many times.
Got anything else to try?Try playing one or more of the Purchased Songs within iTunes. That usually gets the process working after a computer authorization.
Then re-sync your iPod.
Best of Luck
Maybe you are looking for
-
Hello Adobe photoshop album can not open all the time aske me register and enter Unlock code . Thank you abdo magdy
-
Using a field value as subject in Email Submit - help
Hi there, I am new to the forums and very new to LiveCycle and XML and Java. All i need is some hopefully very simple help. I have a PDF form, and all i want is when i click the submit button it uses the value entered into the textbox called JobCode
-
Replaced 3com 3c905b with 3com905c -doesn't work
We replaced a 3com 3c905b with a 3c905c. I can seethe interface with ipconfig -a, and pinging itself says its alive, but nothing goes to the network. Anybody have any ideas? thanks - Greg
-
Last Software Inventory Date old
We a some machines where the Last Software Inventory date is very old but the HW Inventory date is current. Is there any step by step documentation on troubleshooting this type of problem?
-
How to Install AIR on Linux via SSH
How can I install AIR on a linux server via SSH? llama