Backup Mail Server

Hi,
I'm not sure if it's the right section of the forum but it seems to be the most appropriate.
My question is: It's possible to setup a mail server that downloads mail from different mail accounts (given by Isp) and store them.
I need this because the space in the mail account is ridicolous.
It's possible also to let users download email from this local server instead from the Internet?
Thanks
Asterhex

fukawi2 wrote:IIRC, fetchmail needs a local MTA (such as postfix) to deliver the mail to, so you would need postfix also. (I stand to be corrected)
Aha - I think that's where exim4 comes in on our network... We certainly don't have postfix installed, but we do have fetchmail fetching our mail. I have read somewhere that getmail is a lot easier to configure than fetchmail, so it is possible you don't need an MTA with getmail.
If the OP'er will be checking the mail only locally, there is not really a need for an IMAP or POP-server (like dovecot): most email clients can handle plain maildirs. I have no experience with this, so I don't know if this is a workable suggestion or not.
/EDIT: The getmail documentation states explicitly that it can deliver email locally to an mbox or maildir without the need of an MDA or MTA.
Last edited by zenlord (2010-09-30 09:09:05)

Similar Messages

  • Redundent mail server setup (backup mail server)

    i have been reading all the post of setting up a mackup postfix server. i have looked at the configuration files and have a second machine ready to be implemented but have some questions on how exactly the backup works. my current setup is:
    - xserve1 with 10.4.3 OD master running mail, web, dns, ichat, ftp, host name is mail.mydomain.com
    - xserve2 with 10.4.3 (i will make this replica) running web and backup dns
    - G4 466MHz with 10.4.3 Server running mail and web, host name is mail2.mydomain.com (this is to bemy postfix backup server)
    all 3 are behind a firewall with NAT. they have local LAN IPs with NAT to 3 separate WAN IPs and open ports for the needed services.
    my first question is: do i need to run dns as well on mail2.mydomain.com?
    while i understand that mail stays in the queue on the postfix backup, does that mean that while mail.mydomain.com (primary mail server) is down users will not be getting any mail? can the users actually login to the mail2.mydomain.com and if yes how do they authorize?
    should i keep mail2.mydomain.com as a standalone or make it part of the directory?
    any info is appreciated.
    thanks
    martin
    xserve G5   Mac OS X (10.4.3)  

    don't mail servers hold mail for days anyway and keep
    retrying and when our mail comes back up will get all
    the mail?
    Yes, they typically do (unless some braindead administrator has configured his server to try only for a few hours or so).
    i assume there is no difference if my
    backup mail server runs on 10.3.9 then?
    None whatsoever.
    - is there a practical way to set up a mail that
    clinets can login to and check mail while the primary
    server is down?
    Practical? No.
    can the backup server forward as well
    while it holds to the queue?
    Why would you want that? Where should it forward to if the primary is down? As soon as the primary is up, the secondary will forward to i.
    the last time i had some
    coruption and problems with reconstruct (which you
    helped me with), we were down for 24 hours. i am
    trying to avoid this. i have an image and i run
    mailbfr to backup i assume i can use that in case of
    harware failure or massive os corruption that may
    take hours to fix.
    If push comes to shove this may help. Although images are never too brilliant for mail services recovery.
    my problem is that if this happens
    during the week, during daytime we cannot really
    afford to be down at that time.
    This is really your call. Only you can decide how much money you want/need to throw at resilience. But if you decide you cannot afford more than an hour of downtime, you will need far more than an onsite secondary mx
    Alex

  • Mail server down

    assume i have one mail server and one backup mail server
    what can i do switch btw two servers if one down? I can't use ping method to check the mail server availablity....
    Any signal my program can get from improper work of mail server?

    public static boolean checkMailServer(){
              boolean flag = true;
              try{
              Transport transport = (HtmlEmail.session).getTransport("smtp");
              transport.connect();
              } catch (Exception e){
                   flag = false;
              return flag;

  • Setting up Leopard Mail Server to access external pop mail accounts

    First I don't know if this is possible, after a few hours trying I am not really sure if I am doing this right.
    I really just want to have my Leopard Mail server pull any new mail from my web hosting company mail servers that host my domain (samplename.com as an example). My domain is hosted by a web hosting company as part of my website package. I don't really want to stop having the web hosting company host my mail portion. (kinda of a backup mail server of sorts?)
    My Leopard mail server is called leopardserver.local and not my domain name (samplename.com). As I am afraid if I call my Leopard server by my domain name (samplename.com) it will stop letting me access my domain name (samplename.com) from my other Macs. Also possibly adding in to pull from my secondary domain name's mail server, and a gmail.com server later.
    I am trying to avoid to creating the MX records, etc. if possible. Will my idea work?

    Thank you pterobyte. This process was much simpler that I thought. After searching on these forums and finding the syntax for the .fetchmailrc file, I found on a website how to change the permissions for the .fetchmailrc file. This is now working when I log in as me and start it up - I will look at making it run from root later when I have more time.
    I do have a question now related to the flip side - sending mail from my server. When I send mail from my server using the webmail piece or the Mail app on the server I received this message:
    <[email protected]>;;: host smtp-server.mycableisp.com[00.00.000.000] said: 553 5.1.8
    <[email protected]>;;... Domain of sender address [email protected]
    does not exist (in reply to MAIL FROM command)
    To fix this I put in the Reply-To a different valid account like [email protected] - this suppresses the error, but my mail is not going anywhere. The recipient does not get the message that was sent.
    1. How can I fix this so my mail flows out and gets delivered?
    2. If I change the server name to something like domainname.net, would this fix #1?
    Here is the interesting part - If I create the message in Mail.app that has a From field (not webmail - which I will be using 99% of the time) everything flows through the mail server and gets delivered.
    My logs are empty in the Server Admin utility.
    I appreciate being able to learn more about this.

  • Mail server setup issues

    Hi.
    I am in trouble setting up a basic mail server. I just spent the last 10 or so hours, in one more try to set it, and yet no results.
    Please, give some help as i am becoming sort of desperated with it
    This time, i followed this guide since the beginning.
    What I've done:
    - Created a user vmail, with home directory set on /var/mail/vmail/
    - Had a LAMP server already working.
    - Created two databases: postfix_db and roundcube_db, owned by postfix_user and roundcube_user respectively.
    - Since it is for personal use and i don't use "old/odd clients like Outlook"  i skipped smtps. And made the following files:
    My postfix main.cf(every commented line removed):
    queue_directory = /var/spool/postfix
    command_directory = /usr/bin
    daemon_directory = /usr/lib/postfix
    data_directory = /var/lib/postfix
    mail_owner = postfix
    mydomain = mydomainname.tld
    unknown_local_recipient_reject_code = 550
    alias_maps = hash:/etc/postfix/aliases
    alias_database = $alias_maps
    debug_peer_level = 2
    debugger_command =
    PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
    ddd $daemon_directory/$process_name $process_id & sleep 5
    sendmail_path = /usr/bin/sendmail
    newaliases_path = /usr/bin/newaliases
    mailq_path = /usr/bin/mailq
    setgid_group = postdrop
    html_directory = no
    manpage_directory = /usr/share/man
    sample_directory = /etc/postfix/sample
    readme_directory = /usr/share/doc/postfix
    inet_protocols = ipv4
    relay_domains = *
    virtual_alias_maps = proxy:mysql:/etc/postfix/virtual_alias_maps.cf
    virtual_mailbox_domains = proxy:mysql:/etc/postfix/virtual_domains_maps.cf
    virtual_mailbox_maps = proxy:mysql:/etc/postfix/virtual_mailbox_maps.cf
    virtual_mailbox_base = /var/mail/vmail
    virtual_mailbox_limit = 512000000
    virtual_minimum_uid = 5000
    virtual_transport = virtual
    virtual_uid_maps = static:5000
    virtual_gid_maps = static:5000
    local_transport = virtual
    local_recipient_maps = $virtual_mailbox_maps
    transport_maps = hash:/etc/postfix/transport
    smtpd_sasl_auth_enable = yes
    smtpd_sasl_type = dovecot
    smtpd_sasl_path = /var/run/dovecot/auth-client
    smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
    smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
    smtpd_sasl_security_options = noanonymous
    smtpd_sasl_tls_security_options = $smtpd_sasl_security_options
    smtpd_tls_auth_only = yes
    smtpd_tls_cert_file = /etc/ssl/private/server.crt
    smtpd_tls_key_file = /etc/ssl/private/server.key
    smtpd_sasl_local_domain = $mydomain
    broken_sasl_auth_clients = yes
    smtpd_tls_loglevel = 1
    Postfix master.cf
    smtp inet n - n - - smtpd
    submission inet n - n - - smtpd
    -o smtpd_tls_security_level=encrypt
    -o smtpd_sasl_auth_enable=yes
    pickup unix n - n 60 1 pickup
    cleanup unix n - n - 0 cleanup
    qmgr unix n - n 300 1 qmgr
    tlsmgr unix - - n 1000? 1 tlsmgr
    rewrite unix - - n - - trivial-rewrite
    bounce unix - - n - 0 bounce
    defer unix - - n - 0 bounce
    trace unix - - n - 0 bounce
    verify unix - - n - 1 verify
    flush unix n - n 1000? 0 flush
    proxymap unix - - n - - proxymap
    proxywrite unix - - n - 1 proxymap
    smtp unix - - n - - smtp
    relay unix - - n - - smtp
    showq unix n - n - - showq
    error unix - - n - - error
    retry unix - - n - - error
    discard unix - - n - - discard
    local unix - n n - - local
    virtual unix - n n - - virtual
    lmtp unix - - n - - lmtp
    anvil unix - - n - 1 anvil
    scache unix - - n - 1 scache
    /etc/postfix/virtual_alias_maps.cf (sample password)
    user = postfix_user
    password = m/<~VN4XQ!G=jE[A/-
    hosts = localhost
    dbname = postfix_db
    query = SELECT goto FROM alias WHERE address='%s' AND active = true
    /etc/postfix/virtual_domains_maps.cf
    user = postfix_user
    password = m/<~VN4XQ!G=jE[A/-
    hosts = localhost
    dbname = postfix_db
    query = SELECT domain FROM domain WHERE domain='%s' AND backupmx = false AND active = true
    /etc/postfix/virtual_mailbox_limits.cf
    user = postfix_user
    password = m/<~VN4XQ!G=jE[A/-
    hosts = localhost
    dbname = postfix_db
    query = SELECT quota FROM mailbox WHERE username='%s'
    /etc/postfix/virtual_mailbox_maps.cf
    user = postfix_user
    password = m/<~VN4XQ!G=jE[A/-
    hosts = localhost
    dbname = postfix_db
    query = SELECT maildir FROM mailbox WHERE username='%s' AND active = true
    - Created the SSL key with no problem, and put it in place.
    Edited dovecot.conf:
    protocols = imap pop3
    auth_mechanisms = plain
    passdb {
    driver = sql
    args = /etc/dovecot/dovecot-sql.conf
    userdb sql {
    driver = sql
    args = /etc/dovecot/dovecot-sql.conf
    service auth {
    unix_listener auth-client {
    group = postfix
    mode = 0660
    user = postfix
    user = root
    mail_home = /var/mail/vmail/%d/%u
    mail_location = maildir:~
    ssl_cert = </etc/ssl/private/server.crt
    ssl_key = </etc/ssl/private/server.key
    dict {
    #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
    #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext
    !include conf.d/*.conf
    !include_try local.conf
    /etc/dovecot/dovecot-sql.conf
    driver = mysql
    connect = host=localhost dbname=postfix_db user=postfix_user password=m/<~VN4XQ!G=jE[A/-
    default_pass_scheme = MD5-CRYPT
    user_query = SELECT '/var/mail/vmail/%d/%u' as home, 'maildir:/var/mail/vmail/%d/%u' as mail, 5000 AS uid, 5000 AS gid, concat('dirsize:storage=', quota) AS quota FROM mailbox WHERE username = '%u' AND active = '1'
    password_query = SELECT username as user, password, '/var/mail/vmail/%d/%u' as userdb_home, 'maildir:/var/mail/vmail/%d/%u' as userdb_mail, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox WHERE username = '%u' AND active = '1'
    - Installed postfixadmin and roundcube and made their apache alias.
    - Made directories writable for them.
    /etc/webapps/postfixadmin/config.inc.php (note that there is no "?>" to end the script, it came just like that, and since it had no error there ill assume its normal)
    <?php
    $CONF['configured'] = true;
    $CONF['setup_password'] = '562bc24a874b0c2a7340e3da04b3fdf6:d60282f5cbc19340c73cafbb6526379be696a7c7';
    $CONF['postfix_admin_url'] = '[url]http://mydomain.com/postfixadmin[/url]';
    $CONF['postfix_admin_path'] = dirname(__FILE__);
    $CONF['default_language'] = 'en';
    $CONF['database_prefix'] = '';
    $CONF['database_tables'] = array (
    'admin' => 'admin',
    'alias' => 'alias',
    'alias_domain' => 'alias_domain',
    'config' => 'config',
    'domain' => 'domain',
    'domain_admins' => 'domain_admins',
    'fetchmail' => 'fetchmail',
    'log' => 'log',
    'mailbox' => 'mailbox',
    'vacation' => 'vacation',
    'vacation_notification' => 'vacation_notification',
    'quota' => 'quota',
    'quota2' => 'quota2',
    $CONF['admin_email'] = '[email protected]';
    $CONF['smtp_server'] = 'localhost';
    $CONF['smtp_port'] = '25';
    $CONF['encrypt'] = 'md5crypt';
    $CONF['authlib_default_flavor'] = 'md5raw';
    $CONF['dovecotpw'] = "/usr/sbin/dovecotpw";
    $CONF['min_password_length'] = 5;
    $CONF['generate_password'] = 'NO';
    $CONF['show_password'] = 'NO';
    $CONF['page_size'] = '10';
    $CONF['default_aliases'] = array (
    'abuse' => '[email protected]',
    'hostmaster' => '[email protected]',
    'postmaster' => '[email protected]',
    'webmaster' => '[email protected]'
    $CONF['domain_path'] = 'NO';
    $CONF['domain_in_mailbox'] = 'YES';
    $CONF['maildir_name_hook'] = 'NO';
    $CONF['aliases'] = '10';
    $CONF['mailboxes'] = '10';
    $CONF['maxquota'] = '10';
    $CONF['quota'] = 'NO';
    $CONF['quota_multiplier'] = '1024000';
    $CONF['transport'] = 'NO';
    $CONF['transport_options'] = array (
    'virtual', // for virtual accounts
    'local', // for system accounts
    'relay' // for backup mx
    $CONF['transport_default'] = 'virtual';
    $CONF['vacation'] = 'NO';
    $CONF['vacation_domain'] = 'autoreply.change-this-to-your.domain.tld';
    $CONF['vacation_control'] ='YES';
    $CONF['vacation_control_admin'] = 'YES';
    $CONF['alias_control'] = 'NO';
    $CONF['alias_control_admin'] = 'NO';
    $CONF['special_alias_control'] = 'NO';
    $CONF['alias_goto_limit'] = '0';
    $CONF['alias_domain'] = 'YES';
    $CONF['backup'] = 'YES';
    $CONF['sendmail'] = 'YES';
    $CONF['logging'] = 'YES';
    $CONF['fetchmail'] = 'YES';
    $CONF['fetchmail_extra_options'] = 'NO';
    $CONF['show_header_text'] = 'NO';
    $CONF['header_text'] = ':: Postfix Admin ::';
    $CONF['user_footer_link'] = "[url]http://mydomain.com[/url]";
    $CONF['show_footer_text'] = 'YES';
    $CONF['footer_text'] = 'Return to mydomain.com';
    $CONF['footer_link'] = '[url]http://mydomain.com[/url]';
    $CONF['welcome_text'] = <<<EOM
    Welcome to your new account.
    EOM;
    $CONF['emailcheck_resolve_domain']='YES';
    $CONF['show_status']='NO';
    $CONF['show_status_key']='NO';
    $CONF['show_status_text']='&nbsp;&nbsp;';
    $CONF['show_undeliverable']='NO';
    $CONF['show_undeliverable_color']='tomato';
    $CONF['show_undeliverable_exceptions']=array("unixmail.domain.ext","exchangeserver.domain.ext","gmail.com");
    $CONF['show_popimap']='NO';
    $CONF['show_popimap_color']='darkgrey';
    $CONF['show_custom_domains']=array("subdomain.domain.ext","domain2.ext");
    $CONF['show_custom_colors']=array("lightgreen","lightblue");
    $CONF['recipient_delimiter'] = "";
    $CONF['create_mailbox_subdirs_prefix']='INBOX.';
    $CONF['used_quotas'] = 'NO';
    $CONF['new_quota_table'] = 'NO';
    $CONF['theme_logo'] = 'images/logo-default.png';
    $CONF['theme_css'] = 'css/default.css';
    $CONF['xmlrpc_enabled'] = false;
    if (file_exists(dirname(__FILE__) . '/config.local.php')) {
    include(dirname(__FILE__) . '/config.local.php');
    $CONF['domain_path'] = 'YES';
    $CONF['domain_in_mailbox'] = 'YES';
    $CONF['database_type'] = 'mysqli';
    $CONF['database_host'] = 'localhost';
    $CONF['database_user'] = 'postfix_user';
    $CONF['database_password'] = 'm/<~VN4XQ!G=jE[A/-';
    $CONF['database_name'] = 'postfix_db';
    - I went to domain/postfixAdmin/setup.php and domain/roundcube/installer/ and everything was ok.
    db.inc.php (roundcube):
    <?php
    $rcmail_config = array();
    $rcmail_config['db_dsnw'] = 'mysql://roundcube_user:%3D%29CYbd9bK%210Z7%29AsWU@localhost/roundcube_db';
    $rcmail_config['db_dsnr'] = '';
    $rcmail_config['db_persistent'] = FALSE;
    $rcmail_config['db_table_users'] = 'users';
    $rcmail_config['db_table_identities'] = 'identities';
    $rcmail_config['db_table_contacts'] = 'contacts';
    $rcmail_config['db_table_contactgroups'] = 'contactgroups';
    $rcmail_config['db_table_contactgroupmembers'] = 'contactgroupmembers';
    $rcmail_config['db_table_session'] = 'session';
    $rcmail_config['db_table_cache'] = 'cache';
    $rcmail_config['db_table_cache_index'] = 'cache_index';
    $rcmail_config['db_table_cache_thread'] = 'cache_thread';
    $rcmail_config['db_table_cache_messages'] = 'cache_messages';
    $rcmail_config['db_table_dictionary'] = 'dictionary';
    $rcmail_config['db_table_searches'] = 'searches';
    $rcmail_config['db_table_system'] = 'system';
    $rcmail_config['db_sequence_users'] = 'user_ids';
    $rcmail_config['db_sequence_identities'] = 'identity_ids';
    $rcmail_config['db_sequence_contacts'] = 'contact_ids';
    $rcmail_config['db_sequence_contactgroups'] = 'contactgroups_ids';
    $rcmail_config['db_sequence_searches'] = 'search_ids';
    main.inc.php(roundcube):
    <?php
    $rcmail_config = array();
    $rcmail_config['debug_level'] = 5;
    $rcmail_config['log_driver'] = 'file';
    $rcmail_config['log_date_format'] = 'd-M-Y H:i:s O';
    $rcmail_config['syslog_id'] = 'roundcube';
    $rcmail_config['syslog_facility'] = LOG_USER;
    $rcmail_config['smtp_log'] = true;
    $rcmail_config['log_logins'] = false;
    $rcmail_config['log_session'] = false;
    $rcmail_config['sql_debug'] = false;
    $rcmail_config['imap_debug'] = false;
    $rcmail_config['ldap_debug'] = false;
    $rcmail_config['smtp_debug'] = false;
    $rcmail_config['default_host'] = 'tls://localhost/';
    $rcmail_config['default_port'] = 993;
    $rcmail_config['imap_auth_type'] = null;
    $rcmail_config['imap_delimiter'] = null;
    $rcmail_config['imap_ns_personal'] = null;
    $rcmail_config['imap_ns_other'] = null;
    $rcmail_config['imap_ns_shared'] = null;
    $rcmail_config['imap_force_caps'] = false;
    $rcmail_config['imap_force_lsub'] = false;
    $rcmail_config['imap_force_ns'] = false;
    $rcmail_config['imap_timeout'] = 0;
    $rcmail_config['imap_auth_cid'] = null;
    $rcmail_config['imap_auth_pw'] = null;
    $rcmail_config['imap_cache'] = null;
    $rcmail_config['messages_cache'] = false;
    $rcmail_config['smtp_server'] = 'tls://localhost/';
    $rcmail_config['smtp_port'] = 587;
    $rcmail_config['smtp_user'] = '';
    $rcmail_config['smtp_pass'] = '';
    $rcmail_config['smtp_auth_type'] = '';
    $rcmail_config['smtp_auth_cid'] = null;
    $rcmail_config['smtp_auth_pw'] = null;
    $rcmail_config['smtp_helo_host'] = '';
    $rcmail_config['smtp_timeout'] = 0;
    $rcmail_config['enable_installer'] = false;
    $rcmail_config['dont_override'] = array();
    $rcmail_config['support_url'] = '';
    $rcmail_config['skin_logo'] = 'sorrybutnocookie';
    $rcmail_config['auto_create_user'] = true;
    $rcmail_config['user_aliases'] = false;
    $rcmail_config['log_dir'] = 'logs/';
    $rcmail_config['temp_dir'] = 'temp/';
    $rcmail_config['message_cache_lifetime'] = '10d';
    $rcmail_config['force_https'] = false;
    $rcmail_config['use_https'] = false;
    $rcmail_config['login_autocomplete'] = 0;
    $rcmail_config['login_lc'] = 2;
    $rcmail_config['skin_include_php'] = false;
    $rcmail_config['display_version'] = false;
    $rcmail_config['session_lifetime'] = 10;
    $rcmail_config['session_domain'] = '';
    $rcmail_config['session_name'] = null;
    $rcmail_config['session_auth_name'] = null;
    $rcmail_config['session_path'] = null;
    $rcmail_config['session_storage'] = 'db';
    $rcmail_config['memcache_hosts'] = null;
    $rcmail_config['ip_check'] = true;
    $rcmail_config['referer_check'] = false;
    $rcmail_config['x_frame_options'] = 'sameorigin';
    $rcmail_config['des_key'] = '0JaV%FnEivx9e+JdH2g*?n3n';
    $rcmail_config['username_domain'] = '';
    $rcmail_config['mail_domain'] = '';
    $rcmail_config['password_charset'] = 'ISO-8859-1';
    $rcmail_config['sendmail_delay'] = 0;
    $rcmail_config['max_recipients'] = 0;
    $rcmail_config['max_group_members'] = 0;
    $rcmail_config['useragent'] = 'Roundcube Webmail/'.RCMAIL_VERSION;
    $rcmail_config['product_name'] = 'Test';
    $rcmail_config['include_host_config'] = false;
    $rcmail_config['generic_message_footer'] = '';
    $rcmail_config['generic_message_footer_html'] = '';
    $rcmail_config['http_received_header'] = false;
    $rcmail_config['http_received_header_encrypt'] = false;
    $rcmail_config['mail_header_delimiter'] = NULL;
    $rcmail_config['line_length'] = 72;
    $rcmail_config['send_format_flowed'] = true;
    $rcmail_config['mdn_use_from'] = false;
    $rcmail_config['identities_level'] = 0;
    $rcmail_config['client_mimetypes'] = null;
    $rcmail_config['mime_magic'] = null;
    $rcmail_config['mime_types'] = null;
    $rcmail_config['im_identify_path'] = null;
    $rcmail_config['im_convert_path'] = null;
    $rcmail_config['image_thumbnail_size'] = 240;
    $rcmail_config['contact_photo_size'] = 160;
    $rcmail_config['email_dns_check'] = false;
    $rcmail_config['no_save_sent_messages'] = false;
    $rcmail_config['plugins'] = array();
    $rcmail_config['message_sort_col'] = '';
    $rcmail_config['message_sort_order'] = 'DESC';
    $rcmail_config['list_cols'] = array('subject', 'status', 'fromto', 'date', 'size', 'flag', 'attachment');
    $rcmail_config['language'] = null;
    $rcmail_config['date_format'] = 'Y-m-d';
    $rcmail_config['date_formats'] = array('Y-m-d', 'Y/m/d', 'Y.m.d', 'd-m-Y', 'd/m/Y', 'd.m.Y', 'j.n.Y');
    $rcmail_config['time_format'] = 'H:i';
    $rcmail_config['time_formats'] = array('G:i', 'H:i', 'g:i a', 'h:i A');
    $rcmail_config['date_short'] = 'D H:i';
    $rcmail_config['date_long'] = 'Y-m-d H:i';
    $rcmail_config['drafts_mbox'] = 'Drafts';
    $rcmail_config['junk_mbox'] = 'Junk';
    $rcmail_config['sent_mbox'] = 'Sent';
    $rcmail_config['trash_mbox'] = 'Trash';
    $rcmail_config['default_folders'] = array('INBOX', 'Drafts', 'Sent', 'Junk', 'Trash');
    $rcmail_config['create_default_folders'] = false;
    $rcmail_config['protect_default_folders'] = true;
    $rcmail_config['quota_zero_as_unlimited'] = false;
    $rcmail_config['enable_spellcheck'] = false;
    $rcmail_config['spellcheck_dictionary'] = false;
    $rcmail_config['spellcheck_engine'] = 'googie';
    $rcmail_config['spellcheck_uri'] = '';
    $rcmail_config['spellcheck_languages'] = NULL;
    $rcmail_config['spellcheck_ignore_caps'] = false;
    $rcmail_config['spellcheck_ignore_nums'] = false;
    $rcmail_config['spellcheck_ignore_syms'] = false;
    $rcmail_config['recipients_separator'] = ',';
    $rcmail_config['max_pagesize'] = 200;
    $rcmail_config['min_refresh_interval'] = 60;
    $rcmail_config['upload_progress'] = false;
    $rcmail_config['undo_timeout'] = 0;
    $rcmail_config['address_book_type'] = 'sql';
    $rcmail_config['ldap_public'] = array();
    $rcmail_config['autocomplete_addressbooks'] = array('sql');
    $rcmail_config['autocomplete_min_length'] = 1;
    $rcmail_config['autocomplete_threads'] = 0;
    $rcmail_config['autocomplete_max'] = 15;
    $rcmail_config['address_template'] = '{street}<br/>{locality} {zipcode}<br/>{country} {region}';
    $rcmail_config['addressbook_search_mode'] = 0;
    $rcmail_config['default_charset'] = 'ISO-8859-1';
    $rcmail_config['skin'] = 'larry';
    $rcmail_config['mail_pagesize'] = 50;
    $rcmail_config['addressbook_pagesize'] = 50;
    $rcmail_config['addressbook_sort_col'] = 'surname';
    $rcmail_config['addressbook_name_listing'] = 0;
    $rcmail_config['timezone'] = 'auto';
    $rcmail_config['prefer_html'] = true;
    $rcmail_config['show_images'] = 0;
    $rcmail_config['message_extwin'] = false;
    $rcmail_config['compose_extwin'] = false;
    $rcmail_config['htmleditor'] = 0;
    $rcmail_config['prettydate'] = true;
    $rcmail_config['draft_autosave'] = 300;
    $rcmail_config['preview_pane'] = false;
    $rcmail_config['preview_pane_mark_read'] = 0;
    $rcmail_config['logout_purge'] = false;
    $rcmail_config['logout_expunge'] = false;
    $rcmail_config['inline_images'] = true;
    $rcmail_config['mime_param_folding'] = 0;
    $rcmail_config['skip_deleted'] = false;
    $rcmail_config['read_when_deleted'] = true;
    $rcmail_config['flag_for_deletion'] = false;
    $rcmail_config['refresh_interval'] = 60;
    $rcmail_config['check_all_folders'] = false;
    $rcmail_config['display_next'] = true;
    $rcmail_config['autoexpand_threads'] = 0;
    $rcmail_config['reply_mode'] = 0;
    $rcmail_config['strip_existing_sig'] = true;
    $rcmail_config['show_sig'] = 1;
    $rcmail_config['force_7bit'] = false;
    $rcmail_config['search_mods'] = null;
    $rcmail_config['addressbook_search_mods'] = null;
    $rcmail_config['delete_always'] = false;
    $rcmail_config['delete_junk'] = false;
    $rcmail_config['mdn_requests'] = 0;
    $rcmail_config['mdn_default'] = 0;
    $rcmail_config['dsn_default'] = 0;
    $rcmail_config['reply_same_folder'] = false;
    $rcmail_config['forward_attachment'] = false;
    $rcmail_config['default_addressbook'] = null;
    $rcmail_config['spellcheck_before_send'] = false;
    $rcmail_config['autocomplete_single'] = false;
    $rcmail_config['default_font'] = 'Verdana';
    - From what i can see, postfixadmin used and populated its database, but not roundcube.
    - I can open postfixadmin and log in with no apparent errors (not that i know what to do with it instead of roundcube, but at least works...)
    - Whenever i open roundcube it begins to output errors everywhere about db connection (I was only able after changing its .htaccess to Allow from all, is it a bad idea?)
    DB Error in /usr/share/webapps/roundcubemail/program/lib/Roundcube/rcube_db.php (416): [1146] Table 'roundcube_db.session' doesn't exist (SQL Query: SELECT vars, ip, changed FROM session WHERE sess_id = 'pq5ofv7ja0gh2sunsg38jmd3g1')
    Warning: session_start(): Cannot send session cache limiter - headers already sent in /usr/share/webapps/roundcubemail/program/lib/Roundcube/rcube.php on line 445
    DB Error: [1146] Table 'roundcube_db.session' doesn't exist
    DATABASE ERROR: CONNECTION FAILED!
    Unable to connect to the database!
    Please contact your server-administrator.
    DB Error in /usr/share/webapps/roundcubemail/program/lib/Roundcube/rcube_db.php (416): [1146] Table 'roundcube_db.session' doesn't exist (SQL Query: INSERT INTO session (sess_id, vars, ip, created, changed) VALUES ('pq5ofv7ja0gh2sunsg38jmd3g1', 'dGVtcHxiOjE7bGFuZ3VhZ2V8czo1OiJlbl9VUyI7dGFza3xzOjU6ImxvZ2luIjs=', 'xxx.xxx.xxx.xxx', '2014-02-08 07:34:46', '2014-02-08 07:34:46'))
    Thats all i know. Whats wrong? (i already tried to set db logins with no pw at all, but still with the same problems)
    How far am i to be able to send/receive one email? Please, tell me i am close...
    Mail servers could be so much more linear to set up
    Thanks for your help. Time to get some sleep!

    The roundcube db schema needs to setup manually. See /usr/share/webapps/roundcube/INSTALL
    Also, from your /etc/webapps/postfixadmin/config.inc.php:
    $CONF['domain_path'] = 'NO';
    $CONF['domain_in_mailbox'] = 'YES';
    $CONF['maildir_name_hook'] = 'NO';
    ..which results in /var/mail/vmail/[email protected]
    From your dovecot.conf
    mail_home = /var/mail/vmail/%d/%u
    ...which results in /var/mail/vmail/domain.com/user
    That doesn't fit together.

  • 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?

  • 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$

  • New Mail server setup

    Greetings,
    I need some pro's cons, Ideas taunts and general whaddia thinks.
    Setting up a new mail server. dpG5 xserve w/ 10,000 rpm drives
    my thoughts are to take the user information off the machine to a second G5 xserve running as an ODM.
    I thought about splitting IMAP/pop services to another box. keeping my primary SMTP Spam/AV away from cyrus, relaying inbound messages to the IMAP server.
    so I would have
    ODM.mydomain
    SMTP1.mydomain
    IMAP1.mydomain
    -- Does anyone see any performance or configuration hick ups here?
    now comes the ugly question.
    How do I set up each smtp server. the imap server is still going to have to run smtp to deliver and recieve delivery of messages. but I need them to answer for mydomain, not host1.mydomain. I'm a little foggy on what comes first
    --j

    There are multiple ways of achieving this.
    The simplest is for the servers to deliver via smtp to each other.
    So (very very simplified):
    Since you said you use OD, I assume all servers will refer to your OD master for user account details.
    Server 1 (Filter)
    Postfix & amavisd & ClamAV & spamassassin
    main.cf and master.cf should be configured like you are used to now except that you only want to be able to send to the content filter and nowhere else.
    In amavisd.conf uncomment and change IP (to IP of SMTP/IMAP server) of this line:
    $forward_method = 'smtp:127.0.0.1:10025';
    No relay settings needed, because you want mail to go the filter first and not to another SMTP server.
    Server 2 (Mail Stores)
    Postfix & Cyrus
    main.cf and master.cf should be configured like you are used to now except that you do not want any kind of filtering anymore. Also set to accept only from Server 1 (since it should not accept incoming mail from the outside world directly)
    Server 3 (Outgoing SMTP)
    Postfix
    main.cf and master.cf should be configured like you are used to now except that you do not need to accept incoming mail. Also no filtering needed (unless you want to scan outgoing mail)
    Mail clients:
    Point incoming to Server 2 and outgoing to Server 3
    That's pretty much it. I know it's not a walkthrough , but then again this kind of setup is better fully understood rather than copied step-by-step.
    Let me know if you need anything else.
    Alex
    P.S.
    -Optionally you could use Server 3 as a secondary MX for backup reasons.
    -For most Postfix settings see : http://www.postfix.org/postconf.5.html
    -All of this can be further improved with firewall rules

  • Changing Mail Server Settings for Other IMAP

    Hello,
             I'm an Admin for a treatment center and one of our psychiatrists has a BB Tour. He asked me the other day if I could set up his email account on our exchange server for him on his phone. Going through the mail setup wizard I selected "Other" account and set it up for IMAP and then it asked me for his email address and password. It took the domain name and then assumed the mail server names were as such. Now in a perfect world, this wouldnt be an issue. I recently took over for a complete moron and this guy has our MX records pointing to a 3rd party company where all of our outside emails go and then the Outlook clients are set up to pop this box in addition to the Exchange setup (I know its totally lame). What Ive done for everyone else is just setup a IMAP account using the server IP address and mail works fine for them. I cannot for the life of me find where I can actually edit the mail server names for the IMAP account I create on his BB Tour. Is this a limitation the phone? Or am I not looking in the right place. Thanks!
    Solved!
    Go to Solution.

    Yup -- refer back to my first reply where I said to use the carrier BIS website...while I didn't say it quite so clearly, I did not say to use the on-device email setup wizards.
    The device interface to BIS (aka email setup wizards) and the carrier website interface to BIS have subtle differences. For what you need to do, you need to use the carrier website from a PC/browser. Here is the link:
    https://bis.na.blackberry.com/html?brand=vzw
    If you have not yet created BIS credentials, you will need to. I find it easier to first create those on the device interface and then use them in the web interface. Afterwards, you will have to use the credentials in the device interface, but there is a "remember me" box so you will only have to enter them once.
    Personally, I rarely use the device interface...a full keyboard, mouse, and monitor are so much simpler for doing things than a tiny BB screen/keyboard. But that's just me.
    Good luck!
    Occam's Razor nearly always applies when troubleshooting technology issues!
    If anyone has been helpful to you, please show your appreciation by clicking the button inside of their post. Please click here and read, along with the threads to which it links, for helpful information to guide you as you proceed. I always recommend that you treat your BlackBerry like any other computing device, including using a regular backup schedule...click here for an article with instructions.
    Join our BBM Channels
    BSCF General Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Mail Server suddenly stopped working

    My mail server has stopped working, and I can't figure out why. This is a brand new MacMini with the latest Maverics Server (preinstalled) that I just setup last month. (We migrated from an Xserve running 10.6.) Up to this point, mail has worked flawlessly.
    This afternoon I used the Server app to create a new user. I then went about setting them up for ssh access and installing a public/private keypair (this is for a git repository). Around the same time, my mail server simply stopped working. As far as I know, no other configuration changes were made.
    When I go into the Mail service in the Server app the status perpetually says "Starting...". The 'postfix status' command says that postfix is not running. I've checked every log and error file, and I can only find three anomolies:
    The SMTP log file reports:
    Feb 11 01:31:06 mail.gloaming.com postfix/postmap[7152]: warning: /Library/Server/Mail/Data/scanner/amavis/local_domains.db: duplicate entry: "mail.gloaming.com"
    This warning has been logged before, several weeks earlier, so I assume it's not a serious problem.
    The other warning is:
    Feb 11 00:10:49 mail.gloaming.com postfix/postfix-script[23141]: warning: not owned by _postfix: /Library/Server/Mail/Data/mta/./guid_device_maps.plist
    Other threads seem to indicate that this warning is benign.
    The only other problem that looks really suspicious (to me) is in the system.log:
    Feb 11 01:22:52 mail.gloaming.com ocspd[4947]: ERROR: unable to get the receiver data from the DB!
    I'm not sure what that means, but it doesn't sound good.
    Some threads point a finger at the virus and junk mail scanners. If I disable all mail filtering, the mail server status will finally change to "Serving mail at mail.gloaming.com". But it isn't. All attempts to get mail from the server are refused.
    (Oh, and I've restarted the server several times.)
    The postconf command tells me that the postfix system isn't accepting outside connections:
    inet_interfaces = loopback-only
    So it would appear that Server is setting this. Any attempt to change it back to "= all" fails, as the server software overwrites it with "= loopback-only" at its first possible opportunity. (Editing the main.cf file and reloading postfix doesn't fix it either.)
    Here's the really strange part. The server just started do this today. I recovered a backup of the main.cf file from yesterday and diffed it with the one that's not working:
    mail:postfix root# diff /Library/Server/Mail/Config/postfix/main.cf /Users/admin/Desktop/main.cf
    675c675
    < inet_interfaces = loopback-only
    > inet_interfaces = all
    682c682
    < smtpd_helo_restrictions = reject_non_fqdn_helo_hostname reject_invalid_helo_hostname
    > smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname
    692c692
    < mydestination = $myhostname, localhost.$mydomain, localhost, mail.gloaming.com
    > mydestination = $myhostname, localhost.$mydomain, localhost, mail.gloaming.com, $mydomain
    712d711
    < postscreen_dnsbl_sites = zen.spamhaus.org*2
    As you can see, the Server software has deliberatly started setting inet_interfaces to loopback-only and I can't figure out how to get it to set it back to "all".
    Some of the other threads have suggested "wipe and reinstall", but I've spent three weeks setting up this sever and shipping it to a co-location facility—starting over really isn't an option.
    I'd really just want to know why the Server software is suddently configuring the mail server so it won't receive any mail!

    The mystery continues.
    This morning, I decided to take a fresh look at what's going on by recovering a backup copy of my entire /Library/Server/Mail/Config directory from last month. Looking at the item capture list, it shows that none of the files in my Mail/Config directory have changed since late last month.
    Here are the disturbing changes.
    In Server/Mail/Config/dovecot/dovecot.conf, there is one different line.
    working:
         protocols = imap pop3 lmtp sieve
    now:
         protocols = lmtp sieve
    So clearly, the server doesn't think we should be running IMAP or POP. Which is probably the root of the problem.
    In Server/Mail/Config/postfix/mail.cf, there are a number of minor/cosmetic differences, but the problematic ones appear to be
    working:
         inet_interfaces = all
         mydestination = $myhostname, localhost.$mydomain, localhost, mail.gloaming.com, $mydomain
    now:
         inet_interfaces = loopback-only
         mydestination = $myhostname, localhost.$mydomain, localhost, mail.gloaming.com
    Again, this configuration would imply that there are no public mail services.
    Some other odd change occured in the Server/Mail/Config/postfix/main.cf file
    working:
         smtpd     pass  -       -       n       -       -       smtpd
         pickup    fifo  n       -       n       60      1       pickup
              -o content_filter=smtp-amavis:[127.0.0.1]:10024
    now:
         smtpd     pass  -       -       n       -       -       smtpd
              -o receive_override_options=no_address_mappings
         pickup    fifo  n       -       n       60      1       pickup
              -o content_filter=
    Reading through some other posts, I also found another inexplicable change reported by other users having similar problems. The /System/Library/LaunchDaemons/org.postfix.master.plist suddenly changed.
    working:
        <key>OnDemand</key>
        <false/>
        <key>ProgramArguments</key>
        <array>
            <string>master</string>
            <string>-c</string>
            <string>/Library/Server/Mail/Config/postfix</string>
        </array>
    now:
        <key>OnDemand</key>
        <true/>
        <key>ProgramArguments</key>
        <array>
            <string>master</string>
            <string>-c</string>
            <string>/Library/Server/Mail/Config/postfix</string>
            <string>-e</string>
            <string>60</string>
        </array>
    The postfix service is now "OnDemand" with a new, and myserious, "-e 60" option added. (I can find no documentation for an -e option in the postfix control tool.)
    Ultimately, I "fixed" the problem by restoring the backup copy of my entire /Library/Server/Mail/Config folder, the /System/Library/LaunchDaemon/org.postfix.master.plist file, and immedately restarting the server. The mail servers started and everything appears to be normal.
    But this whole experience has made me very learly of the Server app. Why did these configuration changes occur? What settings or circumstances caused them to spontaniously change to an, essentually, unusable state? I'm now afriad of making any changes via Server.app for fear it will decide I shouldn't have a working mail server again.
    If anyone has any insights, I'd ver very interested in hearing them.
    Message was edited by: James Bucanek

  • Mail server has just stopped working. No errors in any log. Help!

    I am running OS X Server 3.0.2 on Mavericks 10.9.1. Today at around 14:30 my Mail server, which has been working fine for over a year and for nearly a month under Server 3.0.2 just stopped working! I have tried stopping and starting Mail in Server.app and via ServerAdmin but the servcies will not start... serveradmin claims that IMAP is running but that SMTP/SMTPD/Virus Scanner/SPAM filtering/Virus updating are not. I tried disabling the all the filtering services but to no avail. Even though it claims IMAP is running I cannot connect from any client...
    I have rebooted the machine but this did not help. I have looked at all the logs (system, mail, dovecot, postfix, amavis) and theer are no suspicious messages in any of them!
    I am out of ideas and my mail server is down which is very serious so if anyone has any ideas please pitch in.
    Thanks.

    My problems were:
    1.    Server.app shows the Mail service stuck in 'starting' status
    2.    serveradmin shows that IMAP is running but SMTPD, Spam filtering, Virus filtering and Virus updating were STOPPED.
    3.    No clients could connect to either IMAPS or SMTP.
    Diagnostics performed:
    All the various messafge logs (system.log, Mail.log, mail-info.log mail-err.log, amavis.log) show no abnormal messages.
    DNS is working just fine.
    In the end I did the following:
    1.    Stop all mail related services.
    2.    Make a safe copy of /Library/Server/Mail/Config
    3.    Restore the previous days version of /Library/Server/Mail/Config from backup.
    4.    Start the Mail service
    And all was working again just fine.
    I then did a file by file compare of all the configuration files between the workign and not working configurations and I found just the following two differences in postfix/main.cf:
    Not working:
    inet_interfaces = loopback-only
    smtpd_helo_required = no
    Working:
    inet_interfaces = all
    smtpd_helo_required = yes
    I don't think the second difference is so critical but the first seems to break everything (not too surprising I guess). All the other files were identical.
    So, the good news is that all is working again but the huge concern is why this change happenned, seemingly at random. My strong suspicion is that Server.app, at some point when I exited it havign made some minor change unrelated to mail decided to apply these incorrect changes to the Mail configuration. Why it would do this is beyond me. I think there are some subtle bugs in Server 3.0 (and maybe Server 2.2 as well)...

  • Mac Mail Smart Folders triplicate messages (Gmail-based mail server)

    I can't get Mail Smart Folders to work well with my Virginmedia mail server, which seems to use a Gmail type of system. (I'm using IMAP).
    It is easy to set up an instruction to select mail e.g. from defined individuals only, or any other qualifier.
    However, I get all mail in triplicate: from the normal Inbox, but also from Gmail-type "All Mail" and "Important" inboxes. I know these mailboxes exist on the Virginmedia server, and also, virtually, in Mail, but I don't ever look at them or need to.  There might be a way of not having all mails defined as "Important" on the server, but "All Mail" exists by default and can't be removed, for obvious reasons.
    I have tried various additional instructions in the Smart Folder such as include if "Message is in Inbox", but that selects all messages. Also, if "Message is not in Inbox", so that I get only two sets of messages, but that has produced strange results such as messages marked as in Spam folder, which seem to have nothing to do with the defined instructions.
    Is there anything "smart" I can do about this, or is it just a matter of Mail not being up to speed with Gmail-based servers. It's just an annoyance, more than anything.

    Nope. Gone.
    I went to my second mac. Opened Mail, it refreshed its previous state, with 1100 messages in the Inbox, I was relieved and while thinking about my backup options, Mail started its new activity cycle and POOF....Gone. One test message in the Inbox.

  • Mail Server Transfer!

    I have Xserve running Mail Server, OD and Web which includes Mailman and webmail.
    I have the boot drive and another partition which has the Mail Data on it..
    what is the best way to transfer the files from this machine to another Xserve running 10.6.. i mean i know how to export mail settings under Server Admin, but how can i get the database and all that transfered.. i'm afraid i will lose something .. and never done this before!

    I do my Cyrus backups to one of the internal drives on my Xserve via mailbfr (1 for backup 2 drives for mirrored OS, and an external array for mail data). When I want to migrate a user to my new Xserve running 10.6, I eject the backup disk and put it in one of the drive bays on the new Xserve. On the new Xserve, I have two 2TB drives mirrored for the mail, an internal SSD drive for the OS and a cheapo third drive I backup the OS to via Carbon Copy Cloner. I can just pop the third drive out and put in the backup disk from the other Xserve.
    Note: I assume you are running Leopard Server on the old Xserve. Before you move any mail data over, you must stop the mail service. Cyrus is prone to corruption of the mail database unless you stop the mail service. Not so much with Dovecot, which is a big reason I am migrating...
    Other was to do it are to copy your mail database to a Firewire of USB drive, then on to the new server, or over the network. Just remember to stop the mail service first.
    On my new server, I am creating my OD users from scratch. I had some corruption on my other server, and wanted to start clean. For the mail settings, I'm duplicating them by hand via the ServerManager Mail plugin, or manually editing the files (/etc/postfix/main.cf and etc/dovecot/dovecot.conf). Also, I'm not doing all the mail accounts at once, but in groups. all-at-once is too risky for me. See:
    http://discussions.apple.com/thread.jspa?threadID=2383747&tstart=0
    for some specifics on my mail migration.
    Message was edited by: flatrack

  • Mail Server changed

    Had a mail server change. Made the change on the BB, but apparently the IMAP port is different on the new server from the old. It does not appear I can change the port through the BB. Any ideas?  I would change it to POP, but it doesn't give the option.
    I could delete the email account, and add it back, but I am worried I may lose my existing mail when I delete the account.
    Any help is appreciated, I'm sure someone has run into this ....
    Ron

    I would recommend to delete the account and set it back up.
    What do you mean by loose the existing email?
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • Backup MX Server

    I have my domain with an ISP and all is well.
    I was wanting to set my domains DNS records so that I get copies of all emails, sent and recieved on this domain, to my mac OSX 10.7 Server, as a backup.
    I have OSX Server 10.7.latest setup and ready to go with the Domain name, IP, Reverse DNS, etc and email, user account, settings.
    Is it simply a matter of creating another MX record in my Domain Names MX record, at the ISP, to point to my OSX 10.7 Servers external WAN IP number?
    The current MX mail record has a priority of 10
    I have a few other OSX 10.7 Servers running as primary domain mail servers, so I am familar with a working setup already.
    Thank you,

    Yes, this is possible.  But you will not have a unified message store and you will need to do a redirection of your client systems.  Here is the reasons.
    First, if you have mail server 1 at mail1.domian.com and a second at mail2.domain.com, it is easy to create the same accounts on these systems.  Thus, MX failover will "work."  But unless they are accessing the same message store (some SAN storage), you will not have a unified message store.  Thus, is mail1 is running smooth and has 10s of GB of mail and goes down, then mail2 will start receiving messages but the historical content will not be present.  The results on the client (IMAP, Exchange, etc) will be unpredictable and merging the content once mail1 comes back on line will be painful to say the least.  Again, this is solved via a clusters mail solution accessing common storage.  Apple used to support this with a click.  Ah, the good old days. 
    The issue with a clustered server though is that both head nodes tend to be in the same place since they need access to the same storage.  And then you are back to a single point of failure... the storage. 
    Now, the second point is that you will have no means of handling the client during the failure of mail1.  Recall, MX records are for mail delivery routing, not from IMAP/POP/Exchange client connections.  If this is the case and you configure your mail clients to connect to mail1.domain.com and this server goes down, they will not magically connect to mail2 unless you modify all client configurations.  But again, we are back to the message store.
    If you are looking for backup, look at services like MX Save.  They provide an SMTP backup service that will collect all undeliverable mail while your primary server is down and then deliver it when you are back up.  Plus, the mimic your server allowing web based or client based access during primary server outage allowing your users to continue to function as if the primary server were still running.
    Building your own mail cluster is difficult enough without the limitations of OS X.  If you are really looking to do this you ought to look at another platform.  Even Kerio is really bad at this.  Especially when you are considering multiple locations.  Keeping the storage in sync is almost impossible on a high traffic server.

Maybe you are looking for

  • Different message in va01: Defect in ECC6 server while saving the sales order .

    Hi ABAP gurus, I am in to upgrade Project In ECC6 server I am getting the different message when saving the sales order in va01 compare to  old sever(4.7) . I have to make it to the same message as it is in the 4.7 server. plz help me . Regards, vana

  • How to find out which C library I am using?

    On my Solaris 9 UltraSparc system, % echo $LD_LIBRARY_PATH /opt/gcc/3.4.4/lib:/opt/glib/2.12.1/lib:/opt/gnome/lib:/opt/openssl/0.9.7g/lib % /usr/lib/libc.so usage: ld.so.1 [-e option,...] dynamic-object [object args,...] On my Solaris 10 x86 system,

  • Problem using admin_client.jar -addDataSourceConnectionPool

    I am using admin_client.jar -addDataSourceConnectionPool to create a Connection Pool. Below is the command i am using java admin_client.jar deployer:oc4j:opmn://localhost:6003/home admin welcome -addDataSourceConnectionPool -applicationName default -

  • How to set a radio button to be selected?

    I'm trying to find out how to do something that should be seemingly simple. That is to create a little function that selects a random radio button as selected. I have 3 radio buttons in a group (see code): </mx:ApplicationControlBar> <mx:RadioButtonG

  • PowerPivot crash Excel 2013 32 bit

    Hi, When trying to connect Oracle DB (11g) on default configuration  (just when trying to do test connection), Excel crashes each time. Power Query connecting well same DB on same server. From Visual Studio I can connect same DB on same server. From