Kim Sunggun via Mailman-users writes:
Have you set any of those to other than default in your Django settings? everything is default.
What we're doing is not relevant because we're not trying to connect to your MTA. Some of us do because our MTAs expect authentication or are running on a different port for some reason. Many of us don't because our MTAs use the defaults too, at least for local connections.
The question *you* need to figure out is why won't your MTA talk to Django *at all*? Any number of reasons, in approximate order of when they arise in the connection process:
- You can't get there from here because of a firewall (very unlikely on localhost).
- The MTA isn't listening on that port at that address. The port might work at a different address, another port might work at that address, or maybe both are different. As Mark recommended, check the Mailman configuration at [mta]. If it says anything about smtp_host or smtp_port, use those in your Django configuration too. If it doesn't, they default to 127.0.0.1:25 or localhost:25, and the Django defaults should be OK.
- The MTA is listening for IPv6 (eg, [::1]). If you specify "localhost", maybe it automatically tries IPv6, but maybe it doesn't. If Django is assuming 127.0.0.1, it won't try [::1].
- The MTA expects mandatory TLS (usually port = 465).
- The MTA expects negotiated TLS (STARTTLS), mostly on port 589 but some sites require it on port 25.
- The MTA expects authentication in TLS initialization (don't ask me, I've never set this up). I don't recall whether generic SASL applies here, although I know you can use X.509 certificates. (SASL is the authentication protocol that most MTAs use *after* the connection is established, but you aren't getting that far.)
I wouldn't be surprised if there are other possible issues, but that's enough for now. ;-)
Your MTA logs should show that there was a connection attempt at the right time from the right host (probably localhost), and give the point at which the connection failed and maybe a reason why. If there's nothing at all in the MTA log, the problem is #1 above.