# Reply by email SSL self signed certificate error

**URL:** <https://meta.discourse.org/t/reply-by-email-ssl-self-signed-certificate-error/30868>\
**Category:** Support\
**Created:** [2015 年 7 月 7 日午後 6:40 UTC](https://meta.discourse.org/t/reply-by-email-ssl-self-signed-certificate-error/30868 "2015-07-07T18:40:39Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![AstonJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/astonj/32/215041_2.png) [@AstonJ](https://meta.discourse.org/u/AstonJ)\
**Post date:** [2015 年 8 月 12 日午前 11:53 UTC](https://meta.discourse.org/t/reply-by-email-ssl-self-signed-certificate-error/30868/26 "2015-08-12T11:53:00Z")

</div>

Hi Felix, thanks for the reply.

> [@fefrei](#):
>
> With the settings you recommend, any active network attacker can easily man-in-the-middle the connection by presenting another self-signed certificate he created himself.

Could you elaborate on this please? If the mail server is on the same domain and physical server as the client (the Discourse install) how could a network attacker exploit this and present another self-signed cert themselves?

Also I know this is not ideal, so can you think of any way where Discourse can behave like Apple Mail (and most other email clients), where they ask you to trust (and always remember) the certificate when they first come across it? I think that’s what @riking was trying to do in [post 13](https://meta.discourse.org/t/reply-by-email-ssl-self-signed-certificate-error/30868/13) and me in [post 15](https://meta.discourse.org/t/reply-by-email-ssl-self-signed-certificate-error/30868/15).

---

_[View the full topic](https://meta.discourse.org/t/reply-by-email-ssl-self-signed-certificate-error/30868)._