So near, and yet so far (Configuring Mailman)
Hello all,
I've spent more time than I care to admit trying to configure Mailman. And I almost have it all working now, but I just can't seem to get my Mailman/Postfix combo to receive emails.
When I try to send emails to lists I'm rebuffed with undelivered notices with:
<testlist@lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found and: <testlist@lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists.fiftyshadesof.green type=MX: Host not found, try again
This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that:
lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. lists.fiftyshadesof.green. 0 IN A 193.37.35.191
I have driven myself mad with this and would very much appreciate any advice anyone can offer.
Many thanks! Jack
On 1/29/21 9:01 AM, Jack Lenox via Mailman-users wrote:
Hello all,
I've spent more time than I care to admit trying to configure Mailman. And I almost have it all working now, but I just can't seem to get my Mailman/Postfix combo to receive emails.
When I try to send emails to lists I'm rebuffed with undelivered notices with:
<testlist@lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found and: <testlist@lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists.fiftyshadesof.green type=MX: Host not found, try again
This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that:
lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. lists.fiftyshadesof.green. 0 IN A 193.37.35.191
I have driven myself mad with this and would very much appreciate any advice anyone can offer.
It appears this is strictly a Postfix issue. I.e. it is rejecting the incoming mail. There are a few things to consider.
Have you restarted Postfix? I don't offhand remember details, but Postfix keeps its own internal notion of some things (not sure if DNS is among them).
Beyond that, what does postconf -n report and for things in that that
reference Mailman stuff, what's in the referenced files?
And, what's in /var/log/mail.log when you send to testlist@lists.fiftyshadesof.green?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 1/29/2021 12:01 PM, Jack Lenox via Mailman-users wrote:
Hello all,
I've spent more time than I care to admit trying to configure Mailman. And I almost have it all working now, but I just can't seem to get my Mailman/Postfix combo to receive emails.
When I try to send emails to lists I'm rebuffed with undelivered notices with:
<testlist@lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found and: <testlist@lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists.fiftyshadesof.green type=MX: Host not found, try again
This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that:
lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. lists.fiftyshadesof.green. 0 IN A 193.37.35.191
I have driven myself mad with this and would very much appreciate any advice anyone can offer.
The key here isn't in your mailman config, or even your postfix config (you might be able to fix it there, I'm not sure). The key is in the error:
<testlist@lists.fiftyshadesof.green>: Host or domain name not found. Name service error for name=lists type=AAAA: Host not found
Specifically, type=AAAA. It's looking for an IPv6 host record and you don't have one. I'm going to guess you got that bounce not from your lists host, rather from your mail relay? Somewhere along the way something is trying to use IPv6 and needs to get kicked to either not do that or at least fall back to IPv4.
-- Joel Lord
On 30 January 2021 4:01:02 am LHDT, Jack Lenox via Mailman-users <mailman-users@mailman3.org> wrote:
Hello all,
This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that:
lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. lists.fiftyshadesof.green. 0 IN A 193.37.35.191
Why is the timeout on the names zero?
When looking them up they'll always come up as expired and invalid.
If you have static IP assignments I suggest setting the timeout to 86400 rather than zero. If you're on a system that changes up address more frequently, then 300 (five minutes) may be more appropriate.
Sent from my Android device with K-9 Mail. Please excuse my brevity.
On 2021-01-29 19:52, Peter Chubb wrote:
On 30 January 2021 4:01:02 am LHDT, Jack Lenox via Mailman-users <mailman-users@mailman3.org> wrote:
Hello all,
This to me appears to be an issue with my DNS settings, but I can't work this out either. I have an A record for lists.fiftyshadesof.green pointing at my server, and an MX record pointing at that:
lists.fiftyshadesof.green. 0 IN MX 0 lists.fiftyshadesof.green. lists.fiftyshadesof.green. 0 IN A 193.37.35.191
Why is the timeout on the names zero?
When looking them up they'll always come up as expired and invalid.
If you have static IP assignments I suggest setting the timeout to 86400 rather than zero. If you're on a system that changes up address more frequently, then 300 (five minutes) may be more appropriate.
Thank you Pete, that's strange. The TTL is set to 86400 seconds. That might have just been a peculiarity of dig when I ran it.
Good news everyone! I've got it working. It turns out my issue was with the mynetwork IP settings in my Postfix config. Things do now appear to be working. My only remaining issue is that the posts aren't appearing in the archive. Hmm.
On 1/29/21 3:52 PM, Jack Lenox via Mailman-users wrote:
Good news everyone! I've got it working. It turns out my issue was with the mynetwork IP settings in my Postfix config. Things do now appear to be working.
Good. Thanks for the update.
My only remaining issue is that the posts aren't appearing in the archive. Hmm.
If you want our help with that, tell us if you have any non-default [archiver.*] settings in mailman.cfg and what the list's Settings -> Archiving settings are.
If you are expecting HyperKitty archiving, are messages remaining queued in Mailman's var/archives/hyperkitty/spool/ directory and if so, what kind of errors do you see in Django's log?
Does the value for MAILMAN_ARCHIVER_KEY in your Django settings match the api_key in the [general] section of the mailman-hyperkitty.cfg (or whatever you call it), quoted in MAILMAN_ARCHIVER_KEY but not in api_key, and is the base_url setting in the [general] section of the mailman-hyperkitty.cfg a URL that can actually access hyperkitty?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (5)
-
j＠cklenox.earth -
Jack Lenox
-
Joel Lord -
Mark Sapiro -
Peter Chubb