[ 
https://issues.apache.org/jira/browse/NUTCH-1861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593916#comment-16593916
 ] 

Yossi Tamari commented on NUTCH-1861:
-------------------------------------

Hi Lewis,

I have a some questions:
 # Isn't SMTP only for sending (and relaying) messages? How can it be used for 
crawling?
 # I assume crawling in this instance will be in the context of a specific user 
(with password), but this user may have access to multiple mailboxes/folders 
(at least with IMAP, I don't think POP3 supports such features). Do you intend 
to support multiple users/passwords?
 # Why did you choose Commons Net over 
[JavaMail|https://javaee.github.io/javamail/]? Is it a license issue? I think 
the implementation would be much easier with JavaMail (it is a much 
higher-level API, I believe).

Regarding your question, I suspect that any users will only be using one 
protocol or the other, so putting them in one plugin is only useful if there is 
a lot of common logic in the implementation (which may be the case). Personally 
I would only consider IMAP (maybe) worth implementing, as I think all servers 
support it today, and POP3 is just too limited.

> Implement POP3 Protocol
> -----------------------
>
>                 Key: NUTCH-1861
>                 URL: https://issues.apache.org/jira/browse/NUTCH-1861
>             Project: Nutch
>          Issue Type: Task
>          Components: protocol
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>
> Implementing the Post Office Protocol within Nutch would open up a new use 
> case which is crawling and indexing of some mail servers.
> This is particularly useful for investigation purposes or for porting/mapping 
> mail from one server to another. 
> We *may* be able to kil two bird with the one stone by implementing both IMAP 
> and POP3 protocols under the one plugin.
> http://commons.apache.org/proper/commons-net/



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to