Closed Bug 3500 Opened 26 years ago Closed 19 years ago

Initial IMAP interaction

Categories

(Grendel Graveyard :: Protocols, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: grail, Unassigned)

References

Details

Grendel + UW-imap = unhappiness.
Is there anything we can do to make the initial connection to uw-imapd a more
successful event?
Status: NEW → ASSIGNED
I need an imap account on an imup-uw server for that. Can you arrange that?
The solution is to allow for protocol spedific features. In this case a server
root is needed.
Can I just go an add some preferences like 'mail.imap-myserver.serverroot'?

How hard will it be to add these protocol specific preferences to the prefs
dialog using XML ?
Target Milestone: M2
I'll look into this after fixing the prefs UI.
Depends on: 8444
Target milestone?
This is a Grendel bug, not a mozilla bug. We have a different schedule.
How come this is still M2? M2 is out for ages!
Milestone 0.8 has been released. We should either resolve this bug or update its
milestone.
This is no longer an issue as far as I can tell.
We've tested mozilla and thunderbird against uw-imap (the last 5 versions up to
and included 2002e) without any major problems.

How do we get this issue closed as I believe it is resolved.
This is grendel, the java mail/news project. Not thunderbird, nor even mozilla 
mailnews.
Reassigning to nobody@mozilla.org as I'm not working on Grendel anymore.
Assignee: edwin → nobody
Status: ASSIGNED → NEW
According to Comment #9 this bug is solved, no action since.
Can't this bug be closed then?
(In reply to comment #9)
> This is no longer an issue as far as I can tell.
> We've tested mozilla and thunderbird against uw-imap (the last 5 versions up to
> and included 2002e) without any major problems.
> 
> How do we get this issue closed as I believe it is resolved.

(In reply to comment #12)
> According to Comment #9 this bug is solved, no action since.
> Can't this bug be closed then?

As Grendel uses JavaMail I tested the providers against a uw-imap 2004 installation.
The current Sun IMAP provider connects with out a problem, as does the GNU
JavaMail IMAP provider.
Therefore I think the bug should be closed, as it is now working.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.