Kyriakos Terzopoulos writes:
No more mail being marked as spam. However I face a (hopefully) new problem now. When I mass subscribe the users, they get an initial invitation email. However after replying I get this in the exim logs, the subsequent mails do not arrive and the users are not verified at all:
2023-10-25 13:36:41 1qvbFh-001kcb-Ig <= myname@myproject.eu H=localhost (webmail.myproject.eu) [127.0.0.1] P=esmtpa A=dovecot_login: myname@myproject.eu S=1726 id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu 2023-10-25 13:36:41 1qvbFh-001kcb-Ig == partners@myproject.eu <partners-confirm+6df62cd0f805b2b66b21a43a42ec8ee77487e8ad@myproject.eu> R=mailman3_router T=mailman3_transport defer (-54): retry time not reached for any host for ' myproject.eu'
It looks like 'myname' has replied to the invitation, and was received by this MTA (is it Mailman's MTA?). Then delivery to Mailman was deferred because delivery to ' myproject.eu' has failed, and Exim is queueing them for future delivery, until the next retry time. Try using 'runq' then checking the log to see why mail is failing in the first place.
I do not understand why there are spaces before the host name in these lines:
id=32091a0e12cc23fa988380639a4c44a6@ myproject.eu retry time not reached for any host for ' myproject.eu'
The first never happens in my Exim instance. (I have no instances of "retry time not reached" at all in my logs.) That suggests a misconfiguration, in Exim, in Mailman, or Postorius. You should check the mailman3_router and the mailman3_transport first because they're easier.
Steve