Suddenly my mails have stopped working following upgrading to 3.1.2. Code: postfix.service - LSB: Postfix Mail Transport Agent Loaded: loaded (/etc/init.d/postfix; bad; vendor preset: enabled) Drop-In: /run/systemd/generator/postfix.service.d └─50-postfix-$mail-transport-agent.conf Active: active (running) since Sun 2017-02-12 01:52:25 IST; 1 day 9h ago Docs: man:systemd-sysv-generator(8) Process: 4426 ExecStop=/etc/init.d/postfix stop (code=exited, status=0/SUCCESS) Process: 4460 ExecStart=/etc/init.d/postfix start (code=exited, status=0/SUCCESS) Tasks: 17 Memory: 43.7M CPU: 9min 33.946s CGroup: /system.slice/postfix.service ├─ 4584 /usr/lib/postfix/sbin/master ├─21007 pickup -l -t unix -u -c ├─21008 error -n retry -t unix -u -c ├─21009 qmgr -l -t unix -u ├─21010 smtp -n amavis -t unix -u -c -o smtp_data_done_timeout=1200 -o smtp_send_xforward_command=yes ├─21011 tlsmgr -l -t unix -u -c ├─21012 smtp -n amavis -t unix -u -c -o smtp_data_done_timeout=1200 -o smtp_send_xforward_command=yes ├─21013 bounce -z -n defer -t unix -u -c ├─21014 scache -l -t unix -u -c ├─21015 bounce -z -n defer -t unix -u -c ├─21016 error -n retry -t unix -u -c ├─21017 error -n retry -t unix -u -c ├─21071 cleanup -z -t unix -u -c ├─21072 proxymap -t unix -u ├─21073 trivial-rewrite -n rewrite -t unix -u -c ├─21116 showq -t unix -u -c └─21135 smtpd -n smtp -t inet -u -c -o stress= -s 2 Feb 13 11:30:01 ip-172-31-17-191 postfix/cleanup[21071]: 5F3D6A9207: message-id=<20170213060001.5F3D6A9207 Feb 13 11:30:01 ip-172-31-17-191 postfix/qmgr[21009]: 5F3D6A9207: from=<[email protected],internal>, size=935, nrcpt=1 (queue active) Feb 13 11:30:01 ip-172-31-17-191 postfix/error[21016]: 5F3D6A9207: to=<[email protected],interna>, orig_to=<xxx>, relay=none, delay=0.06, delays=0.05/0/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) Feb 13 11:30:02 ip-172-31-17-191 postfix/pickup[21007]: 2A6F0A9209: uid=5006 from=<web3> Feb 13 11:30:02 ip-172-31-17-191 postfix/cleanup[21071]: 2A6F0A9209: message-id=<[email protected],internal> Feb 13 11:30:02 ip-172-31-17-191 postfix/qmgr[21009]: 2A6F0A9209: from=<[email protected],interna>, size=984, nrcpt=1 (queue active) "~/a.txt" 40L, 3242C 1,1 Top
When I restart amavis , status shows Code: sudo service amavis status ● amavis.service - LSB: Starts amavisd-new mailfilter Loaded: loaded (/etc/init.d/amavis; bad; vendor preset: enabled) Active: active (running) since Mon 2017-02-13 15:23:26 IST; 3s ago Docs: man:systemd-sysv-generator(8) Process: 3307 ExecStop=/etc/init.d/amavis stop (code=exited, status=0/SUCCESS) Process: 3317 ExecStart=/etc/init.d/amavis start (code=exited, status=0/SUCCESS) Tasks: 1 Memory: 110.5M CPU: 792ms CGroup: /system.slice/amavis.service └─3337 /usr/sbin/amavisd-new (master Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: No decoder for .iso Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: No decoder for .jar Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: No decoder for .lha Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: No decoder for .lrz Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: No decoder for .lz4 Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: No decoder for .swf Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: Using primary internal av scanner code for ClamAV-clamd Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: Found secondary av scanner ClamAV-clamscan at /usr/bin/clamscan Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: Deleting db files snmp.db,__db.002,__db.001,__db.003 in /var/lib/amavis/db Feb 13 15:23:26 ip-172-31-17-191 amavis[3337]: Creating db in /var/lib/amavis/db/; BerkeleyDB 0.55, libdb 5.3 and netstat -tap | grep amavis shows Code: tcp 0 0 localhost:10024 *:* LISTEN 3629/amavisd-new (m tcp 0 0 localhost:10026 *:* LISTEN 3629/amavisd-new (m tcp6 0 0 ip6-localhost:10024 [::]:* LISTEN 3629/amavisd-new (m tcp6 0 0 ip6-localhost:10026 [::]:* LISTEN 3629/amavisd-new (m However, within minutes service amavis status starts showing following error Code: Feb 13 15:28:25 ip-172-31-17-191 amavis[3629]: (!!)TROUBLE in pre_loop_hook: db_init: BDB no dbN: BDB0002 __fop_file_setup: Retry limit (100) Feb 13 15:28:25 ip-172-31-17-191 amavis[3629]: (!)_DIE: Suicide () TROUBLE in pre_loop_hook: db_init: BDB no dbN: BDB0002 __fop_file_setup: Re and the netstat -tap | grep amavis result shows nothing
Solved Code: cd /var/lib/amavis/db/ rm * sa-update service rsyslog restart /etc/init.d/amavis zap /etc/init.d/amavis start service postfix restart I dont know which one worked, but its working perfectly fine now
Sorry I thought issue was resolved but 1. though I am receiving mails. Sending test mails from gmail to mydomains mail shows following error : 2. I am not able to send mails through Thunderbird. (SquirrelMail is sending normally) My /etc/postfix/master.cf Code: # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master" or # on-line: http://www.postfix.org/master.5.html). # # Do not forget to execute "postfix reload" after editing this file. # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (no) (never) (100) # ========================================================================== smtp inet n - y - - smtpd #smtp inet n - y - 1 postscreen #smtpd pass - - y - - smtpd #dnsblog unix - - y - 0 dnsblog #tlsproxy unix - - y - 0 tlsproxy submission inet n - y - - smtpd -o syslog_name=postfix/submission -o smtpd_tls_security_level=encrypt -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject # -o smtpd_reject_unlisted_recipient=no # -o smtpd_client_restrictions=$mua_client_restrictions # -o smtpd_helo_restrictions=$mua_helo_restrictions # -o smtpd_sender_restrictions=$mua_sender_restrictions # -o smtpd_recipient_restrictions= # -o smtpd_relay_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING smtps inet n - y - - smtpd -o syslog_name=postfix/smtps -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes -o smtpd_client_restrictions=permit_sasl_authenticated,reject # -o smtpd_reject_unlisted_recipient=no # -o smtpd_client_restrictions=$mua_client_restrictions # -o smtpd_helo_restrictions=$mua_helo_restrictions # -o smtpd_sender_restrictions=$mua_sender_restrictions # -o smtpd_recipient_restrictions= # -o smtpd_relay_restrictions=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #628 inet n - y - - qmqpd "/etc/postfix/master.cf" 167L, 7750C 1,1 Top My /etc/postfix/main.cf Code: # See /usr/share/postfix/main.cf.dist for a commented, more complete version # Debian specific: Specifying a file name will cause the first # line of that file to be used as the name. The Debian default # is /etc/mailname. #myorigin = /etc/mailname smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu) biff = no # appending .domain is the MUA's job. append_dot_mydomain = no # Uncomment the next line to generate "delayed mail" warnings delay_warning_time = 4h readme_directory = /usr/share/doc/postfix # TLS parameters smtpd_tls_cert_file = /etc/postfix/smtpd.cert smtpd_tls_key_file = /etc/postfix/smtpd.key smtpd_use_tls = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache # See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for # information on enabling SSL in the smtp client. smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination myhostname = ip-172-31-17-191.ap-south-1.compute.internal alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases alias_database = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases myorigin = /etc/mailname mydestination = ip-172-31-17-191.ap-south-1.compute.internal, localhost, localhost.localdomain relayhost = mynetworks = 127.0.0.0/8 [::1]/128 mailbox_size_limit = 0 recipient_delimiter = + inet_interfaces = all inet_protocols = all 35,63 Top
result of netstat -tap Code: Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 localhost:10024 *:* LISTEN 19909/amavisd-new ( tcp 0 0 localhost:10025 *:* LISTEN 24657/master tcp 0 0 localhost:mysql *:* LISTEN 24876/mysqld tcp 0 0 localhost:10026 *:* LISTEN 19909/amavisd-new ( tcp 0 0 localhost:10027 *:* LISTEN 24657/master tcp 0 0 *:submission *:* LISTEN 24657/master tcp 0 0 localhost:11211 *:* LISTEN 1246/memcached tcp 0 0 *:pop3 *:* LISTEN 28475/dovecot tcp 0 0 *:imap2 *:* LISTEN 28475/dovecot tcp 0 0 *:urd *:* LISTEN 24657/master tcp 0 0 *:ftp *:* LISTEN 1564/pure-ftpd (SER tcp 0 0 ip-172-31-17-191:domain *:* LISTEN 1200/named tcp 0 0 localhost:domain *:* LISTEN 1200/named tcp 0 0 *:ssh *:* LISTEN 1255/sshd tcp 0 0 *:smtp *:* LISTEN 24657/master tcp 0 0 localhost:953 *:* LISTEN 1200/named tcp 0 0 *:imaps *:* LISTEN 28475/dovecot tcp 0 0 *:pop3s *:* LISTEN 28475/dovecot tcp 0 0 localhost:45184 localhost:mysql ESTABLISHED 29182/amavisd-new ( tcp 0 0 localhost:mysql localhost:45372 ESTABLISHED 24876/mysqld tcp 0 0 localhost:mysql localhost:45326 ESTABLISHED 24876/mysqld tcp 0 0 localhost:45332 localhost:mysql TIME_WAIT - tcp 0 0 localhost:mysql localhost:45370 ESTABLISHED 24876/mysqld tcp 0 0 ip-172-31-17-191.:pop3s 47.247.1.225:54670 TIME_WAIT - tcp 0 0 localhost:10025 localhost:60044 TIME_WAIT - tcp 0 0 localhost:mysql localhost:45136 ESTABLISHED 24876/mysqld tcp 0 0 localhost:mysql localhost:45184 ESTABLISHED 24876/mysqld tcp 0 0 localhost:10025 localhost:60036 TIME_WAIT - tcp 0 0 localhost:45136 localhost:mysql ESTABLISHED 29074/amavisd-new ( tcp 0 0 localhost:45328 localhost:mysql ESTABLISHED 27529/proxymap tcp 0 0 localhost:45326 localhost:mysql ESTABLISHED 27529/proxymap tcp 0 0 localhost:mysql localhost:45328 ESTABLISHED 24876/mysqld tcp 0 504 ip-172-31-17-191.ap:ssh 47.247.1.225:57928 ESTABLISHED 26980/sshd: ubuntu tcp 0 0 localhost:45370 localhost:mysql ESTABLISHED 27529/proxymap tcp 0 0 localhost:mysql localhost:45324 ESTABLISHED 24876/mysqld tcp 0 0 localhost:45324 localhost:mysql ESTABLISHED 27529/proxymap tcp 0 0 localhost:45330 localhost:mysql TIME_WAIT - tcp 0 0 localhost:45372 localhost:mysql ESTABLISHED 27529/proxymap tcp6 0 0 ip6-localhost:10024 [::]:* LISTEN 19909/amavisd-new ( tcp6 0 0 ip6-localhost:10026 [::]:* LISTEN 19909/amavisd-new ( tcp6 0 0 [::]:submission [::]:* LISTEN 24657/master tcp6 0 0 [::]:pop3 [::]:* LISTEN 28475/dovecot tcp6 0 0 [::]:imap2 [::]:* LISTEN 28475/dovecot tcp6 0 0 [::]:http-alt [::]:* LISTEN 25612/apache2 tcp6 0 0 [::]:http [::]:* LISTEN 25612/apache2 tcp6 0 0 [::]:tproxy [::]:* LISTEN 25612/apache2 tcp6 0 0 [::]:urd [::]:* LISTEN 24657/master tcp6 0 0 [::]:ftp [::]:* LISTEN 1564/pure-ftpd (SER tcp6 0 0 [::]:domain [::]:* LISTEN 1200/named tcp6 0 0 [::]:ssh [::]:* LISTEN 1255/sshd tcp6 0 0 [::]:smtp [::]:* LISTEN 24657/master tcp6 0 0 ip6-localhost:953 [::]:* LISTEN 1200/named tcp6 0 0 [::]:https [::]:* LISTEN 25612/apache2 tcp6 0 0 [::]:imaps [::]:* LISTEN 28475/dovecot tcp6 0 0 [::]:pop3s [::]:* LISTEN 28475/dovecot tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45742 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45714 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45726 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45746 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45710 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45738 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45698 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45730 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45750 ESTABLISHED 25622/apache2 tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45694 TIME_WAIT - tcp6 0 0 ip-172-31-17-1:http-alt 47.247.1.225:45734 TIME_WAIT -
Got the same! Have status=deferred (delivery temporarily suspended: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused) On a Debian 7 machine after upgrading. I don't have Amavis or whatsoever running as I have antispam server elsewhere. Anyway - no one is receiving e-mail. How can I configure a full pass through on Postfix?
Your issue is completely different from this thread. If you don't want to use amavis, then disable it in your postfix configuration: https://www.faqforge.com/linux/cont...ilter-and-antivirus-functions-in-ispconfig-3/
@Rajnish Khare: The postfix config and netstat looks fine as far as I can see, postfix is running and listening on the external interface. The error that you get means that either gmail and your mail client connect to a wrong server (check dns) or you have a firewall on the server or in front of the server that blocks connects on port 25. Update: I just looked at master.cf, I checked main.cf now and this main.cf is not one from an ISPConfig server, you must have overwritten the file made by ispconfig with another one that is not compatible with ispconfig. You should rerun an ispconfig update and choose reconfigure services to fix your main.cf file.
I tried to update, but looks like I goofed up somewhere. I got following error message in the end : Code: Restarting services ... Job for postfix.service failed because the control process exited with error code. See "systemctl status postfix.service" and "journalctl -xe" for details. Update finished. on systemctl status postfix.service : Code: ● postfix.service - LSB: Postfix Mail Transport Agent Loaded: loaded (/etc/init.d/postfix; bad; vendor preset: enabled) Drop-In: /run/systemd/generator/postfix.service.d └─50-postfix-$mail-transport-agent.conf Active: failed (Result: exit-code) since Thu 2017-02-16 18:10:32 IST; 55s ago Docs: man:systemd-sysv-generator(8) Process: 8282 ExecStart=/etc/init.d/postfix start (code=exited, status=1/FAILURE) Feb 16 18:10:28 ip-172-31-17-191 systemd[1]: Stopped LSB: Postfix Mail Transport Agent. Feb 16 18:10:28 ip-172-31-17-191 systemd[1]: Starting LSB: Postfix Mail Transpor Agent. Feb 16 18:10:28 ip-172-31-17-191 postfix[8282]: * Starting Postfix Mail Transpo Agent postfix Feb 16 18:10:30 ip-172-31-17-191 postfix[8282]: postconf: fatal: invalid type field "master" in "stfix master process configuration file. For details on the format" Feb 16 18:10:31 ip-172-31-17-191 postfix[8282]: postconf: fatal: invalid type field "master" in "stfix master process configuration file. For details on the format" Feb 16 18:10:32 ip-172-31-17-191 systemd[1]: postfix.service: Control process exited, code=exited status=1 Feb 16 18:10:32 ip-172-31-17-191 systemd[1]: Failed to start LSB: Postfix Mail Transport Agent. Feb 16 18:10:32 ip-172-31-17-191 systemd[1]: postfix.service: Unit entered faileransport Agent. Feb 16 18:10:32 ip-172-31-17-191 systemd[1]: postfix.service: Failed with result 'exit-code'. and journalctl -xe resulted in : Code: Feb 16 18:10:58 ip-172-31-17-191 clamd[8350]: SWF support enabled. Feb 16 18:10:58 ip-172-31-17-191 clamd[8350]: HTML support enabled. Feb 16 18:10:58 ip-172-31-17-191 clamd[8350]: XMLDOCS support enabled. Feb 16 18:10:58 ip-172-31-17-191 clamd[8350]: HWP3 support enabled. Feb 16 18:10:58 ip-172-31-17-191 clamd[8350]: Self checking every 3600 seconds. Feb 16 18:11:01 ip-172-31-17-191 cron[1252]: (rkhare4) ORPHAN (no passwd entry) Feb 16 18:11:01 ip-172-31-17-191 cron[1252]: (getmail) RELOAD (crontabs/getmail) Feb 16 18:11:01 ip-172-31-17-191 cron[1252]: (root) RELOAD (crontabs/root) Feb 16 18:11:01 ip-172-31-17-191 CRON[8495]: pam_unix(cron:session): session ope Feb 16 18:11:01 ip-172-31-17-191 CRON[8493]: pam_unix(cron:session): session ope Feb 16 18:11:01 ip-172-31-17-191 CRON[8496]: pam_unix(cron:session): session ope Feb 16 18:11:01 ip-172-31-17-191 CRON[8494]: pam_unix(cron:session): session ope Feb 16 18:11:01 ip-172-31-17-191 CRON[8492]: pam_unix(cron:session): session ope Feb 16 18:11:01 ip-172-31-17-191 CRON[8500]: (rkhare3) CMD (/usr/bin/php /var/ww Feb 16 18:11:01 ip-172-31-17-191 CRON[8501]: (rkhare3) CMD (/usr/bin/php /var/ww Feb 16 18:11:01 ip-172-31-17-191 CRON[8499]: (rkhare3) CMD (/usr/bin/php /var/ww Feb 16 18:11:01 ip-172-31-17-191 CRON[8498]: (root) CMD (/usr/local/ispconfig/se Feb 16 18:11:01 ip-172-31-17-191 CRON[8497]: (root) CMD (/usr/local/ispconfig/se Feb 16 18:11:02 ip-172-31-17-191 CRON[8494]: pam_unix(cron:session): session clo Feb 16 18:11:02 ip-172-31-17-191 CRON[8492]: pam_unix(cron:session): session clo Feb 16 18:11:02 ip-172-31-17-191 CRON[8493]: pam_unix(cron:session): session clo Feb 16 18:11:03 ip-172-31-17-191 CRON[8496]: pam_unix(cron:session): session clo Feb 16 18:11:04 ip-172-31-17-191 CRON[8495]: pam_unix(cron:session): session clo Just for records this is how I tried updating : Code: wget -O ispconfig.tar.gz https://git.ispconfig.org/ispconfig/ispconfig3/repository/archive.tar.gz?ref=stable-3.1 tar xfz ispconfig.tar.gz cd ispconfig3*/install/ php -q update.php Shall the script create a ISPConfig backup in /var/backup/ now? (yes,no) [yes]: no Reconfigure Permissions in master database? (yes,no) [no]: yes Service 'firewall_server' has been detected (currently disabled) do you want to enable and configure it? (yes,no) [no]: no Reconfigure Services? (yes,no,selected) [yes]: yes Configuring Postfix Configuring Dovecot Configuring Spamassassin Configuring Amavisd Configuring Getmail Configuring BIND [INFO] haveged not detected - DNSSEC can fail Configuring Pureftpd Configuring Apache Configuring vlogger Configuring Apps vhost Configuring Jailkit Configuring Database Updating ISPConfig ISPConfig Port [8080]: SPConfig SSL certificate (yes,no) [no]: no Reconfigure Crontab? (yes,no) [yes]: yes Updating Crontab Restarting services ... Job for postfix.service failed because the control process exited with error code. See "systemctl status postfix.service" and "journalctl -xe" for details. Update finished.
The update procedure is fine. Which errors do you get in the file /var/log/maillog when you restart postfix?
Extremely sorry as I saw your reply much later, now its too late for me to post the log. Being a development server and having wasted few days on it, I thought best would be to take a backup and reinstall everything from scratch. That worked and everything is working fine now. Moreover, yesterday I also requested Amazon AWS to remove port 25 throttling (However, as my mail was working fine prior to latest update I rule out port 25 firewall issue. And now no way to find that out as Amazon has permanently lifted port 25 throttling from my account.
This is the first thing to do when you get a vps with Amazon. Have you set up your Reverse DNS in amazon? Generally, this option is configured together throttling removal requests. Regards.
After updating to the new version of ISPConfig i had problem too. It appeared that ports of amavis in config files have been changed by ISPC. So postfix couldn't connect to amavis. I fixed that by editing /etc/amavisd/amavisd.conf and changing setting: $inet_socket_port = [10024,10026]; # listen on this local TCP port(s) So the main.cf file (postfix) is corresponding correctly to it (content_filter = amavis:[127.0.0.1]:10024).
New ports have been added in amavis and postfix configuration (master.cf), they are required for dkim signing. By setting them back to the old values, you disabled DKIM on your system, so emails can not be signed anymore.
Too bad i didn't know that. Well, this is one of the problem of whole open source. New things are coming, but there is no mentioning what they do in config files. I done that, because i didn't update amavis config while updating ISPC, just postfix. So just after restarting services, mail system didn't work, so i have to find what is wrong. So i just find out ports are wrong, and make it working like before. But it is also giving me another question. Many times when i upgrade ISPC i make it do not touch config files. The reason is, there are many custom options i use in config files of amavis/postfix/apache. Sometimes ISPC include options that i use, but with different arguments (for example SSL ciphers used in Apache SSL). Is there any way, that i can make such custom arguments for specific software (apache/postfix etc.) that will be always used as default, even after ISPC is upgraded and add them in own ways? Like reading them before putting into config files, and use my own arguments, not the default from installer. For me every upgrade of ISPC is a big mess.
