On 2026-01-19 09:30, BetaRays wrote: > On Mon, Jan 19, 2026 at 08:00:32AM +0100, Jan Eden wrote:
> > This should have resulted in a similar error message as before, since > > the expansion of the list address (testing) does not exist as a local > > user. Instead, I get this error message: > > > > -------------------------------------------------- > > msmtp: recipient address [email protected] not accepted by the server > > msmtp: server message: 524 5.2.4 Mailing list expansion problem: > > <[email protected]> > > -------------------------------------------------- > > > > This does not make any sense to me – how does OpenSMTPD know that > > [email protected] is a mailing list? > > > > - Jan > > “Mailing list expansion problem” is a generic error message when an > address fails to match in a “virtual” I think. > I’ve had this error message without working with mailing lists. > From what I can remember, my issue was that my virtual alias table > had mappings from, e.g. [email protected] to [email protected] > but OpenSMTPD also needs a final mapping from [email protected] to > a local user (which, in my case, is used for lmtp delivery, while > using the last matched address as rcpt-to). > > Maybe enabling tracing and debug logs with smtpctl could help you > understand your issue. Thanks for the suggestion, I found a solution. By adding a mlmmj-receive command to the forwards table – -------------------------------------------------- # /usr/local/etc/mail/forwards testing "|/usr/local/bin/mlmmj-receive -L /var/spool/mlmmj/testing/" [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] -------------------------------------------------- – I can leave the rest of my configuration unchanged: -------------------------------------------------- action "expand_forwards" expand-only virtual <forwards> action "local_mail" lmtp "/var/run/dovecot/lmtp" rcpt-to virtual <virtuals> action "outbound" relay srs helo mail.example.com match from any for rcpt-to <forwards> action "expand_forwards" match from any for rcpt-to <virtuals> action "local_mail" match for local action "local_mail" match from any auth for any action "outbound" match for any action "outbound" -------------------------------------------------- Although this works well, I still wonder whether it is possible to use a "mda" action and a separate match directive for the mailing lists. My previous configuration should have worked (at least in theory), but I must have missed something. - Jan
