Re: size of folder on disk much larger than size reported by mail client.
Am Thursday 14 September 2006 07:56 schrieb Warren Howard:
> Hi,
>
> I've noticed that the size of the folders on disk can be much larger
> than the size reported by the mail client and I'm wondering why.
>
> I'm using Cyrus-imapd 2.2.12 and the mail client is Squirrelmail 1.4.8
> with the 1.5 version of the Folder Sizes plug-in.
>
> In Squirrelmail I can use the Folder Sizes plug-in to show that I have a
> folder with a "count" of 17120 and a size of 68 MB. The folder is a
> shared folder that goes by the name "Postfix users". On the mail server
> the corresponding disk location (to the best of my knowledge) for this
> folder is "/var/spool/imap/p/Internet\ Mailing\ Lists/Postfix\ users/".
>
> This directory has 17123 files in it, exactly 17120 (the count reported
> by the Folder Sizes plug-in) plus three additional files cyrus.cache,
> cyrus.header and cyrus.index. The size of this directory with the three
> additional "cyrus" files is 120 MB - almost twice the size reported by
> the Folder Sizes plug-in for Squirrelmail. Now cyrus.cache is 24 MB and
> cyrus.index is 1 MB (cyrus.header is tiny 165 bytes), subtracting these
> leaves me with mail message files that add up to 95 MB still 27 MB
> larger than what is reported by the Folder Sizes plug-in.
>
> I also checked the size of the "Postfix users" using cyradm (in case the
> Folder Sizes plug-in was wrong).
>
> localhost> info 'Internet Mailing Lists/Postfix users'
> {Internet Mailing Lists/Postfix users}:
> lastupdate: 14-Sep-2006 10:35:00 +0530
> partition: default
> size: 72033301
>
> so why does cyradm and the Folder Sizes plug-in report a size of 68 MB
> where if I go and check on disk I see the sum of the message files on
> disk is closer to 95 MB?
Please use:
# du -bs --exclude="cyrus.*" /path/to/folder
> Is it a file system thing? I'm using reiserfs with the following fstab
> options
>
> /dev/system/var /varreiserfsnotail,noatime 0 0
>
> I'm worried that "notail" and lots of small message files is chewing up
> disk space could it be the case?
--
Andreas
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
size of folder on disk much larger than size reported by mail client.
Hi,
I've noticed that the size of the folders on disk can be much larger
than the size reported by the mail client and I'm wondering why.
I'm using Cyrus-imapd 2.2.12 and the mail client is Squirrelmail 1.4.8
with the 1.5 version of the Folder Sizes plug-in.
In Squirrelmail I can use the Folder Sizes plug-in to show that I have a
folder with a "count" of 17120 and a size of 68 MB. The folder is a
shared folder that goes by the name "Postfix users". On the mail server
the corresponding disk location (to the best of my knowledge) for this
folder is "/var/spool/imap/p/Internet\ Mailing\ Lists/Postfix\ users/".
This directory has 17123 files in it, exactly 17120 (the count reported
by the Folder Sizes plug-in) plus three additional files cyrus.cache,
cyrus.header and cyrus.index. The size of this directory with the three
additional "cyrus" files is 120 MB - almost twice the size reported by
the Folder Sizes plug-in for Squirrelmail. Now cyrus.cache is 24 MB and
cyrus.index is 1 MB (cyrus.header is tiny 165 bytes), subtracting these
leaves me with mail message files that add up to 95 MB still 27 MB
larger than what is reported by the Folder Sizes plug-in.
I also checked the size of the "Postfix users" using cyradm (in case the
Folder Sizes plug-in was wrong).
localhost> info 'Internet Mailing Lists/Postfix users'
{Internet Mailing Lists/Postfix users}:
lastupdate: 14-Sep-2006 10:35:00 +0530
partition: default
size: 72033301
so why does cyradm and the Folder Sizes plug-in report a size of 68 MB
where if I go and check on disk I see the sum of the message files on
disk is closer to 95 MB?
Is it a file system thing? I'm using reiserfs with the following fstab
options
/dev/system/var /varreiserfsnotail,noatime 0 0
I'm worried that "notail" and lots of small message files is chewing up
disk space could it be the case?
Thanks,
Warren.
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Cyrus sasl auth requires entry in /etc/hosts
Am Wednesday 13 September 2006 17:57 schrieb Ramprasad: >I have a cyrus setup with one primary domain and many virtual domains > > A) Saslauthd is running as > saslauthd -m /var/run/saslauthd -a pam -r > > > B) Username in ldap > for primary domain > uid=userid > > for virtual domain > [EMAIL PROTECTED] > > > Now when my /etc/hosts does not have > 127.0.0.1 primary-domain.com > > a primary-domain user is not able to authenticate .. but virtual domain > users have no problem at all Why not use "[EMAIL PROTECTED]" as Authentification Id. Another way would be "defaultdomain: primary-domain.com" in imapd.conf for unqualified UserIds. > Cant I do without the /etc/hosts entry > PS: > I am using cyrus 2.3 on centos 4.3 -- Andreas Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Cyrus sasl auth requires entry in /etc/hosts
Hi, I have a cyrus setup with one primary domain and many virtual domains A) Saslauthd is running as saslauthd -m /var/run/saslauthd -a pam -r B) Username in ldap for primary domain uid=userid for virtual domain [EMAIL PROTECTED] Now when my /etc/hosts does not have 127.0.0.1 primary-domain.com a primary-domain user is not able to authenticate .. but virtual domain users have no problem at all Cant I do without the /etc/hosts entry Thanks Ram PS: I am using cyrus 2.3 on centos 4.3 Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
R: sync client bailing out
>> Now everything seems to have come back up but the replication still has >> problems. The client process on the master bails out frequently with >> these errors in the log: > >It looks like you have some corruption in cyrus.index files on the replica >following the crash. Try running reconstruct on the mailboxes in question. Some corruption indeed: the replica had faulty RAM. I ended up wiping out the mailboxes on the replica and started everything fresh, the data was mostly corrupted anyway. One should run memtest86 every once in a while.. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: Login Mystery
Problem Solved! The (slightly inaccurate) comment in my imapd.conf file is illustrative: defaultdomain: mailadmin.com ## ACHTUNG! The default domain must match the host name my hosts file contained the following entry: 10.0.0.2mailadmin.com mailadmin I changed it to 10.0.0.2host.mailadmin.com mailadmin That fixed the problem. Thanks for the help. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run
On Wed, 13 Sep 2006 09:14:17 +0100 (BST), "David Carter" <[EMAIL PROTECTED]> said: > On Tue, 12 Sep 2006, Wesley Craig wrote: > > > On a related note, what was the problem with accepting the Cambridge > > patches for delayed folder deletion? I'm interested in working on > > getting that or similar code accepted. Now that we have delayed expunge > > for messages, we continue to run tape backups only for the case where > > users inadvertently delete folders. > > [ ... other things about delayed mailbox deletion ... ] > > Without (1) or (2), delayed mailbox deletion is really nothing more > exciting than a RENAME operation to some part of the mailbox hierarchy > without a quota root that only the system administrator can access. Ho hum de dum... of course. Why didn't I think of that. Much easier than trying to fiddle around with the filesystem level deletion code. I smell a patch, some time when I'm more awake and not managing the migration of users to smaller partitions (note to those who haven't been bitten yet - don't ever put thousands of users on a 2Tb filesystem. Just about everything than could possibly go wrong means days of downtime, and users _hate_ that) Hrm... first edge case that sounds interesting, deleting a folder that has subfolders without deleting the subfolders as well... My urgent todo list is down to about 10 items now, and I'm sure at least one of those is easy :) Bron. -- Bron Gondwana [EMAIL PROTECTED] Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
RE: Login Mystery
Cristian Mitrana wrote: > Looks like a configuration problem, can please give more details about it ? > Post your imapd.conf and tell us what version of Cyrus are you using. How > are you authenticating your users ? Do you use Saslauthd, sasldb or sql ? I am using sasldb to authenticate Cyrus Version is cyrus-imapd-2.2.12 ### imapd.conf ### configdirectory: /var/lib/imap partition-default: /var/spool/imap # sievedir: /var/lib/sieve admins: tqis allowanonymouslogin: no autocreatequota: 1 reject8bit: no quotawarn: 90 timeout: 30 poptimeout: 10 dracinterval: 0 drachost: localhost allowplaintext: 1 lmtp_overquota_perm_failure: no sasl_pwcheck_method: auxprop sasl_sasldb_path: /etc/sasldb2 sasl_mech_list: plain login sasl_log_level: 10 virtdomains: yes defaultdomain: mailadmin.com ## ACHTUNG! The default domain must match the host name # # if you want TLS, you have to generate certificates and keys # #tls_cert_file: /usr/ssl/certs/cert.pem #tls_key_file: /usr/ssl/certs/skey.pem #tls_ca_file: /usr/ssl/CA/CAcert.pem #tls_ca_path: /usr/ssl/CA Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Integrted tool for adminstering Cyrus IMAP and LDAP.
AndrXs Tarallo schrieb: I have to deploy an Email Server based on Cyrus IMAP, Postfix and LDAP. This is no problem, I have done it before.However our customer requests for a web based tool for administering user accounts and quotas. We found tools capable of administering accounts in the LDAP Server (ie LDAPmyADMIN) or cyrus accounts, but not an integrated tool.We want a tool where you can create a Cyrus account with LDAP autentication filling one web based form, Same with modifications and deletions. ISPman - http://www.ispman.net/ - does all this. It is an integrated solution and does not just do the LDAP administration through a web interface. Does someone has something to recomend? Thanks in advance. A/P Andres Tarallo Alexander Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: sync_client bails out after 3 MAILBOXES need upgrading to USER in one run
On Tue, 12 Sep 2006, Wesley Craig wrote: On a related note, what was the problem with accepting the Cambridge patches for delayed folder deletion? I'm interested in working on getting that or similar code accepted. Now that we have delayed expunge for messages, we continue to run tape backups only for the case where users inadvertently delete folders. Replication and delayed expunge were added by Ken (working as a contractor) back before he joined CMU. Replication was sponsored by Columbia. Delayed expunge was sponsored by Fastmail, but mostly as a performance enhancement. Unexpunge was just a nice side effect. I believe that Ken implemented the delayed expunge from scratch. My original "two expunge expunge" code is rather more involved: 1) Users can access expunged mail and deleted mailboxes using magic mailbox hierarchies (.EXPUNGED/ and .DELETED/). 2) It hooks into the quota system to record the amount of expunged space in each quota root. Messages are automatically expired when global or per quota root limits are reached. With hindsight (1) was a daft idea on my part. Our users struggle with the idea of multiple mailboxes in their account, let alone magic mailbox hierarchies. (2) is arguably useful if you don't have infinite storage on your IMAP backends. There are however lots of other spool partitions which can fill up under a determined denial of service attack. Without (1) or (2), delayed mailbox deletion is really nothing more exciting than a RENAME operation to some part of the mailbox hierarchy without a quota root that only the system administrator can access. -- David Carter Email: [EMAIL PROTECTED] University Computing Service,Phone: (01223) 334502 New Museums Site, Pembroke Street, Fax: (01223) 334679 Cambridge UK. CB2 3QH. Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
