Mail not saving changes in Mailbox Behaviors

For one of my accounts since the upgrade to Mavericks when I enter the Mailbox Behaviors section, I found that Drafts, Junk and the one under Trash named Store Deleted messages on the server is checked.
I uncheck them because I doon't want them checked. I Save the changes I made then go back to that account and the same ones I just unchecked are now checked again. Its not saving what I just unchecked.
What the heck is wrong?
Also noticed that in OSX 10.8 I could drag all my email accounts to a different order than the way they are now listed. Can't do that now.

Thanks for discovering this issue being connected to drafts. I have trouble with this for a couple of months as well.
Since you assume it to be connected to "drafts", I suggest to deselect "Store draft messages on the server" for your IMAP-Account. I just did this for myself, to see if it helps, and can't give you results yet. Maybe you just wanna try simultaneously. I guess, the reason for our problem could me some messy communication between Mail and the server, where one party get's confused.
Greetings
Paul

Similar Messages

  • IDVD 06 not saving changes?

    Greetings. I teach an adult ed class in iLife. Unfortunately, the lab has old single 533 G4s. When we use iDVD 06, the program is not saving changes made in the different drop zones, etc. We place elements in drops zones, tell the program to save, quit and relaunch...nothing saved.
    This problem was repeated by a student on his G5 at home.
    Any ideas?
    Thanks.
    Michael Colin
    Mac G4 Single 533   Mac OS X (10.4.4)   Problem on G4 and G5

    Hw much free space is left on the macs?
    Plenty. These are very small projects we're working on.
    Thanks for the response.
    Michael
    Mac G4 Dual 533   Mac OS X (10.3.9)  

  • Stocks App not saving changes

    My stocks app is not saving changes no matter what changes I make.  After making a change, I'll exit the app, re-enter and it defaults back to a whole bunch of stuff I didn't add.
    Can someone help me with this, I'm not sure where to even start!

    Nadia Bielawa wrote:
    This did not help at all.  I'm not about to restore my iPhone and set everything up again, there must be a simpler solution. 
    Th simple solution is restart.
    If that fails,  thenreset.
    If that fails, then restore from backup.
    If that fails, then restore as new.
    If that fails then make an appointment at the genius bar.

  • Changes to mailbox behaviors not being saved.

    Hey guys,
    I have two Google accounts set up on Apple Mail. When I try to edit the Mailbox Behaviors (under Preferences>Accounts>Mailbox Behaviors) they are never saved. My steps are:
    1. Go to Mailbox Behaviors
    2. Uncheck Drafts & Sent
    3. Click the other account, choose another tab, or close preferences
    4. Dialog appears asking if I want to save the changes
    5. I choose to SAVE.
    6. Go back into Mailbox Behaviors - the changes were not saved (i.e. everything is still checked).
    Any ideas? I'm running 10.9 on a retina Macbook Pro.

    OK...my previous attempt didnt work as the settings came back after a full sync.  However, I found another thread that solved my problem.  Hope this helps!
    https://discussions.apple.com/thread/5468664?start=15&tstart=0
    Steve Rhyne Oakland, CA
    Re: Mavericks Mail app and Gmail Drafts folder 
    Oct 24, 2013 10:30 AM (in response to Igor D.)
    I had the same problem and it was causing dozens of versions of autosaved drafts to appear in my Trash. (Gmail autosaves drafts at the server level and trashes previous saves. The feature is not customizable.)
    This fixed it for me, at least for the time being:
    1) Quit Mail.app.
    2) Log into Gmail in your favorite web browser.
    3) Click on the gear menu and select "Settings".
    4) Click on the "Labels" tab.
    5) Under "System Labels", next to "Drafts", click on "show if unread" and uncheck the "Show in IMAP' box.
    Now disable "Store draft messages on the server":
    6) Launch Mail.app.
    7) Select Mail > Preferences...
    8) Click on the "Accounts" button in the toolbar.
    9) Click once on the account name and then click the "Mailbox Behaviors" tab.
    10) Uncheck the "Store draft messages on the server" box.
    11) Close the window and opt to save your changes when prompted.
    A few other Gmail / Mavericks Mail.app discoveries:
    * You must enable the "Show in IMAP" option for the "All Mail" label in Gmail if you had it disabled before. (Google this tip for explanations and ramifications.)
    * Mail.app now seems to automatically map the Sent, Junk, Trash and Drafts folders, i.e. you can't use this menu command anymore: Mailbox > Use This Mailbox For > Drafts / Sent / Junk / Trash
    * I used to add the "[Gmail]" prefix under the "Advanced" tab of my mail account to eliminate it from the IMAP view, but it doesn't seem to be necessary any more, and might even have been causing some weirdness.

  • Send mail not saved

    I work with a couple of (imap) mail accounts. Receiving and sending mail is ok but the mail I send through those imap accounts is not saved in the directory sent items. Only the mail send by my apple account is saved.
    I don't how to fix this problem? (I've tried deleting the accounts and make new accounts).
    Neither Apple support or my ISP did not have a solution.
    Who can help
    mac book   Mac OS X (10.4)  

    I guess I figured it out. My settings were saving sent email to server (I was really convinced this was the right setting). By changing this setting my sent mail is saved in the sent directory.
    Thnx for setting my on the right track
    What are your Preferences > Accounts > Mailbox
    Behaviors > Sent settings?
    In the Finder, go to
    ~/Library/Mail/IMAP-username@mailserver/
    . With that folder open, do Edit > Select All
    (⌘A), then Edit > Copy (⌘C), and paste it
    in your reply to this post to let me see the names of
    the files and folders it contains -- you may disguise
    any mailbox names you wish to keep private.
    Note: For those not familiarized with the
    ~/ notation, it refers to the user’s home
    folder, i.e. ~/Library is the Library folder
    within the user’s home folder.
    mac book   Mac OS X (10.4)  

  • Mail not saving IMAP drafts or outgoing messages

    I've searched the HELP topics and have not seen how to solve this problem. I have multiple accounts set up in Mail; a couple are yahoo.com/sbcglobal.net accounts and a couple are through two different companies for which I work. Most of them are set up as POP accounts, and they are behaving properly. The problem is with the one that is set up as an IMAP account. It successfully sends and receives mail, but it will not save drafts or the outgoing mail. I realize I can blind-copy myself and have the messages saved as incoming, but I'd really like them saved as drafts and outgoing. Thanks for any advice!

    Hi Dantedelg,
    If you are having an issue with your MacBook Air's Mail application not saving the Sent mail, you may want to check your Mail Preferences under Accounts > your account > Mailbox Behaviors > Sent. What is the setting for Delete sent messages when: set to? You may wish to change this setting. See this article -
    Mail (Yosemite): Set up Mail with your email accounts
    Thanks for using Apple Support Communities.
    Best,
    Brett L 

  • Yahoo sent mail not saved to server when using Mail only.

    Why does my Yahoo sent mail not get saved to the server when I use Apple's Mail program? (I have it saved in settings to keep sent mail on server).  I can see it in my Sent mail folder on Apple Mail but not on the yahoo server.  It's an IMAP account and it works fine on my iPhone.
    I have tried changing the outgoing ports as well and erasing the account and reinstating it on the Mail program. No luck.

    NatMac:
    This worked for me:
    ernestobenedict London
    This solved my questionRe: Yahoo Mail folder behaviour with Apple Mail 5.0 
    Dec 8, 2011 5:14 PM (in response to ernestobenedict)
    I finally figured out how to fix this; under the mailbox menu there is an option to "use this mailbox for" that allowed me to select the Sent Items folder from my Yahoo IMAP list of folders and make it the default for sent items from the Mac OS X mail software! "
    Thanks to ernestobenedict for this solution!!!

  • Mail not saving sent messages, not moving Junk messages

    Hi everyone, I'm having a bit of trouble with OS Mail. I've set it up to use an IMAP account, and have set my preferences such that Mail should save all my sent messages in the Sent folder (I assume the Sent folder on my computer, not the one on my IMAP server). Regardless, neither my IMAP server's sent folder nor my computer's sent folder contain any messages that I've sent, and I have confirmed that these messages have in fact been received by the recipients (therefore successfully sent). I am unsure of how to resolve this issue, as there is no obvious setting change for me to persue. I just received this computer (new) a few days ago, so I wouldn't expect this problem to be due to disk maintenance/management, etc.
    Also, I have noticed that Junk messages remain highlighted and in my inbox. I changed my prefs to have these messages be placed in my Junk Mail folder. Mail asked me whether I wanted to apply that preference to older messages marked as junk that have yet to be put in the folder; I indicated yes. Nothing happened, and the Junk Mail folder remained empty (until I manually moved the messages to it). Any ideas?
    I have searched the forums for related issues and could only find problems that had an associated error message with it; my issue is different in that there are no error messages; Mail is simply ignoring my preferences. Thanks in advance,
    Vic

    In OS X Mail, this sent folder appears as a subdirectory
    (sub "mailbox"?) under my "Inbox" mailbox along with
    other folders that are mapped on my IMAP account.
    This means you haven't set up your account properly. You probably should set Preferences > Accounts > Advanced > IMAP Path Prefix to INBOX, or something like that.
    After putting the right string in the IMAP Path Prefix field, either the IMAP folders will appear somewhere else in Mail (i.e. not as subfolders of Inbox), or your problem will have already been fixed. Let me know what happens.
    I should probably mention (just realized) that in my
    account settings, my outgoing SMTP server is set to
    be my ISP's server (which is different from my IMAP
    provider).
    I wonder if, by selecting "save messages on server"
    I am saving these messages somewhere on my ISP?
    Mail should still save the sent messages where you've told it to. It's Mail, not the SMTP server, that stores the sent messages. The SMTP server has no bearing on this, but it was a good idea to consider that possibility, nevertheless.
    When I uncheck this option, perhaps my mail will
    be stored on my local computer instead?
    Yes, that's what would happen, but don't uncheck that option if you really want your sent messages to be stored on the IMAP server, or do it temporarily, so that Mail does at least save them somewhere until we fix the problem, but I believe I already know what the problem is.

  • Mail Not Saving Passwords

    OK...here's my system config: MacBook Pro, 17" (MacBookPro2,1), OS X 10.4.10 (8R2232). So running the latest version of Mail.
    Please note that my Jabber account in iChat is exibiting this exact behavior.
    Basically, every time I start mail, it asks me for the password for each of my mail accounts. This has happened before, so at first, I thought nothing of it. Then, when I realized that it was every single time, I looked in prefs and realized that the password field was blank for each account. So, doing what I thought made sense, I went through each account, added the password, and saved it.
    Then, the next time I launched mail, it did the sam thing: asked me for the password for each account. I looked, and low and behold, the fields were blank again. So, I added the password to one, saved it, then clicked on it again, and yes, again, it was blank. So basically, Mail is not saving the passwords to my accounts. All other information can be changed and it will save properly.
    I went to Keychain Access and did a repair on the Keychain, and it fixed nothing. Is this a Keychain corruption? Do I have to delete my entire Keychain to fix this problem?
    Help!

    Post your problem here to get a better assistance:
    http://answers.microsoft.com/en-us/outlook_com/forum
    S.Sengupta, Windows Entertainment and Connected Home MVP

  • Sent Messages are not saved in Sent Mailbox

    It was working correctly but suddenly all my sent messages are not saved in the Sent Mailbox. I follow all the Mail Help instructions but nothing seems to work. Hope that someone can help me. I asked for help on december 14 but it was not helpful

    The mailboxes drawer contains all mailboxes under In, Drafts, Sent, Trash and Junk (if you have Junk Mail set to automatic).
    If you have a .Mac or IMAP type account, you also have an account named icon for the .Mac or IMAP type account at the bottom of the mailboxes drawer. It is named by the Account Description you provided/entered for the account under the Account Information tab for the account preferences.
    If you select save Sent messages on the server for a .Mac or IMAP type account, the account's Sent mailbox will be available under the account named icon in the mailboxes drawer along with all other server stored mailboxes.
    To open the account named icon for your .Mac account to reveal the server stored mailboxes including the account's Sent mailbox, select the black triangle beside your .Mac account icon in the mailboxes drawer pointing it down.
    Select the account's Sent mailbox and at the menu bar, go to Mailbox > Use This Mailbox For and select Sent.
    If you deselect store Sent messages on the server for the account preferences, the account's Sent mailbox will be available under Sent in the mailboxes drawer and you can't use "Use This Mailbox For" for mailboxes stored locally on the hard drive. It can only be used for .Mac or IMAP type account mailboxes that are stored on the server.

  • Lion Server postfix mail not being delivered to mailboxes. "SMTP restriction `reject_invalid_helo_hostname' after `permit' is ignored" and "connect to private/policy: Connection refused" errors.

    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(5

    Ok 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.

  • Sent messages not saved in sent mailbox

    Lately some iCloud sent messages are not saved in the sent mailbox.  this is an intermitant problem.  sometimes msgs go to the outbox even though mail is on line; when they are eventually sent sometimes they do not make it to the sent mailbox.  I call the recipient and the msg has actually been received.  The lost messages do not appear in iCloud.  Rebuild does not help.  any suggestions?

    Tks for your answer. I have a .Mac account and in already try in Preferences-Accounts- and I only see three tabs: " Account Information ", " Mailboxes Behaivor " and " Advanced ". I don´t see the " Special Mailboxes " tab that you mention and I have also read about it. In Mailboxes Behaivor I can choose the option " Store sent messages on the server " and the Delete sent messages option is in " Never". If I choose not to Store sent messages on the server, nothing seems to happen. I hope you can help me with this information and I want to thank you again

  • Mail not saving sent messages

    I've noticed that Mail is not saving my sent messages. I started to notice this yesterday. It's very erratic though. Sometimes it does, sometimes it doesn't. I have the option selected in preferences to Store Sent Messages on the Server (my .mac account).
    Any idea what is going on? I even checked my .mac Sent Mesages folder using WebMail and they're not there either.
    John
    PowerMac G5 Dual 2.3   Mac OS X (10.4.2)  

    You're welcome.
    With a .Mac or IMAP type account, you can save Drafts, Sent, Trash and Junk messages on the server instead of locally on the hard drive.
    Messages in a .Mac or IMAP type account's Inbox mailbox remain on the server until deleted from the account's Inbox mailbox or moved from the Inbox mailbox to a user created "On My Mac" mailbox or deleted from the server using webmail access.
    You can also create additional mailboxes that will be stored on the server.
    Messages in the account's Inbox mailbox and in any other mailboxes stored on the server are synchronized with the Mail.app and with other email clients.
    With POP type accounts, received/incoming messages are downloaded by the Mail.app and by other email clients. You can choose when messages are deleted from the server when downloaded by the Mail.app and by other email clients but you cannot store Drafts, Sent, Trash or Junk messages on the server or create any additional mailboxes that are stored on the server.
    A .Mac or IMAP type account is beneficial for those who access their email account with multiple computers and want to keep all mailboxes for the account synchronized on each computer.
    For example, you have a Desktop at work but also travel with an iBook or PowerBook. If you have a .Mac or IMAP type account and select save Drafts, Sent, Trash and Junk messages on the server in Mail on both Macs, all mailboxes for the account will be kept synchronized in Mail on both Macs. Messages sent with the iBook when traveling will be available on the Desktop Mac in the office and vice-versa.

  • Yosemite Mail mail not saving preferences

    OS X 10.10, Mail 8.0
    I have several mail accounts set up, a mix of POP and IMAP
    One IMAP account does not use secure authentication.
    If I set the preferences for the account under the Advanced tab, and tick 'Allow insecure authentication', then save preferences, I can send mail to the account.
    However if I return to Mail after 5 minutes or so the preference has changed back to disallow insecure authentication, and that mail account no loner works. I get a message:
    "Mail cannot send your password securely to the server. You can remove this restriction in the Accounts preferences by setting “Allow insecure authentication”, which could put your password at risk."
    I have a POP account for a different email address with the same provider, and the preference to allow insecure authentication is saved.
    I have tried deleting the account and setting it ip again, but the IMAP presence to use insecure authentication is still not saved.

    I have this issue as well.  This includes the inability of font preferences to stick, and the toolbar changes to be retained.

  • Crystal Reports 8.5 not saving changes to report criteria

    When I use the formula editor to add new criteria to the report criteria formula, the changes are not saved when the report is closed.  It doesn't seem to matter how I exit the formula editor, and I've even tried "save as" and saving the report to a new name prior to closing.  When I reopen the report, the changes are gone.
    Sometimes the changes don't even last that long - they often disappear while doing a refresh. 
    Are there and known bugs that I haven't found - or better yet, any solutions?

    Hi Roberta.
    I've had this happen a few times as well.  Usually though a message will come up at some point in time saying.  If the report is locked when you open it, either because someone else has the same file opened in Crystal or if you open the report from an e-mail attachement, a message will come up saying something in the lines of the report cannot be saved and it must be saved to a new file. 
    When you do the Save As, where are you saving it to?  Try creating a new folder and saving it to that folder.  You should have full permissions to the new folder and I'm hoping it will save.  I just want to eliminate any problems with permissions.  After you save the file, check the properties of the file.  Did the file's date and time update or does it still have the original date? 
    When you open the report in Crystal, go to File on the menu bar and make sure Save Data with Report is not checked.  Make your changes and rerun the report and save it again.  See if that helps. 
    These are the two common problems I've had when this happens to me. 
    Hope this helps,
    Brian

Maybe you are looking for