[GH-ISSUE #144] POP3 mail parser isn't same as IMAP mail parser, and POP3 mail parser's implementation is incompleted #119

New issue

Closed

opened 2026-02-25 21:34:12 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 21:34:12 +03:00

Owner

Originally created by @hiroshitoda on GitHub (Oct 30, 2016).
Original GitHub issue: https://github.com/cypht-org/cypht/issues/144

Originally assigned to: @jasonmunro on GitHub.

I think that POP3 mail data structure is same as IMAP's one.
But in Cypht, POP3 mail parser isn't same as IMAP's one, and POP3 mail parser's implementation is incompleted.
Because of this, POP3 mail parser cannot parse some mail data which is parsable with IMAP mail parser.

Originally created by @hiroshitoda on GitHub (Oct 30, 2016). Original GitHub issue: https://github.com/cypht-org/cypht/issues/144 Originally assigned to: @jasonmunro on GitHub. I think that POP3 mail data structure is same as IMAP's one. But in Cypht, POP3 mail parser isn't same as IMAP's one, and POP3 mail parser's implementation is incompleted. Because of this, POP3 mail parser cannot parse some mail data which is parsable with IMAP mail parser.

kerem

2026-02-25 21:34:12 +03:00

closed this issue
added the
pop3
label

kerem commented

2026-02-25 21:34:12 +03:00

Author

Owner

@hiroshitoda commented on GitHub (Oct 30, 2016):

So I make pull request #147 for fix POP3 parser in makeshift.

@hiroshitoda commented on GitHub (Oct 30, 2016): So I make pull request #147 for fix POP3 parser in makeshift.

kerem commented

2026-02-25 21:34:13 +03:00

Author

Owner

@jasonmunro commented on GitHub (Oct 31, 2016):

Thank you for working on this! You are correct, POP3 and IMAP use different code paths for E-mail structure. The reason for this is because IMAP provides the BODYSTRUCTURE command that we can use to parse a message without having to download the entire thing. So basically we offload message parsing to the IMAP server itself. The POP3 protocol does not have this functionality, so we have no choice but to parse it ourselves, and as you noticed our implementation is incomplete.

I will test and merge your pull request to improve POP3 parsing this week. Thanks again!

@jasonmunro commented on GitHub (Oct 31, 2016): Thank you for working on this! You are correct, POP3 and IMAP use different code paths for E-mail structure. The reason for this is because IMAP provides the BODYSTRUCTURE command that we can use to parse a message without having to download the entire thing. So basically we offload message parsing to the IMAP server itself. The POP3 protocol does not have this functionality, so we have no choice but to parse it ourselves, and as you noticed our implementation is incomplete. I will test and merge your pull request to improve POP3 parsing this week. Thanks again!

kerem commented

2026-02-25 21:34:13 +03:00

Author

Owner

@jasonmunro commented on GitHub (Nov 1, 2016):

Pull request is merged. Thanks again!

@jasonmunro commented on GitHub (Nov 1, 2016): Pull request is merged. Thanks again!