MDaemon Technologies, Ltd.

Scott

3/1/24, 10:15 AM

Hi, I thought I sent this to support via the website but I did not hear anything back so maybe I did something wrong.

With version 23.5.2 we are seeing problems when emails have multiple recipients using custom queues. It looks like Mdaemon is creating its own route slip .rte file for the extra email addresses. It does not do this if there is only one email address.

In my example below using a custom que it overrides the Qroute.rte route of the custom route and ends up sending through mdaemon instead of the custom route set up.

Log example of sending to one email address that works correctly:

Mon 2024-02-26 13:58:18.457: ----------

Mon 2024-02-26 13:58:49.691: REMOTE message: pd5001000000001.msg

Mon 2024-02-26 13:58:49.691: * Session 425; child 0001

Mon 2024-02-26 13:58:49.692: * From: sxxxxxxx@xxxxxxx.com

Mon 2024-02-26 13:58:49.692: * To: aaaaa@gmail.com

Mon 2024-02-26 13:58:49.692: * Subject: This is a test

Mon 2024-02-26 13:58:49.692: * Message-ID: xxxxxxx

Mon 2024-02-26 13:58:49.692: * Size: 2924; <e:\mdaemon\queues\out\pd5001000000001.msg>

Mon 2024-02-26 13:58:49.693: * Queue route slip host: other.host

Mon 2024-02-26 13:58:49.693: * Queue route slip port: 25

Mon 2024-02-26 13:58:49.694: Resolving TXT record for _mta-other.host (DNS Server: 208.67.222.222)...

Mon 2024-02-26 13:58:49.781: No MTA-STS TXT record found

Mon 2024-02-26 13:58:49.781: Resolving MX record for other.host (DNS Server: 208.67.222.222)...

Mon 2024-02-26 13:58:49.869: Attempting SMTP connection to other.host

Mon 2024-02-26 13:58:49.942: Attempting SMTP connection to IPaddress:25

Mon 2024-02-26 13:58:49.943: Waiting for socket connection...

Mon 2024-02-26 13:58:49.997: * Connection established localip:51076 --> IPaddress:25

Mon 2024-02-26 13:58:49.997: Waiting for protocol to start...

…

Message is delivered to other.host that is set up in the custom que as expected. When looking at the custom que files that get created only a .msg file is created and then deleted out of the que after delivery as expected. The log above shows the Queue route slip host correctly and all is good.

Log example of two email addresses that does not work. One email is on the To: line and the other in on the CC:. Both are going to gmail.com. If both are on the To: line it does the same thing.

Tue 2024-02-27 11:31:26.949: REMOTE message: pd5001000000170.msg

Tue 2024-02-27 11:31:26.949: * Session 426; child 0001

Tue 2024-02-27 11:31:26.949: * From: sxxxxxxx@xxxxxxx.com

Tue 2024-02-27 11:31:26.949: * To: [Recipients in RTE file]@xxxxxx.com

Tue 2024-02-27 11:31:26.949: * Subject: Test

Tue 2024-02-27 11:31:26.949: * Message-ID: xxxxxxxx

Tue 2024-02-27 11:31:26.949: * Size: 2871; <e:\mdaemon\queues\out\pd5001000000170.msg>

Tue 2024-02-27 11:31:26.949: * Queue route slip host: other.host

Tue 2024-02-27 11:31:26.949: * Queue route slip port: 25

Tue 2024-02-27 11:31:26.949: * Route slip host: gmail.com

Tue 2024-02-27 11:31:26.950: * Route slip port: 25

Tue 2024-02-27 11:31:26.951: MTA-STS policy for gmail.com found in cache

Tue 2024-02-27 11:31:26.951: * version: STSv1

Tue 2024-02-27 11:31:26.951: * mode: enforce

Tue 2024-02-27 11:31:26.951: * mx: gmail-smtp-in.l.google.com

Tue 2024-02-27 11:31:26.951: * mx: *.gmail-smtp-in.l.google.com

Tue 2024-02-27 11:31:26.951: * max_age: 86400

Tue 2024-02-27 11:31:26.962: Resolving MX record for gmail.com (DNS Server: 208.67.222.222)...

Tue 2024-02-27 11:31:26.988: * P=005 S=000 D=gmail.com TTL=(3) MX=[gmail-smtp-in.l.google.com]

Tue 2024-02-27 11:31:26.988: * P=010 S=001 D=gmail.com TTL=(3) MX=[alt1.gmail-smtp-in.l.google.com]

Tue 2024-02-27 11:31:26.988: * P=020 S=002 D=gmail.com TTL=(3) MX=[alt2.gmail-smtp-in.l.google.com]

Tue 2024-02-27 11:31:26.988: * P=030 S=003 D=gmail.com TTL=(3) MX=[alt3.gmail-smtp-in.l.google.com]

Tue 2024-02-27 11:31:26.988: * P=040 S=004 D=gmail.com TTL=(3) MX=[alt4.gmail-smtp-in.l.google.com]

Tue 2024-02-27 11:31:26.988: Attempting SMTP connection to gmail-smtp-in.l.google.com

Tue 2024-02-27 11:31:26.988: Resolving A record for gmail-smtp-in.l.google.com (DNS Server: 208.67.222.222)...

Tue 2024-02-27 11:31:27.033: * D=gmail-smtp-in.l.google.com TTL=(5) A=[142.250.1.27]

Tue 2024-02-27 11:31:27.033: Attempting SMTP connection to 142.250.1.27:25

…

You will notice that in this example the email ends up leaving out of the mdaemon local server and not the custom que at all. It ignores that que route completely. I noticed while watching the que directory that it creates its won .rte file and a .msg file. This only happens when there are two different recipients.

Scott