# POP3 Authentication with CRAM-MD5

**URL:** <https://meta.discourse.org/t/pop3-authentication-with-cram-md5/47697>\
**Category:** Product Support\
**Created:** [23 يوليو 2016، 9:46م UTC](https://meta.discourse.org/t/pop3-authentication-with-cram-md5/47697 "2016-07-23T21:46:17Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [24 يوليو 2016، 11:37م UTC](https://meta.discourse.org/t/pop3-authentication-with-cram-md5/47697/2 "2016-07-24T23:37:52Z")

</div>

I think you’re doomed this time. I can’t even find support for CRAM-MD5 in the `Net::POP3` class which Discourse uses, let alone any way to configure it within Discourse. As an added bonus, there don’t appear to be a thundering herd of alternate POP3 libraries for Ruby which we could switch to to provide CRAM-MD5 support.

Short of you doing a lot of coding to add CRAM-MD5 support to `Net::POP3`, and providing a patch to Discourse to add a tickbox to use that support, I think you’re out of luck here.

Alternately, do you have the ability to forward e-mails sent to your incoming address(es) to another MTA? I’m on the hook for a blog post (and associated docker container) about how to do direct-delivery incoming e-mail (obviating the need for POP3 polling at all); if that would work for you, I’ll get that post out ASAP and you can switch to that.

---

_[View the full topic](https://meta.discourse.org/t/pop3-authentication-with-cram-md5/47697)._