I have setup a moderated mailing list in Mercury 4.91 with 2 moderators. Listmembers are able to send to the list and should get their own replies. I just tested the list with my member address and Mercury started working the list. And than came the strange and buggy part: The sender was not my member address The From address was formed of the 2 moderators email address. It created a total mess.

MercuryE log:
T 20230424 212520 64473626 Begin processing job MO000016 from address1@sasktel.net address2@yorktondigital.ca
T 20230424 212523 64473626 Established ESMTP connection to 69.49.101.234
T 20230424 212523 64473626 MAIL FROM:<address1@sasktel.net address2@yorktondigital.ca> SIZE=1368
E 20230424 212523 64473626 553 5.1.3 <address1@sasktel.net address2@yorktondigital.ca>... Invalid route address
T 20230424 212523 64473626 Connection closed normally.

I can't see any wrong settings in my list configuration which could cause such behavior. I have 2 lists with 130/150 users.
Years ago with Mercury 4.01 I did not have such problem.

Any pointers would be appreciated.

Johannes

There may be some clues in the MercuryS log, please have a look and see if you can locate the corresponding entry where the list post is received.

Hi Rolf,

the corresponding MercuryS entry gives no clue. here it is. Luckily I can access them over the internet.

T 20230424 212507 64473636 Connection from 192.168.200.34
T 20230424 212507 64473636 EHLO webmail-client.yorktondigital.ca
T 20230424 212507 64473636 AUTH PLAIN
T 20230424 212507 64473636 MAIL FROM:submittername@yorktondigital.ca
T 20230424 212507 64473636 RCPT TO:listname@yorktondigital.com
T 20230424 212507 64473636 DATA
T 20230424 212507 64473636 DATA - 32 lines, 981 bytes.
T 20230424 212507 64473636 QUIT
T 20230424 212507 64473636 Connection closed with 192.168.200.34, 0 sec. elapsed.

BUT I can confirm that Version 4.91 has a serious bug in the handling from mailing lists. How: I do have a second install of Mercury at a different location, it is 4.8, as it is still on XP as an internal setup.

I created a test list with the exact same settings and it is working fine. What I found is, that Mercury is sending From (internall handling) in 3 ways the list emails:
1: using the FIRST moderator email in the moderator list
2: if no moderator is set, using the error handling email
3: if neither of both is set, it is using the submitter's email

The receipient will see only the submitter email. So much for the handling of the internals of Mercury, which you propably know already. I just mentioned it for completeness. I had to get my head around this, as I was not used to it from my old system.

Now to the bug in 4.91
I have 2 moderator and 2 error email set. Both are the same for moderator and error handling. Mercury is sending FROM (internally) with BOTH emails as ONE email. That is clearly shown in MercuryE log above. Or additional here which shows it better

T 20230425 091912 64474e62 Begin processing job MO000049 from <>
T 20230425 091912 64474e63 Begin processing job MO000048 from <>
T 20230425 091912 64474e64 Begin processing job MO000047 from <>
T 20230425 091912 64474e65 Begin processing job MO000046 from <>
T 20230425 091912 64474e66 Begin processing job MO000045 from <>
T 20230425 091912 64474e67 Begin processing job MO000044 from <>
T 20230425 091912 64474e68 Begin processing job MO000043 from <>
T 20230425 091912 64474e69 Begin processing job MO000042 from <>
T 20230425 091912 64474e6a Begin processing job MO000041 from <>
T 20230425 091912 64474e6b Begin processing job MO000040 from <>
E 20230425 091912 64474e62 Permanent error 11001 (non-existent host or domain) resolving 'sasktel.net admin@yorktondigit'.
E 20230425 091912 64474e63 Permanent error 11001 (non-existent host or domain) resolving 'sasktel.net admin@yorktondigit'.
E 20230425 091912 64474e64 Permanent error 11001 (non-existent host or domain) resolving 'sasktel.net admin@yorktondigit'.
E 20230425 091912 64474e65 Permanent error 11001 (non-existent host or domain) resolving 'sasktel.net admin@yorktondigit'.
E 20230425 091912 64474e66 Permanent error 11001 (non-existent host or domain) resolving 'sasktel.net admin@yorktondigit'.
E 20230425 091912 64474e67 Permanent error 11001 (non-existent host or domain) resolving 'sasktel.net admin@yorktondigit'.

Without my 4.8 install on a different location to which I can point to (DNS) for the particular domain, I would not be able to use the mailing lists in Mercury.

Johannes

Tested this with a similar setup (a newly created tiny mailing list with 2 members and 1 moderator) and got this result:

T 20230426 022345 640a427f Job MO000FD0 processing complete.
T 20230426 022639 640a4280 Begin processing job MO000FD3 from rolf@domain1.se
T 20230426 022641 640a4280 Established ESMTP connection to 64.233.161.27
T 20230426 022641 640a4280 MAIL FROM:rolf@domain1.se SIZE=611
T 20230426 022641 640a4280 250 2.1.0 OK u30-20020a056512041e00b004eff38a6713si1824911lfk.398 - gsmtp
T 20230426 022641 640a4280 RCPT TO:rolf@domain2.se
T 20230426 022641 640a4280 250 2.1.5 OK u30-20020a056512041e00b004eff38a6713si1824911lfk.398 - gsmtp
T 20230426 022641 640a4280 Connection closed normally.
T 20230426 022641 640a4280 Job MO000FD3 processing complete.

With or without a moderator assigned the poster's address was used in MAIL FROM.

The only noticeable difference in settings was that the Fanout option wasn't used (set to 1).

Hi Rolf,

after your post (thank you for looking into this) I did some further testing with mailinglists in Mercury 4.91 and got a positive result. Here are the findings.

As mentioned above in regards to the internal handling of Mercury, as soon as an email is set for the error handling, this email is used to send out the emails submitted by a list member. No matter if a moderator is set or not.

Now to my problem:
I had, and still will have, set 2 emails for error handling. If both emails will get the error messages has to be seen.
If 2 emails for error handling are listed, they have to be listed in a certain way, if not, it will produce such error, as I had listed in the MercuryE log and sending out will not work.

The working format is:
email1, email2
email1, "empty space" email2 is working and email1 is used for sending. The receiver will still see the original submitter to the mailing list, as mentioned in my previous post.

The format which is wrong and which I had entered and produces the error is:
email1 email2, that is email1 "empty space" email2
It seems that Mercury is reading this as one email

I am happy that the mailing list is working now and I don't have to use the other instance.
Learned something new.

Johannes