Data format error: : Mailbox doesn't exist

[Sebastian Haas]

Hello list,

I have a very strange problem using Postfix and Cyrus together. If I 
send an mail with more then one local recipient, Cyrus fails to deliver 
the mail, only the first recipient will get the mail. Postfix generates 
a bounce message.


This is the returned message (looks similar to the logs):

<[EMAIL PROTECTED]>: data format error. Command output: : Mailbox does 
not exist


<[EMAIL PROTECTED]>: data format error. Command output: : Mailbox does 
not exist


Log output:
Nov  9 08:01:44 mailserver postfix/pipe[10522]: D1EA8BCCE: 
to=<[EMAIL PROTECTED]>, relay=cyrus, delay=1, status=bounced (data 
format error. Command output: : Mailbox does not exist )
Nov  9 08:01:44 mailserver postfix/pipe[10522]: D1EA8BCCE: 
to=<[EMAIL PROTECTED]>, relay=cyrus, delay=1, status=bounced (data 
format error. Command output: : Mailbox does not exist )


If I send the mail itemized it is delivered right to each recipient.

Postfix delivers message to Cyrus via a Unix type socket to lmtpd.

My Cyrus version: v2.1.18-IPv6-Debian-2.1.18-1
The box runs on Linux Kernel 2.6.4

What could be the problem? Did you need any additional information?

--
Mit freundlichen Gruessen/Best Regards,
Sebastian Haas

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: improving concurrency/performance (fwd)

[Andrew McNamara]

I forwarded John's message to Andrew Morton, linux kernel maintainer, and
this is his reply (it was cc'ed to the list, but, not being a subscriber,
I presume it bounced):

--- Forwarded Message

Date:Tue, 08 Nov 2005 15:21:31 -0800
From:Andrew Morton <[EMAIL PROTECTED]>
To:  Andrew McNamara <[EMAIL PROTECTED]>
cc:  "John Madden" <[EMAIL PROTECTED]>,
 info-cyrus@lists.andrew.cmu.edu
Subject: Re: improving concurrency/performance (fwd)

Andrew McNamara <[EMAIL PROTECTED]> wrote:
>
> This guy is having a problem with cyrus-imap and ext3 - when multiple
> processes are attempting to write to the one filesystem (but not the one
> file), performance drops to next to nothing when only five processes are
> writing. An strace shows most of the time is being spent in fdatasync
> and fsync.
> 
> ...

Yes, on ext3, an fsync() syncs the entire filesystem.  It has to, because
all the metadata for each file is shared - it's just a string of
journallable blocks.  Similar story with the data, in ordered mode.

So effectively, fsync()ing five files one time each is performing 25 fsync()s.

One fix (which makes the application specific to ext3 in ordered-data or
journalled-data mode) is to perform a single fsync(), with the
understanding that this has the side-effect of fsyncing all the other
files.  That's an ugly solution and is rather hard to do if the workload
consists of five separate processes!

So I'd recommending mounting the filesystem with the `-o data=writeback'
mode.  This way, each fsync(fd) will sync fd's data only.  That's much
better than the default data-ordered mode, wherein a single fsync() will
sync all the other file's data too.

In data=writeback mode it is still the case that fsync(fd) will sync the
other file's metadata, but that's a single linear write to the journal and
the additional cost should be low.

Bottom line: please try data=writeback, let me know.


