Does a Campaign Manager Integrate with KumoMTA for Tracking and Analytics?

Hi,

I’ve been using KumoMTA for email delivery and am now looking to integrate a campaign management tool that can provide tracking and analytics.

I’m interested in knowing if any campaign manager (either open-source or paid) can work well with KumoMTA for the following needs:

Tracking and analytics for open rates, click-through rates, etc.
Customizable headers to ensure proper campaign tracking
Efficient handling of large email lists and high-speed email processing
Good list management and segmentation features
My goal is to continue using KumoMTA for sending emails while leveraging a campaign manager that offers robust insights and easy integration. I’d appreciate any recommendations or advice on how to achieve this.

Thank you

Essentially any campaign tool that allows for use of arbitrary SMTP should work for your purposes here. One know example is OnGage, which we have tested against and documented integration at Ongage - KumoMTA Docs

I’ve also encountered AllInOneEmail that is similar, and I know Mautic can use a generic SMTP relay.

Also if you’re in production we’d appreciate it if we could add your logo to our user list on the website.

I am encountering an issue with my KumoMTA setup where, after enabling SMTP authentication, the connection successfully authenticates but then disconnects with the error message “Peer Disconnected.” The process begins with a successful connection log entry [10.0.0.0:56774->10.0.0.1:587] 0ns === Connected 2024-09-07 05:19:43.332224048 UTC. The EHLO command is sent at 68ms and responds with 68ms ← 250-test.example.com Aloha localhost. STARTTLS is issued at 136ms with a response 136ms ← 220 Ready to Start TLS. The AUTH PLAIN command is sent at 412ms and receives a 235 2.7.0 AUTH OK! response. However, at 548ms, an error occurs: 548ms === ERROR: Peer Disconnected, and the connection closes: 548ms === Closed. I have checked the SMTP authentication settings, and they appear correct. I have also reviewed network and firewall configurations. Possible issues could include post-authentication restrictions, TLS/SSL problems, or network rule impacts. I would appreciate any advice on further diagnostics or solutions

[10.0.0.0:56774->10.0.0.1:587]   0ns === Connected 2024-09-07 05:19:43.332224048 UTC
[10.0.0.0:56774->10.0.0.1:587]   0ns === conn_meta hostname="test.example.com"
[10.0.0.0:56774->10.0.0.1:587]   0ns === conn_meta received_from="10.0.0.0:56774"
[10.0.0.0:56774->10.0.0.1:587]   0ns === conn_meta received_via="10.0.0.1:587"
[10.0.0.0:56774->10.0.0.1:587]   0ns === conn_meta reception_protocol="ESMTP"
[10.0.0.0:56774->10.0.0.1:587]  48µs <-  220 test.example.com KumoMTA
[10.0.0.0:56774->10.0.0.1:587]  68ms  -> EHLO localhost
[10.0.0.0:56774->10.0.0.1:587]  68ms === smtp_server_ehlo: Ok
[10.0.0.0:56774->10.0.0.1:587]  68ms <-  250-test.example.com Aloha localhost
[10.0.0.0:56774->10.0.0.1:587]  68ms <-  250-PIPELINING
[10.0.0.0:56774->10.0.0.1:587]  68ms <-  250-ENHANCEDSTATUSCODES
[10.0.0.0:56774->10.0.0.1:587]  68ms <-  250 STARTTLS
[10.0.0.0:56774->10.0.0.1:587] 136ms  -> STARTTLS
[10.0.0.0:56774->10.0.0.1:587] 136ms <-  220 Ready to Start TLS
[10.0.0.0:56774->10.0.0.1:587] 344ms  -> EHLO localhost
[10.0.0.0:56774->10.0.0.1:587] 344ms === smtp_server_ehlo: Ok
[10.0.0.0:56774->10.0.0.1:587] 344ms <-  250-test.example.com Aloha localhost
[10.0.0.0:56774->10.0.0.1:587] 344ms <-  250-PIPELINING
[10.0.0.0:56774->10.0.0.1:587] 344ms <-  250-ENHANCEDSTATUSCODES
[10.0.0.0:56774->10.0.0.1:587] 344ms <-  250 AUTH PLAIN
[10.0.0.0:56774->10.0.0.1:587] 412ms  -> AUTH PLAIN
[10.0.0.0:56774->10.0.0.1:587] 412ms <-  334
[10.0.0.0:56774->10.0.0.1:587] 480ms  -> AHByaXlhbnNoAGt1bW9tdGE=
[10.0.0.0:56774->10.0.0.1:587] 480ms === smtp_server_auth_plain: Ok: Bool(true)
[10.0.0.0:56774->10.0.0.1:587] 480ms <-  235 2.7.0 AUTH OK!
[10.0.0.0:56774->10.0.0.1:587] 480ms === conn_meta authn_id="dummyuser"
[10.0.0.0:56774->10.0.0.1:587] 480ms === conn_meta authz_id="dummyuser"
[10.0.0.0:56774->10.0.0.1:587] 548ms === ERROR: Peer Disconnected
[10.0.0.0:56774->10.0.0.1:587] 548ms === Closed


Anything in the syslog?

peer disconnected suggests that the client choose to close the connection

Does this thing affects to my mailing ?

That depends on whether it properly connects on a future connection before the message ages out of the queues.

okay got it