December 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBMAIL-153) Headless install in the installer is broken.

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-153?page=all ] Andrew Oliver closed JBMAIL-153. -------------------------------- Fix Version/s: (was: 1.0-RC1) Resolution: Won't Fix Assignee: (was: Andrew Oliver) > Headless install in the installer is broken. > -------------------------------------------- > > Key: JBMAIL-153 > URL: http://jira.jboss.com/jira/browse/JBMAIL-153 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Bug > Affects Versions: 1.0-RC1 > Environment: Installer > Reporter: Aron Sogor > > After completeing the install on the last screen creat automatic install script. > Use the the script with the installer "java -jar install.jar <your savedscript>. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-143) Task management

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-143?page=all ] Andrew Oliver closed JBMAIL-143. -------------------------------- Fix Version/s: (was: 1.0-RC1) Resolution: Won't Fix Assignee: (was: Aron Sogor) > Task management > --------------- > > Key: JBMAIL-143 > URL: http://jira.jboss.com/jira/browse/JBMAIL-143 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Sub-task > Affects Versions: 1.0-M5 > Reporter: Aron Sogor > Priority: Optional > > Enable adding TODO tasks into the system. > TODO task has name/dec/create and due dates and priority. > This exist but no ICal entry exposed. > Needs some input/idea/design how to make this really usefull. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-132) refactor mailist stuff.

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-132?page=all ] Andrew Oliver closed JBMAIL-132. -------------------------------- Fix Version/s: (was: 1.0-RC1) Resolution: Won't Fix Assignee: (was: Andrew Oliver) > refactor mailist stuff. > ----------------------- > > Key: JBMAIL-132 > URL: http://jira.jboss.com/jira/browse/JBMAIL-132 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Task > Affects Versions: 1.0-RC1 > Reporter: Andrew Oliver > > presently built on hibernate, move to ejb3 stuff. Fix the Unit tests, add some adminstrative stuff for them. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-133) Can't build and run under IBM SDK

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-133?page=all ] Andrew Oliver closed JBMAIL-133. -------------------------------- Resolution: Won't Fix Assignee: (was: Andrew Oliver) > Can't build and run under IBM SDK > --------------------------------- > > Key: JBMAIL-133 > URL: http://jira.jboss.com/jira/browse/JBMAIL-133 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Task > Components: SMTP, POP, IMAP > Affects Versions: 1.0-M4 > Environment: All Linux distributions running IBM SDK 1.4 and 1.5. > This will also be observed on all platforms not running a Sun SDK > Reporter: Ulrich Romahn > > The SSL support of all three protocols (IMAP, POP, SMTP) will not be working on a non-Sun SDK. > The "offending" line is: > java.security.Security.addProvider( new com.sun.net.ssl.internal.ssl.Provider()); > and is located in the following three files: > - org.jboss.mail.imap4.handlers.CmdSTARTTLS.java > - org.jboss.mail.smtp.handlers.CmdSTARTTLS.java > - org.jboss.mail.pop3.handlers.CmdSTLS > This should be changed, if possible. > I am working on a possible solution. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-134) Mail with header and no body hangs SMTP connection until timeout

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-134?page=all ] Andrew Oliver closed JBMAIL-134. -------------------------------- Fix Version/s: (was: 1.0-RC1) Resolution: Won't Fix Assignee: (was: Andrew Oliver) > Mail with header and no body hangs SMTP connection until timeout > ---------------------------------------------------------------- > > Key: JBMAIL-134 > URL: http://jira.jboss.com/jira/browse/JBMAIL-134 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Bug > Components: SMTP > Affects Versions: 1.0-M4, 1.0-M5 > Reporter: Andrew Oliver > Original Estimate: 5 hours > Remaining Estimate: 5 hours > > " > From: here\r\n > To: there\r\n > Subject: empty message\r\n > \r\n > \r\n.\r\n > " > (only escape characters are intended as line feeds, actual line feeds added for visual effect) > The above will cause M4 to hang a connection until timeout (life). We need to handle empty bodies somehow. This is going to be some work to trace down due to how bad MailHeadersImpl.java has spaghettiized. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-130) clusterize locks table

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-130?page=all ] Andrew Oliver closed JBMAIL-130. -------------------------------- Fix Version/s: (was: 1.0-RC1) Resolution: Won't Fix Assignee: (was: Andrew Oliver) > clusterize locks table > ---------------------- > > Key: JBMAIL-130 > URL: http://jira.jboss.com/jira/browse/JBMAIL-130 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Feature Request > Components: POP > Affects Versions: 1.0-RC1 > Reporter: Andrew Oliver > > Locks table needs to have some kind of instance id and the thread id. Locks should be deleted or at runtime if they are from the same instance upon startup and if that thread is known to be gone and from the owning instance. Meaning if server A owns the lock and the same user connects to server A, server A can check the thread pool and see if the same thread ID is still in existence with the same userID. . . IF not then the lock can be safely ignored/deleted. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-142) ICalendar export/import

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-142?page=all ] Andrew Oliver closed JBMAIL-142. -------------------------------- Fix Version/s: (was: 1.0-RC1) Resolution: Won't Fix Assignee: (was: Aron Sogor) > ICalendar export/import > ----------------------- > > Key: JBMAIL-142 > URL: http://jira.jboss.com/jira/browse/JBMAIL-142 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Sub-task > Affects Versions: 1.0-RC1 > Reporter: Aron Sogor > > Import ICAL/VCAL via WebDAV( fancy way to say Http PUT/GET). Sunbird/Firfox/ThunderBird/Mozilla Calendar, Mac ICal(I think needs checking) and OSAF Chandler all share caldars over webdav, by uploading their file via an http put and getting/refreshing their caledar with an HTTP GET. > Enable exporting users calendar hence meaning user's invites to ICal/VCal format. > - Each entry exported useing GUIDs for each calendar entry. > - if the entry cancelled do not export it. > Parse the uploaded Ical with Ical4j and compare each entry (ID by GUID): > -if the GUID not found the entry is new create a personal event as organizer and invite itself. > -if the GUID known comapre each field if that has changed, if needed update entry* > -if GUID found but event canceled do nothing. > * according the ical spec if the event changes they should/could change the version/sequence attribute. That is not done by Mozilla. > if there is a version/sequence attribute compare it with current version, if it is a stale/old record skip the update. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-106) Allow pass-through authentication relaying

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-106?page=all ] Andrew Oliver closed JBMAIL-106. -------------------------------- Resolution: Won't Fix Assignee: (was: Andrew Oliver) > Allow pass-through authentication relaying > ------------------------------------------ > > Key: JBMAIL-106 > URL: http://jira.jboss.com/jira/browse/JBMAIL-106 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Feature Request > Reporter: Andrew Oliver > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Users should be able to configure their accounts to: > allow them to connect with security tokens (user/password). > automatically relay their outgoing emails through another mail server which JBMS will pass the authentication tokens to (passthrough) or > pass a defined set of authentication tokens > This will require either an enveloping or stamping concept on top of mail that defines more about how the mail should be processed. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-118) Support SMTP over POP for user authentication

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-118?page=all ] Andrew Oliver closed JBMAIL-118. -------------------------------- Resolution: Won't Fix Assignee: (was: Andrew Oliver) > Support SMTP over POP for user authentication > --------------------------------------------- > > Key: JBMAIL-118 > URL: http://jira.jboss.com/jira/browse/JBMAIL-118 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Sub-task > Components: SMTP, POP > Reporter: Andrew Oliver > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Support requiring users to authenticate with POP before SMTP. -- 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

19 years, 7 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBMAIL-113) Allow administrator to require a key strength

by Andrew Oliver (JIRA)

[ http://jira.jboss.com/jira/browse/JBMAIL-113?page=all ] Andrew Oliver closed JBMAIL-113. -------------------------------- Resolution: Won't Fix Assignee: (was: Andrew Oliver) > Allow administrator to require a key strength > --------------------------------------------- > > Key: JBMAIL-113 > URL: http://jira.jboss.com/jira/browse/JBMAIL-113 > Project: JBoss Mail ** Closed - moved to http://buni.org ** > Issue Type: Feature Request > Components: SMTP, POP, Security > Affects Versions: 1.0-RC1 > Reporter: Andrew Oliver > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Presently useSSL and TLS does not require any particular key strength or support of any particular key strength on the part of the client. We should allow the administrator to restrict SSL to a minimum strength. -- 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

19 years, 7 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2006