Recipient address rejected: User unknown in virtual alias table; from=<hit@options.org> to=<atm@alist.net>
This is from the transport table. All Mailman3 aliases show up there. I suppose the actual problem could be further down stream and the error might be somewhat bogus. But, I gotta go with the error I got.
The working lists I created with the current software. This one I imported from mailman2. Everything in the mailman3 interface looks normal. Import seemed OK. Aliases obviously created. Half a dozen for each list. Web searches don’t show much.
First entry is the log entry. At least the only part that looked relevant.
The second entry is from the transport section and it looks the same as the ones created with a new list. This seems to have nothing to do with alias. Transport seems to bypass that.
There is something different with the imported list. I’m asking the fine folks at Mailman now. My gut feeling is Postfix is reporting back what it was told. Mailman 3 log is showing a connect and then disconnect.
Mailman3 has an smpt log so it would appear to get this far:
Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) recip: atm@alist.net Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) Data: b'DATA' Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) Data: b'QUIT' Mar 02 10:14:13 2023 (1242405) ('127.0.0.1', 56410) connection lost Mar 02 10:14:13 2023 (1242405) Connection lost during _handle_client() Mar 02 10:53:13 2023 (1242405) Available AUTH mechanisms: LOGIN(builtin) PLAIN(builtin)
That’s why I’m leaning towards it not really being Postfix now. Been ‘learning’ over half a day on this one. But, I was in the process of digging this all out to post on their site. I’ll see what happens.
The initial domain, which worked, didn’t have a generic some.domain
That evidently wildcards. The domains I will be using mailman for won’t really have other email addresses so I can remove that from the virtual table.
