error marking messages as read

Hello, I got the following error in my syslog trying to mark 1930 messages as read. I am using Cyrus 2.1.12 as the server, and Mozilla 1.2.1 as my mail client. Apr 4 14:04:47 kang imapd[51441]: Fatal error: word too long Is this a problem with the IMAP server, or the client?

Re: Cyrus bug when returning mailbox names

Ian Macdonald wrote: Hi, There seems to be a bug in the Cyrus code that incorrectly returns the name of a mailbox with a trailing space as that name without the space: [EMAIL PROTECTED] telnet cyrus 143 Trying 1.2.3.4... Connected to cyrus. Escape character is '^]'. * OK babbage.corp.google.com C

Re: /Noinferiors on INBOX

Morgan Sackett wrote: John A. Tamplin wrote: 1.5 did not have altnamespace, it was always INBOX.Trash etc. What exactly is the problem with having \Noinferiors set on INBOX? In altnamespace, it does not have any subfolders. Ie, if I have user/jtampli and user/jtampli/test, that will show up

Re: /Noinferiors on INBOX

Rob Siemborski wrote: altnamespace=yes should give you same level folders, altnamespace=no should give you nexting. -Rob Unfortunately, I'm seeing the opposite results. If I have altnamespace=no, then I can see and sub to all of the folders and they are at the same level as INBOX. Inbox ha

Re: /Noinferiors on INBOX

John A. Tamplin wrote: 1.5 did not have altnamespace, it was always INBOX.Trash etc. What exactly is the problem with having \Noinferiors set on INBOX? In altnamespace, it does not have any subfolders. Ie, if I have user/jtampli and user/jtampli/test, that will show up as INBOX and test, and

Re: /Noinferiors on INBOX

1.5.x gave the nested subfolders with altnamespace=no. 2.0.16 gave nesting with altnamespace=yes. Now, with 2.1.12, altnamespace=yes gives /Noinferiors, and altnamspace=no gives same level folders. HELP! Ken Murchison wrote: Morgan Sackett wrote: Should this happen? I do have subfold

Re: /Noinferiors on INBOX

Yes, altnamespace is enabled, and it always has been. Ken Murchison wrote: Morgan Sackett wrote: Should this happen? I do have subfolders in the mailbox, but clients won't look at them. Also, clients report errors in trying to create or append messages into a subfolder. However,

/Noinferiors on INBOX

Should this happen? I do have subfolders in the mailbox, but clients won't look at them. Also, clients report errors in trying to create or append messages into a subfolder. However, I can create a new folder both through cyradm, and directly logged in with a CREATE command. Is there a way t

Re: lmtp read error

seems to be strange now is that I no longer can see folders that I had under inbox. Maybe after a reconstruct I will have it. Mitrana Cristian wrote: * Morgan Sackett <[EMAIL PROTECTED]> [27-03-03 00:39]: Henrique de Moraes Holschuh wrote > Indeed. That's my setup exact

Re: lmtp read error

Henrique de Moraes Holschuh wrote > Indeed. That's my setup exactly. However, I just run lmtpd -a, bound to a > private network where only the LMTP servers and the SMTP servers are > connected to. Thus, no authorization worries, and no SASL overhead. Here is the error that

Re: lmtp read error

Rob Siemborski wrote: Not that Cyrus Murder is the only reason the use TCP LMTP. Its entirely reasonable to have your MTA on a separate machine and have delivery to cyrus happen via TCP LMTP over the network. This is my planned usage. I am migrating mail services from one machine to another on

Re: lmtp read error

Scott M. Likens wrote: Why aren't you using unix:/var/spool/imap/lmtp If you had taken the time to read through the previous message, I had stated that I recieve a "connection refused" error using the socket method. There is absolutely no reason to use TCP LMTP unless you have to. In this case

Re: lmtp read error

Mitrana Cristian wrote: * Morgan Sackett <[EMAIL PROTECTED]> [26-03-03 16:37]: You are correct about the MX records, though mail addressed directly to the machine gets delivered correctly. As far as I have read, LMTP does not require or use MX records. The socket method give

Re: lmtp read error

uot;63.105.30.19:lmtp" prefork=1 Sebastian Konstanty Zdrojewski wrote: The relay none message seems to indicate the MX record for the recipient domain is not properly configured... I am using a similar configuration, but using socket lmtp connection. Do you have lmtpd daemon running?

lmtp read error

I have a freshly configured Cyrus IMAP system set up. I am using Postfix to deliver mail to the system, and I currently have it set up to deliver via lmtp over tcp. Whenever postfix tries to deliver a message, I get an error. Here is an example Mar 25 14:42:06 kang postfix/lmtp[10398]: 53799