[JBoss JIRA] Closed: (JBMAIL-47) SMTP Client Proxy
by Andrew Oliver (JIRA)
[ http://jira.jboss.com/jira/browse/JBMAIL-47?page=all ]
Andrew Oliver closed JBMAIL-47.
-------------------------------
Resolution: Won't Fix
Assignee: (was: Andrew Oliver)
> SMTP Client Proxy
> -----------------
>
> Key: JBMAIL-47
> URL: http://jira.jboss.com/jira/browse/JBMAIL-47
> Project: JBoss Mail ** Closed - moved to http://buni.org **
> Issue Type: Sub-task
> Reporter: Andrew Oliver
>
> The SMTP client proxy mimic's a real SMTP Server however it translates the requests into the HTTP requests expected by:
> http://jira.jboss.com/jira/browse/JBMAIL-42
> Expectations:
> 1. It issues the http://servername/SMTP/CONNECT on initial connection from the client and returns the greeting from HTTP SMTP proxy which in turn is just returning the real server's greeting. From then on the jsessionid is associated with THIS connection to the client.
> 2. It hangs up on the client if it gets an invalid session from the server (avoid having to smartly implement the protocols to reconnect to a return to state and leave it up to the client to do that).
> 3. Server proxy is "locked down" to connect to only one host or set of hosts (so you can't use this to launch a distributed denial of service attack against a third party, sorry)
> Possiblities:
> 1. Could be a protocol implementation for JBoss Mail's framework that simply uses something like Jakarta Commons HTTPClient to issue commands to the server proxy. Thus you run parts of JBoss AS and JBMailServer on client and server.
> 2. This could be dumbly implemented to support ANY protocol if some standardization on the SERVER Proxy and Client Proxy can be thought of.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Closed: (JBMAIL-46) POP Client Proxy
by Andrew Oliver (JIRA)
[ http://jira.jboss.com/jira/browse/JBMAIL-46?page=all ]
Andrew Oliver closed JBMAIL-46.
-------------------------------
Resolution: Won't Fix
Assignee: (was: Andrew Oliver)
> POP Client Proxy
> ----------------
>
> Key: JBMAIL-46
> URL: http://jira.jboss.com/jira/browse/JBMAIL-46
> Project: JBoss Mail ** Closed - moved to http://buni.org **
> Issue Type: Sub-task
> Reporter: Andrew Oliver
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> The POP client proxy mimic's a real POP Server however it translates the requests into the HTTP requests expected by:
> http://jira.jboss.com/jira/browse/JBMAIL-42
> Expectations:
> 1. It issues the http://servername/POP/CONNECT on initial connection from the client and returns the greeting from HTTP Pop proxy which in turn is just returning the real server's greeting. From then on the jsessionid is associated with THIS connection to the client.
> 2. It hangs up on the client if it gets an invalid session from the server (avoid having to smartly implement the protocols to reconnect to a return to state and leave it up to the client to do that).
> 3. Server proxy is "locked down" to connect to only one host or set of hosts (so you can't use this to launch a distributed denial of service attack against a third party, sorry)
> Possiblities:
> 1. Could be a protocol implementation for JBoss Mail's framework that simply uses something like Jakarta Commons HTTPClient to issue commands to the server proxy. Thus you run parts of JBoss AS and JBMailServer on client and server.
> 2. This could be dumbly implemented to support ANY protocol if some standardization on the SERVER Proxy and Client Proxy can be thought of.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months
[JBoss JIRA] Closed: (JBMAIL-42) STMP/POP/IMAP over HTTP/REST
by Andrew Oliver (JIRA)
[ http://jira.jboss.com/jira/browse/JBMAIL-42?page=all ]
Andrew Oliver closed JBMAIL-42.
-------------------------------
Resolution: Won't Fix
Assignee: (was: Andrew Oliver)
> 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>
> 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=<me(a)nowhere.com> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
17 years, 9 months