eclipse-ee4j / eclipse-ee4j/angus-mail

Add FAQ entry for "Got bad greeting from SMTP host"

Open
#134 0 comments 0 reactions 0 assignees View on GitHub
documentation good first issue
Dominant language
Java
Stars
87
Forks
23
PR merge metrics
No merged PRs in 30d

Description

Per https://github.com/eclipse-ee4j/angus-mail/issues/109 the error seen was:
````
[07-09-2023 18:46:26][AP-Web][WARN] Details: Got bad greeting from SMTP host: localhost, port: 465, response: [EOF]
[07-09-2023 18:46:26][AP-Web][WARN] Type: jakarta.mail.MessagingException
[07-09-2023 18:46:26][AP-Web][WARN] Stacktrace:
[07-09-2023 18:46:26][AP-Web][WARN] org.eclipse.angus.mail.smtp.SMTPTransport.openServer(SMTPTransport.java:2231)
[07-09-2023 18:46:26][AP-Web][WARN] org.eclipse.angus.mail.smtp.SMTPTransport.protocolConnect(SMTPTransport.java:729)
[07-09-2023 18:46:26][AP-Web][WARN] jakarta.mail.Service.connect(Service.java:345)
[07-09-2023 18:46:26][AP-Web][WARN] jakarta.mail.Service.connect(Service.java:225)
[07-09-2023 18:46:26][AP-Web][WARN] jakarta.mail.Service.connect(Service.java:246)
[07-09-2023 18:46:26][AP-Web][WARN] jakarta.mail.Transport.send0(Transport.java:230)
[07-09-2023 18:46:26][AP-Web][WARN] jakarta.mail.Transport.send(Transport.java:152)
````

Setting `mail.smtp.ssl.enable=true` fixed the issue.

1. Add a [FAQ entry](https://github.com/eclipse-ee4j/angus-mail/blob/master/www/FAQ.html) for `Got bad greeting from SMTP host: , port: , response: [EOF]`
2. Add some details explaining that the server most likely expected an SSL connection instead of TLS.
3. Explain that the resolution is to add `mail.smtp.ssl.enable=true` and remove `mail.smtp.starttls.enable=true`

Contributor guide

Open the contributing guide

Research direction

Start with www/FAQ.html and review the linked Angus Mail issue 109 for context. Add an FAQ entry for the exact "Got bad greeting from SMTP host" response, explaining that the server likely expects SSL rather than TLS. Done means documenting the ssl.enable setting and removing the starttls.enable setting.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.