[GH-ISSUE #452] Proposal: Deprecate POP3 support if no one steps up to maintain it #370

Closed
opened 2026-02-25 21:34:52 +03:00 by kerem · 10 comments
Owner

Originally created by @marclaporte on GitHub (Feb 2, 2021).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/452

Originally assigned to: @jasonmunro on GitHub.

We have multiple issues with POP3:
https://github.com/jasonmunro/cypht/labels/pop3

Clearly, it's not working very well.

Our energy should be on the present and the future, not the past. We should focus on making IMAP rock stable. I see no reason to use POP3. Please someone explain to me the use case.

And then, get JMAP rock stable:
https://github.com/jasonmunro/cypht/issues/180

And then, with any remaining energy, support EWS:
https://github.com/jasonmunro/cypht/issues/247

Now, I know there are some POP3 users and fans. This is your time to step up and say "I will help". We need coders. If you can't code, we need someone to lead a fundraising campaign so we can hire coders.

I propose to give community members 2 months to come up with a plan. In the absence of one, we mark POP3 issues / code / etc. as deprecated. And in the issues, we indicate that we are looking for help. If no one steps up by 2021-12-31, we remove all POP3 related code from Cypht.

Thoughts?

Originally created by @marclaporte on GitHub (Feb 2, 2021). Original GitHub issue: https://github.com/cypht-org/cypht/issues/452 Originally assigned to: @jasonmunro on GitHub. We have multiple issues with POP3: https://github.com/jasonmunro/cypht/labels/pop3 Clearly, it's not working very well. Our energy should be on the present and the future, not the past. We should focus on making IMAP rock stable. I see no reason to use POP3. Please someone explain to me the use case. And then, get JMAP rock stable: https://github.com/jasonmunro/cypht/issues/180 And then, with any remaining energy, support EWS: https://github.com/jasonmunro/cypht/issues/247 Now, I know there are some POP3 users and fans. This is your time to step up and say "I will help". We need coders. If you can't code, we need someone to lead a fundraising campaign so we can hire coders. I propose to give community members 2 months to come up with a plan. In the absence of one, we mark POP3 issues / code / etc. as deprecated. And in the issues, we indicate that we are looking for help. If no one steps up by 2021-12-31, we remove all POP3 related code from Cypht. Thoughts?
kerem 2026-02-25 21:34:52 +03:00
  • closed this issue
  • added the
    pop3
    label
Author
Owner

@jasonmunro commented on GitHub (Feb 9, 2021):

I agree. If we end up removing it I might archive in its own repo with the hope someone someday wants to revisit :)

<!-- gh-comment-id:775681792 --> @jasonmunro commented on GitHub (Feb 9, 2021): I agree. If we end up removing it I might archive in its own repo with the hope someone someday wants to revisit :)
Author
Owner

@marclaporte commented on GitHub (Feb 10, 2021):

I removed POP3 issues from blockers to release 1.2:
https://github.com/jasonmunro/cypht/projects/2

<!-- gh-comment-id:776489799 --> @marclaporte commented on GitHub (Feb 10, 2021): I removed POP3 issues from blockers to release 1.2: https://github.com/jasonmunro/cypht/projects/2
Author
Owner

@kmpoppe commented on GitHub (Mar 9, 2021):

There might, for some VERY strange reason, Mx providers that will not allow IMAP but only POP3 ... Even though they'd deserve a good slap!

Are you seeking to remove the support for POP3 completely to get it out of the current repo? If so, would it make sense to build a new repo that supplies a module that would enable POP3 again - but can be supported without touching the main repo?

Just my 2 cents.

K

<!-- gh-comment-id:794478404 --> @kmpoppe commented on GitHub (Mar 9, 2021): There might, for some VERY strange reason, Mx providers that will not allow IMAP but only POP3 ... Even though they'd deserve a good slap! Are you seeking to remove the support for POP3 completely to get it out of the current repo? If so, would it make sense to build a new repo that supplies a _module_ that would enable POP3 again - but can be supported without touching the main repo? Just my 2 cents. K
Author
Owner

@marclaporte commented on GitHub (Mar 9, 2021):

Mostly, I want to align expectations with reality. If we don't expect to have brainpower to maintain a feature, we should remove it, or tag it as experimental (help wanted).

<!-- gh-comment-id:794596669 --> @marclaporte commented on GitHub (Mar 9, 2021): Mostly, I want to align expectations with reality. If we don't expect to have brainpower to maintain a feature, we should remove it, or tag it as experimental (help wanted).
Author
Owner

@henrique-borba commented on GitHub (Apr 5, 2021):

I agree. I don't think we must call it "experimental" because in my perspectice it seems like it is a kind of early stage feature that WILL be updated. I recommend to just call it deprecated for a future release and just give it a deprecation deadline.

I know some people still use POP3 but honestly, it is an outdated old protocol that most people will avoid.

<!-- gh-comment-id:813647455 --> @henrique-borba commented on GitHub (Apr 5, 2021): I agree. I don't think we must call it "experimental" because in my perspectice it seems like it is a kind of early stage feature that WILL be updated. I recommend to just call it deprecated for a future release and just give it a deprecation deadline. I know some people still use POP3 but honestly, it is an outdated old protocol that most people will avoid.
Author
Owner

@marclaporte commented on GitHub (Apr 6, 2021):

+1 for "deprecated"

<!-- gh-comment-id:814467882 --> @marclaporte commented on GitHub (Apr 6, 2021): +1 for "deprecated"
Author
Owner

@Master0ne commented on GitHub (May 23, 2021):

+1 for getting rid of POP3 support entirely. Away with the cruft for developers to be able to concentrate on more important stuff.

<!-- gh-comment-id:846542995 --> @Master0ne commented on GitHub (May 23, 2021): +1 for getting rid of POP3 support entirely. Away with the cruft for developers to be able to concentrate on more important stuff.
Author
Owner

@marclaporte commented on GitHub (Feb 28, 2023):

RFC 9899 IMAP v POP
https://www.youtube.com/watch?v=NAkAMDeo_NM&t=468s

<!-- gh-comment-id:1447524232 --> @marclaporte commented on GitHub (Feb 28, 2023): RFC 9899 IMAP v POP https://www.youtube.com/watch?v=NAkAMDeo_NM&t=468s
Author
Owner

@marclaporte commented on GitHub (Sep 11, 2023):

So upcoming Cypht 1.5 will no longer have POP support.

<!-- gh-comment-id:1713004046 --> @marclaporte commented on GitHub (Sep 11, 2023): So upcoming Cypht 1.5 will no longer have POP support.
Author
Owner

@marclaporte commented on GitHub (Oct 4, 2025):

Google Is Ending Gmailify and POP Support
https://slashdot.org/story/447452

<!-- gh-comment-id:3367777657 --> @marclaporte commented on GitHub (Oct 4, 2025): Google Is Ending Gmailify and POP Support https://slashdot.org/story/447452
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/cypht#370
No description provided.