Have setup a CentOS 5.5 with IPSConfig that has been running for maybe 6 months, it was only intended to be a web server for multiple domains. Issue now is that a web developer has created a form that he is trying to email from the site, I did not have anything configured for mail and he does not care to write a script that would not require the mail service to be on the web server.

Have configured/reconfigured main.cf multiple times but no success.

Postfix appears to send the outbound email to the queue but never goes out. Have setup mail service for the domain "land***.com" in ISPConfig and tested with a single user created for the domain from the server.

What did I miss in the configuration to get "connection refused"?

Nov 2 11:27:19 WC01 postfix/cleanup[6711]: E4DFA1190011: message-id=<20101102162712.E4DFA1190011@WC01.nors***.com>
Nov 2 11:27:19 WC01 postfix/qmgr[6665]: E4DFA1190011: from=<admin@land***.com>, size=377, nrcpt=1 (queue active)
Nov 2 11:27:19 WC01 postfix/smtp[6713]: connect to 127.0.0.1[127.0.0.1]: Connection refused (port 10024)
Nov 2 16:27:19 WC01 postfix/smtp[6713]: E4DFA1190011: to=<admin@nors***.com>, relay=none, delay=17, delays=17/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]: Connection refused)
Nov 2 11:27:22 WC01 postfix/smtpd[6669]: disconnect from wc01.land***.com[69.***.***.161]

Any ideas, should I remove the domain from mail services and would postfix work on its own on a server with ISPConfig?

Looks like you have some kind of content filter there (Amavis??) and it is refusing the connections. {is down||not installed etc}.

Without seeing your main.cf and your master.cf it's impossible to say. The output of would help people here to help you.

2 members found this post helpful.

# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
body_checks = regexp:/etc/postfix/body_checks
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
header_checks = regexp:/etc/postfix/header_checks
html_directory = no
inet_interfaces = all
mail_owner = postfix
mailbox_size_limit = 0
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
message_size_limit = 0
mime_header_checks = regexp:/etc/postfix/mime_header_checks
mydestination = $myhostname, localhost, localhost.localdomain, $mydomain
mydomain = land***.com
myhostname = WC01.nors***.com
mynetworks = 127.0.0.0/8, 69.***.***.0/24
mynetworks_style = host
myorigin = $mydomain
nested_header_checks = regexp:/etc/postfix/nested_header_checks
newaliases_path = /usr/bin/newaliases.postfix
proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
receive_override_options = no_address_mappings
relay_domains = mysql:/etc/postfix/mysql-virtual_relaydomains.cf
relay_recipient_maps = mysql:/etc/postfix/mysql-virtual_relayrecipientmaps.cf
relayhost =
sample_directory = /usr/share/doc/postfix-2.3.3/samples
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options =
smtpd_client_restrictions = check_client_access mysql:/etc/postfix/mysql-virtual_client.cf
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, check_recipient_access mysql:/etc/postfix/mysql-virtual_recipient.cf, reject_unauth_destination
smtpd_sasl_auth_enable = yes
smtpd_sasl_authenticated_header = yes
smtpd_sasl_path = private/auth
smtpd_sasl_type = dovecot
smtpd_sender_restrictions = check_sender_access mysql:/etc/postfix/mysql-virtual_sender.cf
smtpd_tls_cert_file = /etc/postfix/smtpd.cert
smtpd_tls_key_file = /etc/postfix/smtpd.key
smtpd_tls_security_level = may
smtpd_use_tls = yes
transport_maps = proxy:mysql:/etc/postfix/mysql-virtual_transports.cf
unknown_local_recipient_reject_code = 550
virtual_alias_domains =
virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf
virtual_gid_maps = static:5000
virtual_mailbox_base = /var/vmail
virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql-virtual_domains.cf
virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql-virtual_mailboxes.cf
virtual_transport = dovecot
virtual_uid_maps = static:5000

It was the content filter, now I need to know of any issues with me just remarking out the line referencing the amavis to get the email to work or should I just go ahead and spend some time to fix the amavis issue?

I originally intended the server to be only for web hosting and not be configured as an email server. For some reason this web developer did not want to use a script to send the form like another developer uses. Anyway, we just try to make everyone happy.

Well Amavis-New is kind of a mixed bag. It passes email to be scanned for Viruses and Spam (usually) via CLAMAV & SpamAssassin. It also takes care of quarantining mail and has some additional rules and features.

Personally I don't like it as when I have used it in large scale production mail servers, I found it to be flaky. OTOH, it has its lovers and it appears in the widely sold Barracuda spam filtering device.

If your server is just being used to send email then I would not really bother with Amavis. If, on the other hand, you go into hosting inbound mail and want to offer spam & virus filtering that would be the time to get it working.