> --- Forwarded Message
> 
> Date:Tue, 08 Nov 2005 09:25:54 -0500
> From:"John Madden" <[EMAIL PROTECTED]>
> To:  Jure =?iso-8859-1?Q?Pe=E8ar?= <[EMAIL PROTECTED]>
> cc:  info-cyrus@lists.andrew.cmu.edu
> Subject: Re: improving concurrency/performance
> 
> > As expected, these are from locking operations. 0x8 is file descriptor,
> > which, if I read lsof output correctly, points to config/socket/imap-0.lock
> > (what would that be?) and 0x7 is F_SETLKW which reads as "set lock or wait
> > for it to be released" in the manual page.
> 
> Yup, that's exactly the sort of thing I was suspecting -- the performance I
> was seeing just didn't make sense.
> 
> imap-0.lock is in /var/imap/socket for me.  I believe it's one of the lock
> file s created when cyrus is started, so it wouldn't make any sense for
> imapd to ever be spinning on it.
> 
> The delays I was seeing ocurred when multiple imapd's were writing to the
> spool at the same time.  I do see a lot of this though:
> 
> fcntl(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
> 
> It looks like the lock to open a file in the target mailbox.  But again,
> very l ow actual throughput and still little or no iowait.  However, adding
> a -c to the strace, the top three syscalls are:
> 
> % time seconds  usecs/call callserrors syscall
> - -- --- --- - - 
>  52.680.5147201243   414   fdatasync
>  29.870.291830 846   345   fsync
>   4.190.040898  27  1519   fcntl
> 
> Makes me wonder why the fsync's are taking so long since the disk is
> performing so well.  Anyone know if that's actually typical?
> 
> -- 
> John Madden
> UNIX Systems Engineer
> Ivy Tech Community College of Indiana
> [EMAIL PROTECTED]
> 
> - 
> Cyrus Home Page: http://asg.web.cmu.edu/cyrus
> Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
> List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
> 
> --- End of Forwarded Message

--- End of Forwarded Message


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: improving concurrency/performance

[Wil Cooley]

On Tue, 2005-11-08 at 09:25 -0500, John Madden wrote:

> Makes me wonder why the fsync's are taking so long since the disk is 
> performing so
> well.  Anyone know if that's actually typical?

Some time ago I wrote a little LD_PRELOAD libary that neutered fsync()
and related calls, intended for use with migration; maybe it'll help,
maybe it won't.  At any rate, if you're doing practice migrations and
aren't worried too much about trashing your test system, try it and let
me know.

http://haus.nakedape.cc/svn/public/trunk/small-projects/fakesync/

Wil
-- 
Wil Cooley <[EMAIL PROTECTED]>
Naked Ape Consulting, Ltd


signature.asc
Description: This is a digitally signed message part

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Frequent DBERROR DB4

[Stephen Conway]

Hello:
 
We have a Cyrus IMAPD server version 2.1.12 running on a RH 8 server.  All
is working find up until last week, now we are getting increasing errors as
follows:
 
Nov  7 22:36:33 antar lmtpd[1057]: DBERROR db4: 50 lockers
 
The number before lockers keeps going higher and higher until eventually the
server stops receiving pop and imap connections.  After a restart of the
server, it starts over again.  My question is, how can I stop these, and why
after a reboot does it reset down to 1 again?  I have read a bit in the
archives and it seems that this has something to do with Berkley DB and that
updating to newest version of Cyrus should fix this, is this correct?  If
so, what are the necessary steps to install the latest version, preserving
the existing system, users, messages, etc.
 
Any light you can shed is appreciated.

Regards,
 
Steve


-- 
ShipMail Now 30% Faster


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

unable to init duplicate delivery database

[Libor Kunes]

Hello,
I have Cent OS 3.4 and I have installed cyrus-imap 2.2. Everything ran 
OK. When I have started cyrus-imapd my maillog started to increase 
drastically with the following errors:

   lmtpunix: DBERROR: opening /var/imap/deliver.db: cyrusdb error
   lmtpunix[1515]: FATAL: lmtpd: unable to init duplicate delivery 
database

   unable to initialize inviromnent loc

All these errors keep going on and on. I remove the contents of the db 
folder and deliver.db and restarted cyrus-imapd. I did not help. These 
mistakes stopped occuring when I removed /var/lib/imap/socket folder but 
I was not able to receive any mail. I also tried to reinstal the whole 
cyrus-imap but in vain.


Could anyone help me what to do to repair this problem?
Thanks a lot

Libor


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Set quota

[Craig White]

On Tue, 2005-11-08 at 16:58 +0100, Alexander Dalloz wrote:
> Am Di, den 08.11.2005 schrieb Craig White um 14:38:
> 
> > I haven't a clue what features are included in FC-3 - that is why I
> > suggested checking out the README to see if feature was included.
> > 
> > Myself, I use RHEL & CentOS for servers (never Fedora) and never use
> > RHEL/CentOS cyrus-imapd because of the tremendous autocreate packages in
> > Simon's RPM's (thanks Simon btw)
> > 
> > I actually created an RFE in bugzilla.redhat.com to incorporate either
> > more of the autocreate stuff or use Simon's RPM's and it was tossed into
> > the next release category which is what I presumed never happened
> > category (e.g. RH's laggard adoption of openldap advances).
> > 
> > Craig
> 
> There is no need for an RFE. The Fedora Core / Fedora Extras (FC4)
> packages of Cyrus-IMAPd are based (~99%) on Simon's great work and
> include the autocreate patches already. They, the patches, are just not
> that up to date as those Simon's latest RPM incorporate.

Yes, it was clear that the RHEL/Fedora cyrus-imapd were taken from
invoca-ch (Simon) but they weren't the same as that which you can
download and build from Simon's web site.

I think I did the RFE on FC-3 which was long before FC-4 and RHEL-4 came
out and specifically wanted autosieve and some of the others and I know
they weren't included in RHEL-4 version. I don't use Fedora for servers
(CentOS or RHEL) so I wouldn't know where they are on the FC-4 cyrus-
imapd but my guess is that they didn't change.

So I have given up on RHEL cyrus-imapd packages and just use Simon's and
the autocreate stuff is great - excepting of course, what Aleksandar's
(note not Alexander Dalloz) admonition that when I had an issue with
ldap lookups of aliases, it created a new mailbox when it should have
aliased to a real account...it is fragile and you have to watch out. The
autosieve and the autosubscribe features in Simon's packages are worth
straying from RHEL/Fedora packages.

As for OP - I don't recall if autocreatequota is part of Fedora's
packages, which is why I recommended checking the readme. The nasty
thing about directives in imapd.conf is that they seem to be silently
ignored if not applicable so there's no log created if the feature is
requested in imapd.conf but not part of package.

Craig

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Set quota

[Casper]

From man imapd.conf



*



*autocreatequota:* 0

  If nonzero, normal users may create their own IMAP accounts by

  creating the mailbox INBOX. The user's quota is set to the value if

  it is positive, otherwise the user has unlimited quota.





*createonpost:* 0

  If yes, when lmtpd receives an incoming mail for an INBOX that does

  not exist, then the INBOX is automatically created by lmtpd.





*autocreateinboxfolders:* 

  If a user does not have an INBOX created then the INBOX as well as

  some INBOX subfolders are created under two conditions. 1. The user

  logins via the IMAP or the POP3 protocol. (autocreatequota option

  must have a nonzero value) 2. A message arrives for the user through

  the LMTPD protocol.(createonpost option must yes)

  autocreateinboxfolders is a list of INBOX's subfolders separated by

  a "|", that are automatically created by the server under the

  previous two situations. <- READ THIS



*



*autocreateinboxfolders:* 



Should look like



*autocreateinboxfolders:* inbox|spam|whatevermore



/Casper
 





Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: improving concurrency/performance

[John Madden]

> Hm. I'd definitely take a second look at your ds6800 configuration ... How is 
> your
> write cache configured there?

Let's just say they're not terribly clear on that. :)








-- 
John Madden
UNIX Systems Engineer
Ivy Tech Community College of Indiana
[EMAIL PROTECTED]


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Set quota

[Alexander Dalloz]

Am Di, den 08.11.2005 schrieb Craig White um 14:38:

> I haven't a clue what features are included in FC-3 - that is why I
> suggested checking out the README to see if feature was included.
> 
> Myself, I use RHEL & CentOS for servers (never Fedora) and never use
> RHEL/CentOS cyrus-imapd because of the tremendous autocreate packages in
> Simon's RPM's (thanks Simon btw)
> 
> I actually created an RFE in bugzilla.redhat.com to incorporate either
> more of the autocreate stuff or use Simon's RPM's and it was tossed into
> the next release category which is what I presumed never happened
> category (e.g. RH's laggard adoption of openldap advances).
> 
> Craig

There is no need for an RFE. The Fedora Core / Fedora Extras (FC4)
packages of Cyrus-IMAPd are based (~99%) on Simon's great work and
include the autocreate patches already. They, the patches, are just not
that up to date as those Simon's latest RPM incorporate.

Alexander


-- 
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp 
Serendipity 16:55:52 up 10 days, 14:56, load average: 0.65, 0.34, 0.16 


signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: improving concurrency/performance

[Jure Pečar]

On Tue, 8 Nov 2005 09:25:54 -0500 (EST)
"John Madden" <[EMAIL PROTECTED]> wrote:

> The delays I was seeing ocurred when multiple imapd's were writing to the 
> spool at
> the same time.  I do see a lot of this though:
> 
> fcntl(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0
> 
> It looks like the lock to open a file in the target mailbox.  But again, very 
> low
> actual throughput and still little or no iowait.  However, adding a -c to the
> strace, the top three syscalls are:
> 
> % time seconds  usecs/call callserrors syscall
> -- --- --- - - 
>  52.680.5147201243   414   fdatasync
>  29.870.291830 846   345   fsync
>   4.190.040898  27  1519   fcntl
> 
> Makes me wonder why the fsync's are taking so long since the disk is 
> performing so
> well.  Anyone know if that's actually typical?

Hm. I'd definitely take a second look at your ds6800 configuration ... How is 
your write cache configured there?

I can't really measure the percentage of fdatasync, since on live system most 
is time spent in select() and read() ... 
 
> Also interesting is the errors column for the open() call on this strace:
> 
> % time seconds  usecs/call callserrors syscall
> -- --- --- - - 
>   1.070.019902 17   622130 open
> 
> Why 130 errors?  I assume if there's an error that the call is re-tried...

Probably many ENOENT when trying to open msg/motd and msg/shutdown files.


-- 

Jure Pečar
http://jure.pecar.org


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: improving concurrency/performance

[John Madden]

> As expected, these are from locking operations. 0x8 is file descriptor,
> which, if I read lsof output correctly, points to config/socket/imap-0.lock
> (what would that be?) and 0x7 is F_SETLKW which reads as "set lock or wait
> for it to be released" in the manual page.

Yup, that's exactly the sort of thing I was suspecting -- the performance I was
seeing just didn't make sense.

imap-0.lock is in /var/imap/socket for me.  I believe it's one of the lock files
created when cyrus is started, so it wouldn't make any sense for imapd to ever 
be
spinning on it.

The delays I was seeing ocurred when multiple imapd's were writing to the spool 
at
the same time.  I do see a lot of this though:

fcntl(6, F_SETLKW, {type=F_UNLCK, whence=SEEK_SET, start=0, len=0}) = 0

It looks like the lock to open a file in the target mailbox.  But again, very 
low
actual throughput and still little or no iowait.  However, adding a -c to the
strace, the top three syscalls are:

% time seconds  usecs/call callserrors syscall
-- --- --- - - 
 52.680.5147201243   414   fdatasync
 29.870.291830 846   345   fsync
  4.190.040898  27  1519   fcntl

Makes me wonder why the fsync's are taking so long since the disk is performing 
so
well.  Anyone know if that's actually typical?

Also interesting is the errors column for the open() call on this strace:

% time seconds  usecs/call callserrors syscall
-- --- --- - - 
  1.070.019902 17   622130 open

Why 130 errors?  I assume if there's an error that the call is re-tried...

John





-- 
John Madden
UNIX Systems Engineer
Ivy Tech Community College of Indiana
[EMAIL PROTECTED]


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: imapd.conf parameter: sasl_minimum_layer not working as advertised

[Ken Murchison]

Kevin wrote:

Hi Folks-

I'm using Cyrus IMAPd v2.2.12.

I'd like to allow clients to authenticate using the plaintext mechanism,
but only if those connections are secured with TLS.  Is there a way to
do so?

I have the following settings in imapd.conf:

sasl_minimum_layer: 56
allowplaintext: yes

But I can still connect to the server with unencrypted connections and
do plaintext authentication.

According to man imapd.conf:

sasl_minimum_layer: 0
 The  minimum  SSF  that the server will allow a client to negotiate.  A
 value of 1 requires integrity protection; any higher value requires
 some  amount  of  encryption.

Before using the sasl_minimum_layer parameter at all, the server was
allowing plaintext logins that were encrypted with TLS and those that
were not.  I figured that by setting this parameter to 2, I would
accomplish my goal of allowing plaintext logins but only if encrypted
with TLS and denying unencrypted plaintext logins.  When the setting of
2 failed, I tried 56, but it too allows unencrypted plaintext
authentication.

Is this a bug or am I missing something?


What you want is:

allowplaintext: no

--
Kenneth Murchison
Systems Programmer
Carnegie Mellon University

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Set quota

[Craig White]

On Tue, 2005-11-08 at 18:49 +0530, Subhasha_HL wrote:
> It is on fedora core 3. I just used the same on fedora core 3
> - Original Message - 
> From: "Craig White" <[EMAIL PROTECTED]>
> To: 
> Sent: Tuesday, November 08, 2005 5:36 PM
> Subject: Re: Set quota
> 
> 
> > On Tue, 2005-11-08 at 16:42 +0530, Subhasha_HL wrote:
> >> Hi,
> >>I have configured cyrus-imap with postfix. I have set quotawarn to
> >> 90 in /etc/impad.conf.  autocreatequota to 200 MB. These configuration
> >> does not work. And also listquotaroot doesnot shows mailbox size.
> >> Any help please 
> > 
> > where did you install cyrus-imap from? My understanding is that the
> > autocreate patches aren't included in cyrus-imapd source but are
> > available here...
> > 
> > http://email.uoa.gr/projects/cyrus/
> > 
> > or in some pre-packaged distributions such as Simon Matter's...
> > 
> > http://www.invoca.ch/pub/packages/cyrus-imapd/
> > 
> > I have found that the documentation included with the package you have
> > installed should tell you which, if any, autocreate features are
> > included in your setup...
> > 
> > # locate autocreate
> > warning: locate: warning: database /var/lib/slocate/slocate.db' is more
> > than 8 days old
> > /usr/share/doc/cyrus-imapd-2.2.12/README.autocreate
> > 
> > less /usr/share/doc/cyrus-imapd-2.2.12/README.autocreate

let's keep on list please

I haven't a clue what features are included in FC-3 - that is why I
suggested checking out the README to see if feature was included.

Myself, I use RHEL & CentOS for servers (never Fedora) and never use
RHEL/CentOS cyrus-imapd because of the tremendous autocreate packages in
Simon's RPM's (thanks Simon btw)

I actually created an RFE in bugzilla.redhat.com to incorporate either
more of the autocreate stuff or use Simon's RPM's and it was tossed into
the next release category which is what I presumed never happened
category (e.g. RH's laggard adoption of openldap advances).

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

imapd.conf parameter: sasl_minimum_layer not working as advertised

[Kevin]

Hi Folks-

I'm using Cyrus IMAPd v2.2.12.

I'd like to allow clients to authenticate using the plaintext mechanism,
but only if those connections are secured with TLS.  Is there a way to
do so?

I have the following settings in imapd.conf:

sasl_minimum_layer: 56
allowplaintext: yes

But I can still connect to the server with unencrypted connections and
do plaintext authentication.

According to man imapd.conf:

sasl_minimum_layer: 0
 The  minimum  SSF  that the server will allow a client to negotiate.  A
 value of 1 requires integrity protection; any higher value requires
 some  amount  of  encryption.

Before using the sasl_minimum_layer parameter at all, the server was
allowing plaintext logins that were encrypted with TLS and those that
were not.  I figured that by setting this parameter to 2, I would
accomplish my goal of allowing plaintext logins but only if encrypted
with TLS and denying unencrypted plaintext logins.  When the setting of
2 failed, I tried 56, but it too allows unencrypted plaintext
authentication.

Is this a bug or am I missing something?

TIA.

-Kevin



Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

*****SPAM***** Re: Set quota

[Casper]

Spam detection software, running on the system "moso.dk", has
identified this incoming email as possible spam.  The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email.  If you have any questions, see
[EMAIL PROTECTED] for details.

Content preview:  Craig White wrote: >On Tue, 2005-11-08 at 16:42 +0530,
  Subhasha_HL wrote: > > >>Hi, >> I have configured cyrus-imap with
  postfix. I have set quotawarn to >>90 in /etc/impad.conf.
  autocreatequota to 200 MB. These configuration >>does not work. And also
  listquotaroot doesnot shows mailbox size. >>Any help please >> >> >
  >where did you install cyrus-imap from? My understanding is that the
  >autocreate patches aren't included in cyrus-imapd source but are
  >available here... > >http://email.uoa.gr/projects/cyrus/ > >or in some
  pre-packaged distributions such as Simon Matter's... >
  >http://www.invoca.ch/pub/packages/cyrus-imapd/ > >I have found that the
  documentation included with the package you have >installed should tell
  you which, if any, autocreate features are >included in your setup... >
  ># locate autocreate >warning: locate: warning: database
  /var/lib/slocate/slocate.db' is more >than 8 days old
  >/usr/share/doc/cyrus-imapd-2.2.12/README.autocreate > >less
  /usr/share/doc/cyrus-imapd-2.2.12/README.autocreate > >Craig > > > >
  [...] 

Content analysis details:   (7.1 points, 5.0 required)

 pts rule name  description
 -- --
 1.8 RCVD_IN_SORBS_SOCKSRBL: SORBS: sender is open SOCKS proxy server
[82.99.44.213 listed in dnsbl.sorbs.net]
 1.8 RCVD_IN_DSBL   RBL: Received via a relay in list.dsbl.org
[]
 0.3 RCVD_IN_NJABL_PROXYRBL: NJABL: sender is an open proxy
[82.99.44.213 listed in combined.njabl.org]
 3.1 RCVD_IN_XBLRBL: Received via a relay in Spamhaus XBL
[82.99.44.213 listed in sbl-xbl.spamhaus.org]


--- Begin Message ---

Craig White wrote:


On Tue, 2005-11-08 at 16:42 +0530, Subhasha_HL wrote:
 


Hi,
  I have configured cyrus-imap with postfix. I have set quotawarn to
90 in /etc/impad.conf.  autocreatequota to 200 MB. These configuration
does not work. And also listquotaroot doesnot shows mailbox size.
Any help please 
   



where did you install cyrus-imap from? My understanding is that the
autocreate patches aren't included in cyrus-imapd source but are
available here...

http://email.uoa.gr/projects/cyrus/

or in some pre-packaged distributions such as Simon Matter's...

http://www.invoca.ch/pub/packages/cyrus-imapd/

I have found that the documentation included with the package you have
installed should tell you which, if any, autocreate features are
included in your setup...

# locate autocreate
warning: locate: warning: database /var/lib/slocate/slocate.db' is more
than 8 days old
/usr/share/doc/cyrus-imapd-2.2.12/README.autocreate

less /usr/share/doc/cyrus-imapd-2.2.12/README.autocreate

Craig


 




autocreatequota should be working if createonpost is set to yes and no 
need for patching cyrus source.




From man imapd.conf

*

*autocreatequota:* 0
   If nonzero, normal users may create their own IMAP accounts by
   creating the mailbox INBOX. The user's quota is set to the value if
   it is positive, otherwise the user has unlimited quota.


*createonpost:* 0
   If yes, when lmtpd receives an incoming mail for an INBOX that does
   not exist, then the INBOX is automatically created by lmtpd.


*autocreateinboxfolders:* 
   If a user does not have an INBOX created then the INBOX as well as
   some INBOX subfolders are created under two conditions. 1. The user
   logins via the IMAP or the POP3 protocol. (autocreatequota option
   must have a nonzero value) 2. A message arrives for the user through
   the LMTPD protocol.(createonpost option must yes)
   autocreateinboxfolders is a list of INBOX's subfolders separated by
   a "|", that are automatically created by the server under the
   previous two situations. <- READ THIS

*

*autocreateinboxfolders:* 

Should look like

*autocreateinboxfolders:* inbox|spam|whatevermore

/Casper
--- End Message ---

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Set quota

[Craig White]

On Tue, 2005-11-08 at 16:42 +0530, Subhasha_HL wrote:
> Hi,
>I have configured cyrus-imap with postfix. I have set quotawarn to
> 90 in /etc/impad.conf.  autocreatequota to 200 MB. These configuration
> does not work. And also listquotaroot doesnot shows mailbox size.
> Any help please 

where did you install cyrus-imap from? My understanding is that the
autocreate patches aren't included in cyrus-imapd source but are
available here...

http://email.uoa.gr/projects/cyrus/

or in some pre-packaged distributions such as Simon Matter's...

http://www.invoca.ch/pub/packages/cyrus-imapd/

I have found that the documentation included with the package you have
installed should tell you which, if any, autocreate features are
included in your setup...

# locate autocreate
warning: locate: warning: database /var/lib/slocate/slocate.db' is more
than 8 days old
/usr/share/doc/cyrus-imapd-2.2.12/README.autocreate

less /usr/share/doc/cyrus-imapd-2.2.12/README.autocreate

Craig


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Set quota

[Subhasha_HL]

Hi,
   I have configured cyrus-imap with 
postfix. I have set quotawarn to 90 in /etc/impad.conf.  autocreatequota to 
200 MB. These configuration does not work. And also listquotaroot doesnot shows 
mailbox size.
Any help please 
 
Thanks 
Subhasha

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re[2]: Problem with Subject: XXXX XXXXXX on Cyrus

[Igor Belikov]

Hello lkolchin,

Monday, November 7, 2005, 6:28:37 PM, you wrote:

luhai> The patch from Igor is also interesting, if nothing
luhai> else works, I'd like to try it.

I must to inform you that developers of this patch do not accept it
because it not "correctly" deals with 8-bit headers. But I mean that
leave headers as-is more correct than kill headers, replacing 8-bit
chars with "X".

In attachment to this letter are patch file and short description.

-- 
Best regards,
 Igormailto:[EMAIL PROTECTED]

Cyrus-IMAP.2.2.12.ignore8bit.info
Description: Binary data


Cyrus-IMAP.2.2.12.ignore8bit.patch
Description: Binary data

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html