How does one get access to the actual keyset for the extensions hashmap, only documented methods are getExtensionParameter or supportsExtension?

[KevinDyer-3DS]

I am working on a new mail user/transport agent for our web based applications. It must be able to connect to a myriad of SMTP servers for different customer situations from straight forward SMTP through ESMTP (AUTH, STARTTLS, OAUTH2). I am trying to make the code perform some checks with what is in the EHLO response and realized I do not have a means to access the MailConnection object that is established within the Transport object. I therefore cannot easily access either supportsExtension(String Name) or extensionParameter(String Name) to interrogate what the server said it supports.

Without trying to use reflection how does one provide reasonable feedback on what the server said it supported versus what the program was configured to use? Do I re-implement sendEhlo within my own code, but that is kind of stupid right?

A simple Transport.getMailConnection() method would at least allow developers the ability to access that level of information.

[KevinDyer-3DS]

After I submitted this request I realised there wasn't any way to get all of the parameter names or simply extract the entire extension hashmap from the MailConnection object.

MailConnection connection = Transport.getMailConnection();
String[] ehloParameters = connection.getParameters();

I was looking at MailConnection from org.apache.geronimo.mail.util.MailConnection shipped with TomEE. But if you look at the original SMTPTransport Javadoc for com.sun.mail.smtp.SMTPTransport you will see it only provides for getExtensionParameter(String Name) or supportsExtension(String Ext). You have to know all the possible extensions upfront and your code needs to be updated if/when a new extension is added by vendor X or Y. Or we could update the API document to add a way to at least return all of the current extensions provided by the SMTP server in this session Set getExtensionNames() that returns the keyset for the extensions hashmap. This way the SMTP client has the ability to provide better diagnostics to the user and/or administrator, rather than having to dig into a debug mode or perform a MITM attack to break the SSL traffic to view the actual SMTP traffic.

I reviewed the current Angus code and the SMTPTransport provides the same, only getExtensionParameter or supportsExtension. There is no way for the calling code to retrieve the known extensions from the Angus mail Transport object.

[jmehrens]

What us the fully qualified class name for MailConnection?

Angus-mail has demos for Transport and Stores.

You then have to cast to specific service implementation.