Configuration problems using mlmmj+postfix
Good question,
there is 'something' at port 25, here is the output
sudo netstat -nltp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 490/rpcbind tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 517/sshd tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 1135/master tcp 0 0 0.0.0.0:39048 0.0.0.0:* LISTEN 499/rpc.statd tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 10910/mysqld tcp6 0 0 :::111 :::* LISTEN 490/rpcbind tcp6 0 0 :::80 :::* LISTEN 13443/apache2 tcp6 0 0 :::22 :::* LISTEN 517/sshd tcp6 0 0 :::25 :::* LISTEN 1135/master tcp6 0 0 :::443 :::* LISTEN 13443/apache2 tcp6 0 0 :::56747 :::* LISTEN 499/rpc.statd
Kind regards and thanks
Christian Gleerup
-----Original Message-----
Quoted 30 lines
From: "Morten Shearman Kirkegaard" <[email protected]>
To: [email protected]
Date: 23/11/2015 20:49
Subject: Re: [mlmmj] Configuration problems using mlmmj+postfixHi Christian,
Quoted 7 lines · Christian Gleerup
I have some problems getting mlmmj to send mails out, and I don't know where to look, so I hope you can help me.
I have the following clues
In/var/log/mail.errNov 23 16:00:01 Lists /usr/local/bin/mlmmj-send[21648]:init_sockfd.c:56: Could not connect to 127.0.0.1: Connection refused
By default mlmmj uses 127.0.0.1 as relay host, when sending mails. It appears that you don't have an SMTP server listening there.
Does the following command (assuming you're on Linux) show an SMTP daemon?
$ netstat -nltpKind regards,
Morten
you are right, the port is overridden in
/etc/mlmmj/nyhedsbrev/control/smtpport
the old server must have listened to port 10025.
would you recomend me just changing it to 25? Or should I change postfix and the firewall to listen to 10025
Ohh and one more thing,
when I change the configuration, and the configuration is right so Things start working.
I would like to be sure the old mails are 'not' send, since they are only relevant for one day (newsletter) should I just empty the /var/spool/mlmmj/nyhedsbrev/queue using the commandline or should i use some mlmmj command?
kind regards
Christian Gleerup
-----Original Message-----
Quoted 20 lines
From: "Piotr Auksztulewicz" <[email protected]>
To: [email protected]
Date: 24/11/2015 04:18
Subject: Re: [mlmmj] Configuration problems using mlmmj+postfixQuoted 2 lines · Christian Gleerup
Good question,
there is 'something' at port 25, here is the outputI had a quick look at the code, are you sure you are not overriding the port in the control/smtpport setting for your list? Also, there's a "secret"
MLMMJ_TESTINGenvironment variable which overrrides the port to 10025 :-)Signature · 1 line
Piotr "Malgond" Auksztulewicz [email protected]
Hi Morten,
postfix responds to telnet, so that seems correct. -----Original Message-----
Quoted 21 lines
From: "Morten Shearman Kirkegaard" <[email protected]>
To: [email protected]
Date: 24/11/2015 09:18
Subject: Re: [mlmmj] Configuration problems using mlmmj+postfixHi Christian,
Quoted 2 lines · Christian Gleerup
Good question,
there is 'something' at port 25, here is the output...
Quoted 1 line
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 1135/master
So, Postfix *is* listening on TCP/25. Can you telnet to 127.0.0.1 25 ?
Kind regards,
Morten
Morten and Piotr
I have updated and deleted the emails, now the 'editor' just need to write a new newsletter and see if it is send out.
thank you both for you help.
Kind Regards
Christian Gleerup
-----Original Message-----
Quoted 26 lines
From: "Morten Shearman Kirkegaard" <[email protected]>
To: [email protected]
Date: 24/11/2015 13:48
Subject: Re: [mlmmj] Configuration problems using mlmmj+postfixQuoted 6 lines · Christian Gleerup
you are right, the port is overridden in
/etc/mlmmj/nyhedsbrev/control/smtpportthe old server must have listened to port 10025.
would you recomend me just changing it to 25?Yes, and you can do that by just removing the "smtpport" file.
Quoted 2 lines
should I just empty the
/var/spool/mlmmj/nyhedsbrev/queueusing the commandline or should i use some mlmmj command?The command line is fine.
Kind regards,
Morten