f I've done that. Both commands did not return anything. So present status is: Can login to roundcube webmail, but inbox is empty. Mails appear to send, and are listed in sent items folder, but do not arrive. Admin mails from the ISPConfig dashboard appear to get sent but do not arrive. Cannot setup a remote client account in Outlook due to "Send test email message: The server responded: 451 4.3.0..." There are quite a lot of files in the postfix folder but not sure where to start looking if postfix is causing the issue. Thank you for your help so far, I feel like we are making progress.
Here is the mail log Nov 9 23:22:31 212-129-10-138 amavis[12138]: (12138-04) Blocked MTA-BLOCKED {TempFailedOpenRelay}, [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected].10.XXX>, mail_id: 9UnbH8hzJBRS, Hits: 0, size: 476, 452 ms Nov 9 23:22:31 212-XXX-10-XXX postfix/smtp[14345]: 864511C8B47: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=201721, delays=201721/0.01/0/0.45, dsn=4.3.0, status=deferred (host 127.0.0.1[127.0.0.1] said: 451 4.3.0 id=12138-04 - Temporary MTA failure on relaying, from MTA(smtp:[127.0.0.1]:10025): 451 4.3.0 Error: queue file write error (in reply to end of DATA command))
Please try this: http://www.faqforge.com/linux/controlpanels/ispconfig2/postfix-queue-file-write-error/
Reset the message max size from 0 to 900000000. Still this in the log (host 127.0.0.1[127.0.0.1] said: 451 4.3.0 id=12129-07 - Temporary MTA failure on relaying, from MTA(smtp:[127.0.0.1]:10025): 451 4.3.0 Error: queue file write error (in reply to end of DATA command))
Code: # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # # Do not forget to execute "postfix reload" after editing this file. # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - n - - smtpd #smtp inet n - n - 1 postscreen #smtpd pass - - n - - smtpd #dnsblog unix - - n - 0 dnsblog #tlsproxy unix - - n - 0 tlsproxy #submission inet n - n - - smtpd # -o syslog_name=postfix/submission # -o smtpd_tls_security_level=encrypt # -o smtpd_sasl_auth_enable=yes # -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=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #smtps inet n - n - - smtpd # -o syslog_name=postfix/smtps # -o smtpd_tls_wrappermode=yes # -o smtpd_sasl_auth_enable=yes # -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=permit_sasl_authenticated,reject # -o milter_macro_daemon_name=ORIGINATING #628 inet n - n - - qmqpd pickup unix n - n 60 1 pickup cleanup unix n - n - 0 cleanup qmgr unix n - n 300 1 qmgr #qmgr unix n - n 300 1 oqmgr 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 # -o smtp_helo_timeout=5 -o smtp_connect_timeout=5 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 # # ==================================================================== # Interfaces to non-Postfix software. Be sure to examine the manual # pages of the non-Postfix software to find out what options it wants. # # Many of the following services use the Postfix pipe(8) delivery # agent. See the pipe(8) man page for information about ${recipient} # and other message envelope options. # ==================================================================== # # maildrop. See the Postfix MAILDROP_README file for details. # Also specify in main.cf: maildrop_destination_recipient_limit=1 # maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient} ${extension} ${recipient} ${user} ${nexthop} ${sender} # # ==================================================================== # # Recent Cyrus versions can use the existing "lmtp" master.cf entry. # # Specify in cyrus.conf: # lmtp cmd="lmtpd -a" listen="localhost:lmtp" proto=tcp4 # # Specify in main.cf one or more of the following: # mailbox_transport = lmtp:inet:localhost # virtual_transport = lmtp:inet:localhost # # ==================================================================== # # Cyrus 2.1.5 (Amos Gouaux) # Also specify in main.cf: cyrus_destination_recipient_limit=1 # #cyrus unix - n n - - pipe # user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m ${extension} ${user} # # ==================================================================== # # Old example of delivery via Cyrus. # #old-cyrus unix - n n - - pipe # flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension} ${user} # # ==================================================================== # # See the Postfix UUCP_README file for configuration details. # #uucp unix - n n - - pipe # flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) # # ==================================================================== # # Other external delivery methods. # #ifmail unix - n n - - pipe # flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) # #bsmtp unix - n n - - pipe # flags=Fq. user=bsmtp argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient # #scalemail-backend unix - n n - 2 pipe # flags=R user=scalemail argv=/usr/lib/scalemail/bin/scalemail-store # ${nexthop} ${user} ${extension} # #mailman unix - n n - - pipe # flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py # ${nexthop} ${user} dovecot unix - n n - - pipe flags=DROhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${user}@${nexthop} amavis unix - - - - 2 smtp -o smtp_data_done_timeout=1200 -o smtp_send_xforward_command=yes 127.0.0.1:10025 inet n - - - - smtpd -o content_filter= -o local_recipient_maps= -o relay_recipient_maps= -o smtpd_restriction_classes= -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o mynetworks=127.0.0.0/8 -o strict_rfc821_envelopes=yes -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks
No, this just forwards the messages to amavis for the spam and antivirus scan. Amavis is listening on port 10024. Please restart amavis and check if it shows any errors in the mail.log file for the restart.
Code: amavis[5297]: (05297-12) Negative SMTP response to data-dot (<[email protected]>): 451 4.3.0 Error: queue file write error, dt: 0.6 ms Code: amavis[5297]: (05297-12) (!)Jo4bEvsCcMXl FWD from <[email protected]> -> <[email protected]>, BODY=7BIT 451 4.3.0 from MTA(smtp:[127.0.0.1]:10025): 451 4.3.0 Error: queue file write error Nov 11 08:19:20 212-129-10-138 amavis[5297]: (05297-12) Blocked MTA-BLOCKED {TempFailedOpenRelay}, [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: Jo4bEvsCcMXl, Hits: 0, size: 550, 452 ms Code: amavis[5297]: (05297-12) Blocked MTA-BLOCKED {TempFailedOpenRelay}, [127.0.0.1] <[email protected]> -> <[email protected]>, Message-ID: <[email protected]>, mail_id: Jo4bEvsCcMXl, Hits: 0, size: 550, 452 ms Might this be a firewall issue?
That's understandable. I have no idea why or how mail would be coming in on port 10025 anyway? It isn't something I set up although I can see it in the master.cf file. I assume I should change this line.. Code: 127.0.0.1:10025 inet n - - - - smtpd EDIT: I've uninstalled postfix and will reinstall.
This should not change your configs... i use the setups from howtoforge quiten often and never had such a problem.
When you reinstalled postfix (with --purge) then you have to run an ispconfig update with reconfigure services afterward
The postfix master.cf has this entry Code: smtp inet n - n - - smtp The 2nd n being chroot. Is this correct?
I found a part I may have not done, in the hosts file Please explain the middle line more clearly, or whether it is unlikely that this omission is causing the 451 4.3.0 error message.
The middle line is the IP of your server followed by the fully qualified hostname of your server followed by the short server hostname. I dont think that this is related to yur issue, but you should correct it anyway. I dont have a centos 7 server here as I only Use Debian and Ubuntu as it causes less problems. On Debian, postfix is chrooted. But this does not mean that it is chrooted on Centos as well, but you can try to change that line, but it might be that you have to alter it for all postfix services then.
