On Friday, 15 October 1999 at 12:06, Raju K V wrote:
> hi,
>
> like you, I am also not familiar with locale issues. But i did some
> checking and I found that the LANG environment variable is set to "C".
> also I wrote a test program which uses the SKIPWS macro from protos.h in
> mutt source code
On Fri, Oct 15, 1999 at 12:06:08PM +0530, Raju K V wrote:
> BTW, I notice that whenever I access the mailserver using IMAP, a mail
> Mail System Internal Data DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL
> DATA
> gets created. Why?
>
Yes, it's a pain in the *** in my opinion. Apparently it's cr
hi,
like you, I am also not familiar with locale issues. But i did some
checking and I found that the LANG environment variable is set to "C".
also I wrote a test program which uses the SKIPWS macro from protos.h in
mutt source code and it works fine. It works fine. So I feel that it is
not a loc
On Thursday, 14 October 1999 at 12:50, Edmund GRIMLEY EVANS wrote:
> > > mutt_socket_write():a0004 FETCH 1:5 (FLAGS INTERNALDATE RFC822.SIZE
>BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
>IN-REPLY-TO REPLY-TO)])
> > > mutt_socket_read_line_d():* 1 FETCH (FL
> > mutt_socket_write():a0004 FETCH 1:5 (FLAGS INTERNALDATE RFC822.SIZE
>BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE
>IN-REPLY-TO REPLY-TO)])
> > mutt_socket_read_line_d():* 1 FETCH (FLAGS () INTERNALDATE "12-Oct-1999 11:18:49
>+0530" RFC822.SIZE 2865 BOD
On Tuesday, 12 October 1999 at 10:18, Raju K V wrote:
> hi,
>
> I am attaching the .muttdebug0 which I got after running mutt -d4. The
> password has been blanked out.
[SNIP]
> mutt_socket_write():a0004 FETCH 1:5 (FLAGS INTERNALDATE RFC822.SIZE
>BODY.PEEK[HEADER.FIELDS (DATE FROM SUBJECT TO CC
hi,
I am attaching the .muttdebug0 which I got after running mutt -d4. The
password has been blanked out.
Mutt 1.0pre3i started at Tue Oct 12 10:16:18 1999
.
Debugging at level 4.
mutt_alloc_color(): Color pairs used so far: 1
mutt_alloc_color(): Color pairs used so far: 2
mutt_alloc_color(): C
On Monday, 11 October 1999 at 19:02, Raju K V wrote:
> hi,
>
> I had reported this problem previously, but received no satisfactory
> answer. I usually read mails after popping them from the mail server.
> Since the server's POP support is not reliable, I thought of using IMAP.
> when I change fo
hi,
I had reported this problem previously, but received no satisfactory
answer. I usually read mails after popping them from the mail server.
Since the server's POP support is not reliable, I thought of using IMAP.
when I change folders to {canine}INBOX (i have also tried {canine}inbox,
{canine}
yes, I have tried that too. still no mails.
Raju
On Fri, Oct 08, 1999 at 11:04:10AM -0500, David DeSimone [[EMAIL PROTECTED]] wrote:
> Raju K V <[EMAIL PROTECTED]> wrote:
> >
> > When I change folders {canine}/var/spool/mail/rajukv where canine is
> > my mailserver, no mails are displayed. But
Raju K V <[EMAIL PROTECTED]> wrote:
>
> When I change folders {canine}/var/spool/mail/rajukv where canine is
> my mailserver, no mails are displayed. But I get a message 'new mail
> in folder' though none of the mails are displayed.
The usual way to specify your incoming mailbox is
{canine}
hi,
I pop mails from my mailserver. The server also supports IMAP. When I
change folders
{canine}/var/spool/mail/rajukv where canine is my mailserver,
no mails are displayed. But I get a message 'new mail in folder' though
none of the mails are displayed.
I can pop mails from the same machine.
m
12 matches
Mail list logo
