[jboss-jira] [JBoss JIRA] Closed: (JBMAIL-42) STMP/POP/IMAP over HTTP/REST

STMP/POP/IMAP over HTTP/REST ---------------------------- Key: JBMAIL-42 URL: http://jira.jboss.com/jira/browse/JBMAIL-42 Project: JBoss Mail ** Closed - moved to http://buni.org ** Issue Type: Feature Request Components: SMTP, POP Reporter: Andrew Oliver Priority: Critical Original Estimate: 2 days Remaining Estimate: 2 days Develop an HTTP Proxy which allows one to tunnel HTTP to SMTP or POP. Example: C: GET /SMTP/Connect HTTP/1.1 C: S: HTTP/1.1 200 OK S: Set-Cookie: JSESSIONID=440CF11A9AB5B28872380A333659F4C1; Path=/ S: Content-Type: text/html;charset=UTF-8 S: Content-Length: xxx S: Date: Thu, 17 Mar 2005 15:22:33 GMT S: Server: Apache-Coyote/1.1 S: S: 220 set.superlinksoftware.com SMTP Server (JBMAIL SMTP Server version 0.1) ready March 17, 2005 10:00:36 AM EST Connection closed (not necessary for 1.1 but demonstrative) C: GET /SMTP/EHLO HTTP/1.1 C: Keep-Alive: 300^M C: Connection: keep-alive^M C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M C: S: HTTP/1.1 200 OK S: Content-Type: text/html;charset=UTF-8 S: Content-Length: xxx S: Date: Thu, 17 Mar 2005 15:22:33 GMT S: Server: Apache-Coyote/1.1\ S: S: 334 VXNlcm5hbWU6 C: GET /SMTP/AUTH_LOGIN HTTP/1.1 C: Keep-Alive: 300^M C: Connection: keep-alive^M C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M C: S: HTTP/1.1 200 OK S: Content-Type: text/html;charset=UTF-8 S: Content-Length: xxx S: Date: Thu, 17 Mar 2005 15:22:33 GMT S: Server: Apache-Coyote/1.1\ S: S: 334 VXNlcm5hbWU6 S: C: POST /SMTP/AUTH_LOGIN HTTP/1.1 C: Keep-Alive: 300^M C: Connection: keep-alive^M C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M C: Content-Type: application/x-www-form-urlencoded C: C: {encoded user} S: S: HTTP/1.1 200 OK S: Content-Type: text/html;charset=UTF-8 S: Content-Length: xxx S: Date: Thu, 17 Mar 2005 15:22:33 GMT S: Server: Apache-Coyote/1.1\ S: S: 334 UGFzc3dvcmQ6 S: C: POST /SMTP/AUTH_LOGIN HTTP/1.1 C: Keep-Alive: 300^M C: Connection: keep-alive^M C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M C: Content-Type: application/x-www-form-urlencoded C: C: {encoded pwd} S: S: HTTP/1.1 200 OK S: Content-Type: text/html;charset=UTF-8 S: Content-Length: xxx S: Date: Thu, 17 Mar 2005 15:22:33 GMT S: Server: Apache-Coyote/1.1\ S: S: 200 Authorized S: C: POST /SMTP/MAIL_FROM HTTP/1.1 C: Keep-Alive: 300^M C: Connection: keep-alive^M C: Cookie: JSESSIONID=63C8CC3E206426A2F24183422D6EF4E4^M C: Content-Type: application/x-www-form-urlencoded C: C: <me(a)nowhere.com&gt; the intent is the "proxy" will be implemneted as a servlet and connect to port 25 on the "real" mail server. All submitted data can be based on HTTP POSTS. All requests should be valid HTTP. (so urlencode and do parm1=&lt;me(a)nowhere.com&gt; if its not valid to pass just a key with no value) The Session ID is the key to the open connection from the proxy. In the event the connection from the proxy to real mail server closes then an invalid session error should be returned to the client.