On Fri, 20 Oct 2006, Mark Clarkson wrote:
"/" means use names from the filesystem root. I doubt very much that is
what you want.
After more reading am I right in saying that "/" could be used if I was using
the "black box mode"?
In black box mode, "/" is the mail store root. What you want for your
prefix is the location of your mail.
That should either be the empty string, meaning your UNIX home directory,
or perhaps a subdirectory name followed by / (e.g., "mail/" if you put
your mail in the ~/mail subdirectory).
I still can't figure out how to
get Outlook and Evolution working with the default uw-imap configuration. I
know it can be done, and that it's probably simple but I can't see it.
I don't know anything about Evolution. But as a start for Outlook, try
the most minimal configuration first. I avoid using Outlook for mail; I
tried it once many years ago and found it to be highly unsatisfactory.
The only thing I can think of is that I have the wrong namespace. I am under
the impression now however that using uw-imap as-is, with no changes to the
source and no extra c-client.conf or .imaprc, that a user's home directory
will be the mail store.
That impression is correct.
When I issue a namespace command
by running imapd under my username I get:
* NAMESPACE (("" "/")("#mhinbox" NIL)("#mh/" "/")) (("~" "/")) (("#shared/"
"/")("#ftp/" "/")("#news." ".")("#public/" "/"))
,so a valid namespace for me would be "" or "~"?
The empty string is indeed what you want.
I want to get uw-imap working in it's default configuration first before
trying any other fancier ones, but would I be right in saying that other
configurations may be more compatible with the more popular email clients and
this could be the root of my problem, or does it sound more like I have
messed something up?
I don't know. One problem is hidden configuration changes that you don't
know about. Third party redistributions of UW imapd tend to "fix" the
default configuration for UW imapd to be something else, and they neglect
to tell you what they "fixed" it to.
I have also heard of clients which try to guess from the greeting message
what server implementation it is, and then magically adjust their behavior
to "fix" things for that that server.
Needless to say, such "fixes" invariably are site-specific and break on
other sites.
If you can, see if you can get an IMAP protocol transcript from your
client so we can see what the client is doing. That's often the most
helpful thing in diagnosing what may be going on.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
