No I am not confusing inbound and outbound and for this I'm only
concerned about inbound and actually only on ports 10024-26 that are for
lack of a better way to put it a customization.
-Curt
postconf -Mf
smtp inet n - n - - smtpd
submission inet n - n - - smtpd
-o syslog_name=postfix/submission
-o smtpd_tls_security_level=encrypt
-o smtpd_sasl_auth_enable=yes
pickup fifo n - n 60 1 pickup
cleanup unix n - n - 0 cleanup
qmgr fifo n - n 300 1 qmgr
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
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
postlog unix-dgram n - n - 1 postlogd
scan unix - - n - 10 smtp
:10026 inet n - n - 10 smtpd
-o content_filter=
-o local_recipient_maps=
-o relay_recipient_maps=
-o myhostname=filter.mynetwork.local
-o smtpd_helo_restrictions=
-o smtpd_client_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks=127.0.0.0/8
-o smtpd_use_tls=no
-o smtp_use_tls=no
spamtnsp unix - n n - - local
-o alias_maps=lmdb:/etc/aliaases
On 6/29/24 01:26, Peter via Postfix-users wrote:
On 29/06/24 18:09, Curtis J Blank via Postfix-users wrote:
I don't know how many times now I have said this but I will day it
again.
I have postfix set up to only listen on/use 127.0.0.1 *not* ::1.
What postfix listens on is irrelevant, this has to do with which IP
postfix connects to spampd with.
And. I am not using spamd, it listens on port 783. I am using spampd
which shows up as perl because is it written in perl and it listens
on 10025.
Okay, but that does not change things.
Here is the proof:
new:/etc/postfix # netstat -putan |grep -e ^Active -e ^Proto -e
127\.0\.0\.1\: -e \:\:1\:
This shows nothing of interest, except that perl is only listening on
127.0.0.1 which we already knew because you changed that setting just
now.
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2360/cupsd
tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN 2441/spamd
tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN
5063/amavisd (maste
tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN 13980/perl
tcp6 0 0 ::1:783 :::* LISTEN 2441/spamd
tcp6 0 0 ::1:631 :::* LISTEN 2360/cupsd
tcp6 0 0 ::1:10024 :::* LISTEN 5063/amavisd
(maste
udp 0 0 127.0.0.1:323 0.0.0.0:* 2399/chronyd
udp 0 0 127.0.0.1:659 0.0.0.0:* 2580/rpc.statd
udp6 0 0 ::1:323 :::* 2399/chronyd
new:/etc/postfix #
So you said " Ideally you want to either configure postfix to never
try to connect to ::1 (but only connect to 127.0.0.1)".
That is one of two possible solutions that I proposed.
That is what I want and I've been saying all along that that is how I
have it configured. Unless I'm totally not understanding something
here...
You are confusing outbound connections with inbound (listening)
connections. You are also confusing what different settings do. It is
obvious that postfix is configured to connect to ::1 because it *is*
attempting to connect to ::1. Postfix does not go against its
configuration.
content_filter = scan:[127.0.0.1]:10025
This is the setting that controls the connection, but it's connecting
through the scan: service which is defined in master.cf. As
previously requested, please show the output of:
postconf -Mf
Peter
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
_______________________________________________
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
