[
https://issues.apache.org/jira/browse/EMAIL-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17935084#comment-17935084
]
Michael Osipov commented on EMAIL-211:
--------------------------------------
I bet that this will be probematic because most SMTP servers will drop the
connection unless you send a command in a short period of time. Yes, TLS
handshake is expensive...
> Add connection pooling
> ----------------------
>
> Key: EMAIL-211
> URL: https://issues.apache.org/jira/browse/EMAIL-211
> Project: Commons Email
> Issue Type: New Feature
> Reporter: Hiran Chaudhuri
> Priority: Major
>
> Congratulations for an easy to use straightforward client library.
> However the application I created spends most of it's time connecting to the
> mailserver. How come?
>
> Apparently the examples on
> [https://commons.apache.org/proper/commons-email/userguide.html] follow this
> pattern:
>
> {code:java}
> Email email = new SimpleEmail();
> ...
> email.addTo("[email protected]"); email.send();
> {code}
> As an effect, in the background it creates a JavaMail Session and Transport,
> uses it to send the email and then forgets about it again. In my environment
> building a connection requires to get an authentication token, then using
> that for secure SMTP. Establishing such a connection takes a few seconds,
> which limits the throughput of sending emails.
>
> Please add a feature (or document how to do if already possible) to reuse
> connections for sending several mails. Also the solution should be thread
> safe so a multithreaded application can send emails in parallel.
>
> I guess this should be easily doable by combining commons-pool and
> commons-email. However my attempts failed miserable, making me want to switch
> to other mail client libraries altogether.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
