esackbauer By the way, do you remember when you asked me why I used port 587? Well that was from their documentation.
Also, the TLS on port 25 looks like this:
[
{
"cmd": null,
"response": [
{
"code": "220",
"message": "mail.my.domain ESMTP Postcow"
}
]
},
{
"cmd": "EHLO passbolt.my.domain",
"response": [
{
"code": "250",
"message": "mail.my.domain"
},
{
"code": "250",
"message": "PIPELINING"
},
{
"code": "250",
"message": "SIZE 104857600"
},
{
"code": "250",
"message": "ETRN"
},
{
"code": "250",
"message": "STARTTLS"
},
{
"code": "250",
"message": "ENHANCEDSTATUSCODES"
},
{
"code": "250",
"message": "8BITMIME"
},
{
"code": "250",
"message": "DSN"
},
{
"code": "250",
"message": "CHUNKING"
}
]
},
{
"cmd": "STARTTLS",
"response": [
{
"code": "220",
"message": "2.0.0 Ready to start TLS"
}
]
}
]
Doesn’t this mean it just gets a bad response from Mailcow? I mean, cmd=“STARTTLS” and response “ready to start tls”?
I am fairly ass in mail-related stuff so pardon my dummy questions
