mbentley,

Omada SDN Controller seems to even send a CC to the username set for authentication if authentication is used. That's indeed pretty bad.

What's more, this »hostname« in the EHLO message:

EHLO omada

prevents the MTA from using strict hostname checking setting which is used by mail providers to mitigate against spam mails.

Suggested fix: Omada Controller should let one specify what hostname to use in HELO/EHLO messages.

Fae, please can you add this to the list of bugs? I did report this to support already twice in last two years among other bugs regarding the mail submissions ports (see post #2 in this thread).

Additionally, in SDN controller it's not possible anymore to specify official SMTP submission port 587 and there is no way to send TLS-encrypted mail to port 25 using STARTTLS.

Suggested fixes: Allow the user to define the SMTP port, don't force any port numbers (setting a default is o.k., but it then should be either port 25 or port 587, not port 465). Also don't change the port number if SSL/TSL encryption is selected. We admins know better than Omada Controller what ports our own MTA uses for mail submission.

This should really be fixed, since it violates the SMTP standard.

ASCII, it's really weird. An username for SMTP authentication should never be passed into a Cc: header.

I use something like »omada@localhost« as authentication username – initially used by a controller running on the same sever as the MTA –, which then gets rewritten to »omada@our.full.domain« when seen in Cc: header even if the mail is actually being submitted by an Omada Controller running on a remote site. Of course, this role account has no mailbox at all.

As for username/emailaddr in authentication credentials: are you using SASL? If so, it needs a domain specification (»localhost« or »full.domain«) for certain MTAs.

@R1D2 

Fae, please can you add this to the list of bugs? I did report this to support already twice in last two years among other bugs regarding the mail submissions ports (see post #2 in this thread).

Thanks for your valued feedback and thoughtful suggestions. This has been forwarded to the product department who will evaluate it. Thank you for all.