Hi everybody,
I have some questions regarding IMAP.
First, it seems that RFC 3501 is missing the definition of 'CHAR'.
More precisely, in RFC 2060 I found that
QUOTED_CHAR ::= any TEXT_CHAR except quoted_specials / \ quoted_specials
TEXT_CHAR ::= any CHAR except CR and LF
CHAR
At 2003-08-27 12:53:21 +0900, [EMAIL PROTECTED] wrote:
First, it seems that RFC 3501 is missing the definition of 'CHAR'.
I think it defers to the definition in RFC 2234 (ABNF) for this and some
other terminals (CR, LF, DIGIT, etc.).
B1 SEARCH CHARSET UTF-8 TEXT 0x80 ?
(Mozilla 1.4 is
Marcel Crasmaru writes:
Hi everybody,
I have some questions regarding IMAP.
First, it seems that RFC 3501 is missing the definition of 'CHAR'.
CHAR is defined in RFC2234, which defines the grammar used in RFC 3501
(and most other RFCs, but not RFC 2060). It's a seven-bit US-ASCII
value
I want to change the default folder locations to
$home/imap/. I have read the CONFIG file and it
seems to indicate that I will need to change a
file in the source and recompile and that I will
need to do this for every sercurity update or
patch that comes out.
Is there no way to change this
Thanks for the reply.
Using a config file would be fine. However, to say
that there is as much chance of getting a config file
wrong completly misses the point.
You only have to get the config file right once and
it would stay that way through any upgrade. If I have
to change the source file each
On Wed, 27 Aug 2003, William O'Shea wrote:
You only have to get the config file right once and
it would stay that way through any upgrade.
Actually, that isn't true; or rather, that has historically not been the
case with imapd.
There is an unsupported config file capability. There is a way
Resurrecting a badly beaten horse...
Is there any interest in having NTLM authentication (as a SASL mech and
possibly as an HTTP mech) documented as an Informational RFC? I believe
I have enough existing documentation (Eric Glass'
http://davenport.sourceforge.net/ntlm.html being the best) and
