Results 1 to 5 of 5

Thread: Zimbra's postfix main.cf file not saving changes after reboot!

  1. #1
    Join Date
    Oct 2006
    Posts
    4
    Rep Power
    9

    Default Zimbra's postfix main.cf file not saving changes after reboot!

    Greetings, I'm running Zimbra on Ubuntu and I what I wanted to do is use BitDefender's antivirus to scan mail instead of clam or whatever it has by default. I edited the Postfix main.cf and master.cf files and marked out the zimbra antivirus and added the lines for the BitDefender antivirus, according to the instructions by BitDefender and reloaded postfix and it worked flawlessly.

    However, as soon as I reboot, all of the changes made to the main.cf file concerning the BitDefender antivirus in /opt/zimbra/postfix-2.2.9/conf/ folder are gone and it's back to not working again.

    Here is what the main.cf file looks like after I have configured it to use BitDefender before I reboot:


    #
    #content_filter = smtp-amavis:[127.0.0.1]:10024
    #

    myhostname = localhost.localdomain
    recipient_delimiter =
    smtpd_sasl_auth_enable = yes
    smtpd_tls_auth_only = yes
    smtpd_use_tls = yes
    disable_dns_lookups = no
    message_size_limit = 10240000
    mailbox_size_limit = 0
    relayhost =
    smtpd_recipient_restrictions = reject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_unlisted_recipient, reject_invalid_hostname, reject_non_fqdn_sender, reject_unauth_destination, permit
    alias_maps = hash:/etc/aliases
    broken_sasl_auth_clients = yes
    command_directory = /opt/zimbra/postfix-2.2.9/sbin
    daemon_directory = /opt/zimbra/postfix-2.2.9/libexec
    header_checks = pcre:/opt/zimbra/conf/postfix_header_checks
    mailq_path = /opt/zimbra/postfix-2.2.9/sbin/mailq
    manpage_directory = /opt/zimbra/postfix-2.2.9/man
    newaliases_path = /opt/zimbra/postfix-2.2.9/sbin/newaliases
    queue_directory = /opt/zimbra/postfix-2.2.9/spool
    sender_canonical_maps = ldap:/opt/zimbra/conf/ldap-scm.cf
    sendmail_path = /opt/zimbra/postfix-2.2.9/sbin/sendmail
    smtpd_client_restrictions = reject_unauth_pipelining
    smtpd_data_restrictions = reject_unauth_pipelining
    smtpd_helo_required = yes
    smtpd_reject_unlisted_recipient = no
    smtpd_tls_cert_file = /opt/zimbra/conf/smtpd.crt
    smtpd_tls_key_file = /opt/zimbra/conf/smtpd.key
    smtpd_tls_loglevel = 1
    transport_maps = ldap:/opt/zimbra/conf/ldap-transport.cf
    version = 2.2.9
    virtual_alias_domains = ldap://opt/zimbra/conf/ldap-vad.cf
    virtual_alias_maps = ldap:/opt/zimbra/conf/ldap-vam.cf
    virtual_mailbox_domains = ldap:/opt/zimbra/conf/ldap-vmd.cf
    virtual_mailbox_maps = ldap:/opt/zimbra/conf/ldap-vmm.cf
    virtual_transport = error
    #Added by BitDefender, do not remove!
    content_filter = smtp:127.0.0.1:10025

    #End of added lines

    Here is what it looks like after I reboot:


    #
    #content_filter = smtp-amavis:[127.0.0.1]:10024
    #

    myhostname = localhost.localdomain
    recipient_delimiter =
    smtpd_sasl_auth_enable = yes
    smtpd_tls_auth_only = yes
    smtpd_use_tls = yes
    disable_dns_lookups = no
    message_size_limit = 10240000
    mailbox_size_limit = 0
    relayhost =
    smtpd_recipient_restrictions = reject_non_fqdn_recipient, permit_sasl_authenticated, permit_mynetworks, reject_unlisted_recipient, reject_invalid_hostname, reject_non_fqdn_sender, reject_unauth_destination, permit
    alias_maps = hash:/etc/aliases
    broken_sasl_auth_clients = yes
    command_directory = /opt/zimbra/postfix-2.2.9/sbin
    daemon_directory = /opt/zimbra/postfix-2.2.9/libexec
    header_checks = pcre:/opt/zimbra/conf/postfix_header_checks
    mailq_path = /opt/zimbra/postfix-2.2.9/sbin/mailq
    manpage_directory = /opt/zimbra/postfix-2.2.9/man
    newaliases_path = /opt/zimbra/postfix-2.2.9/sbin/newaliases
    queue_directory = /opt/zimbra/postfix-2.2.9/spool
    sender_canonical_maps = ldap:/opt/zimbra/conf/ldap-scm.cf
    sendmail_path = /opt/zimbra/postfix-2.2.9/sbin/sendmail
    smtpd_client_restrictions = reject_unauth_pipelining
    smtpd_data_restrictions = reject_unauth_pipelining
    smtpd_helo_required = yes
    smtpd_reject_unlisted_recipient = no
    smtpd_tls_cert_file = /opt/zimbra/conf/smtpd.crt
    smtpd_tls_key_file = /opt/zimbra/conf/smtpd.key
    smtpd_tls_loglevel = 1
    transport_maps = ldap:/opt/zimbra/conf/ldap-transport.cf
    version = 2.2.9
    virtual_alias_domains = ldap://opt/zimbra/conf/ldap-vad.cf
    virtual_alias_maps = ldap:/opt/zimbra/conf/ldap-vam.cf
    virtual_mailbox_domains = ldap:/opt/zimbra/conf/ldap-vmd.cf
    virtual_mailbox_maps = ldap:/opt/zimbra/conf/ldap-vmm.cf
    virtual_transport = error
    #Added by BitDefender, do not remove!
    content_filter =

    #End of added lines
    Why is it deleting the BitDefender information after reboot, and how can I make it stop?

  2. #2
    Join Date
    Aug 2005
    Posts
    1,433
    Rep Power
    12

    Default main.cf is auto-generated

    Zimbra regenerates main.cf. If you want to persistently change the postfix config, I believe you need to edit /opt/zimbra/conf/zmmta.cf instead and add/change a POSTCONF line.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  3. #3
    Join Date
    Oct 2006
    Posts
    4
    Rep Power
    9

    Default

    Quote Originally Posted by dkarp
    Zimbra regenerates main.cf. If you want to persistently change the postfix config, I believe you need to edit /opt/zimbra/conf/zmmta.cf instead and add/change a POSTCONF line.
    Thanks for the quick response.

    So what you're saying is that in the zmmta.cf the lines that contain the following:

    smtp-amavis:[127.0.0.1]:10024

    I should change to:

    smtp:127.0.0.1:10025

    to match the correct BitDefender configuration?

  4. #4
    Join Date
    Sep 2005
    Posts
    274
    Rep Power
    10

    Default

    sounds rights, but we may not blow away zmmta.cf on upgrades, so watch out for that.
    Bugzilla - Wiki - Downloads - Before posting... Search!

  5. #5
    Join Date
    Oct 2006
    Posts
    4
    Rep Power
    9

    Default

    Quote Originally Posted by anand
    sounds rights, but we may not blow away zmmta.cf on upgrades, so watch out for that.
    Thanks, that worked for me. Much appreciated.

Similar Threads

  1. centos 5 zimbra 4.5.6 no statistics
    By rutman286 in forum Installation
    Replies: 9
    Last Post: 08-14-2007, 10:30 AM
  2. Replies: 3
    Last Post: 07-18-2007, 08:01 AM
  3. Opensource backup Question.
    By nfear24 in forum Administrators
    Replies: 3
    Last Post: 04-01-2007, 12:47 AM
  4. Traslation SVN tree status
    By meikka in forum I18N/L10N - Translations
    Replies: 7
    Last Post: 02-13-2007, 11:13 AM
  5. M3 problem with shares
    By titangears in forum Users
    Replies: 4
    Last Post: 01-12-2006, 01:01 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •