Hi,

I'm trying to get postfix-2.5.5 and amavisd-new-2.3.3 working together
with two postfix instances, /etc/postfix and /etc/postfix-out. I'm
receiving the following error:

Aug 16 18:05:05 smtp01 postfix/error[1655]: 07C7335815B:
to=<j...@example.com>, relay=none, delay=1152,
delays=1152/0.07/0/0.02, dsn=4.3.0, status=deferred (mail transport unavailable)

I believe this is a problem with the first instance, and its inability
to communicate with amavisd, correct? netstat shows me the following:

# netstat -tapn | egrep '10024|10025|25'
tcp        0      0 127.0.0.1:25              0.0.0.0:*
LISTEN      3161/master
tcp        0      0 64.XX.XX.23:25           0.0.0.0:*
LISTEN      3046/master
tcp        0      0 64.XX.XX.22:25           0.0.0.0:*
LISTEN      3046/master
tcp        0      0 127.0.0.1:10024         0.0.0.0:*
LISTEN      781/amavisd (master
tcp        0      0 127.0.0.1:10025         0.0.0.0:*
LISTEN      3161/master

Is it necessary to have another IP other than loopback to do this
properly? I had this working properly with a much older version of
postfix, but the upgrade killed it so I'm starting over.

I have inet_interfaces in the first instance configured to be the two
23 and 22 addresses on the 64 network, and in the second instance it
is configured to 127.0.0.1. Connecting to loopback on ports 25, 10024,
and 10025 using telnet are successful. This happens with currently
queued messages as well as new incoming messages.

I have the filter defined in main.cf in the first instance:

content_filter = smtp-amavis:[127.0.0.1]:10024

I have the smtp-amavis filter defined in master.cf in the second instance:

smtp-amavis unix -      -       n       -       2 smtp
        -o smtp_data_done_timeout=1200
        -o smtp_send_xforward_command=yes
        -o disable_dns_lookups=yes
        -o max_use=20

127.0.0.1:10025        inet  n       -       y       -       -       smtpd
        -o content_filter=
        -o local_recipient_maps=
        -o relay_recipient_maps=
        -o cleanup_service_name=cleanup2
        -o myhostname=localhost
        -o mynetworks=127.0.0.0/8
        -o smtpd_restriction_classes=
        -o smtpd_client_restrictions=
        -o smtpd_helo_restrictions=
        -o smtpd_sender_restrictions=
        -o smtpd_recipient_restrictions=permit_mynetworks,reject

cleanup2       unix    n       -       y       -       0       cleanup
        -o header_checks=pcre:/etc/postfix/header_checks_out
        -o mime_header_checks=
        -o nested_header_checks=
        -o body_checks=
        -o canonical_maps=
        -o sender_canonical_maps=
        -o recipient_canonical_maps=
        -o masquerade_domains=
        -o content_filter=

Could this have something to do with my transport maps? I have a few listed:

# The 22 address
alex.example.com smtp:[127.0.0.1]:10024

# The 23 address
susan.example.com smtp:[127.0.0.1]:10024

# Probably covers everything, so the above really isn't necessary?
*       smtp:[127.0.0.1]:10024

example.com       smtp:[127.0.0.1]:10024
.example.com      smtp:[127.0.0.1]:10024

Some of the examples and documentation I have read use lmtp instead of
smtp. Why would someone choose one over the other?

I hope someone has some ideas of what to do next...
Thanks,
Alex

Reply via email to