Re: Fwd: Public Key for Cyrus IMAPD
On Wed, 2013-03-20 at 09:23 +0800, Gene Leung wrote: > It seems no one care about the public key. Then, why still put the > signature file there for download? Or any other way for verify the > integrity of the download. "no one cares" is a bit harsh for 24hrs without a response. This list is primarily people who use / administer Cyrus IMAPd. And I'd wager most of those people use Cyrus from a package. Packagers are ones who care most about things like checksums, and they probably don't pay much attention to this list. I also wouldn't be surprised these days if packagers didn't work directly from a git checkout and just skipped the tgz. > Any where I can find the pubic key for verify the files downloaded of > the Cyrus IMAP software? Anyway, nope, I do not see a checksum/sumkey at ftp://ftp.cyrusimap.org/cyrus-imapd/ Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: very large mailboxes backup, long retention period deleted also
Hello, Thanks for your suggestions. Reading list archives, many alerted against NFS for cyrus imap. Someone listed the fwrite syscall as the source of problems with NFS. I found some old bug reports https://bugzilla.redhat.com/show_bug.cgi?id=90159 http://forums.codeguru.com/showthread.php?322677-Problems-with-fwrite-and-NFS but browsing http://git.cyrusimap.org/cyrus-imapd/ a little, it seems that recent 2.4.x versions uses fwrite only for db operations. Is this assumption correct? Are there another syscalls in cyrus that cause trouble with NFS 3 or 4? If so, then, as we use metadata partition at separated high-speed LUN on fs and kernel tuned for small files[1,2,3], it could be possible to use NFS only for data partition. Had anyone tried this approach on production? What are the recent cyrus 2.4.x versions experiences over NFS? Regards. Andre Felipe Machado [1] http://www.techforce.com.br/news/linux_blog/lvm_raid_xfs_ext3_tuning_for_small_files_parallel_i_o_on_debian [2] http://www.techforce.com.br/news/linux_blog/debian_linux_kernel_tuning_low_latency_small_files [3] http://www.techforce.com.br/news/linux_blog/xenserver_reduzir_latencia_i_o On 19/Mar/2013 09:50 Eric Luyten wrote .. > > Maybe, if cyrus becomes compatible with NFS, then HSM solutions like > > http://www.openarchive.net could help. > > > Andre, > > While, in general, participants in this forum still are pretty reluctant > putting their Cyrus mailstores on NFS storage, there has been at least > one architect/administrator of a very large Cyrus configuration pretty > happy using NetApp filers and NFS as their underlying storage structure. > When using intelligent storage (does not have to be NFS, sub-LUN tiering > in block access methods (iSCSI, FC) will also do the job) you will be > pushing the tiering issue down to your storage level, which may be (part > of) a solution to your problem. > > Kind regards, > Eric Luyten, Computing Centre VUB/ULB. Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Partition selection algorithm and ZFS filesystems
Friends, The man page for imapd.conf contains this note (emphasis added): defaultpartition: The partition name used by default for new mailboxes. *If not specified, the partition with the most free space will be used for new mailboxes.* However, with the advent of ZFS and other filesystems with Thin Provisioning, it is common for all partitions to have the same amount of free space reported by the filesystem. For example, this from a client's system with 30 data partitions and 30 meta-data partitions: data2/mailstore/1 4.9T 18G4.9T 0% /var/mailstores/1 data2/mailstore/104.9T 12G4.9T 0% /var/mailstores/10 data2/mailstore/114.9T 10G4.9T 0% /var/mailstores/11 data2/mailstore/124.9T 16G4.9T 0% /var/mailstores/12 data2/mailstore/134.9T 15G4.9T 0% /var/mailstores/13 data2/mailstore/144.9T 16G4.9T 0% /var/mailstores/14 ... data2/imapmeta/1 4.9T1.2G4.9T 0%/var/imapmeta/1 data2/imapmeta/10 4.9T283M4.9T 0%/var/imapmeta/10 data2/imapmeta/11 4.9T370M4.9T 0%/var/imapmeta/11 data2/imapmeta/12 4.9T251M4.9T 0%/var/imapmeta/12 data2/imapmeta/13 4.9T369M4.9T 0%/var/imapmeta/13 data2/imapmeta/14 4.9T230M4.9T 0%/var/imapmeta/14 ... In light of this, we intend to have our account creation scheme base its choice on space used, rather than free space. But, would it be possible, in light of the wide spread adoption of thin provisioned filesystems, to have the default behavior changed in 2.5 or some future version of Cyrus imapd? Thanks in advance, -nic -- Nic Bernstein n...@onlight.com Onlight, Inc. www.onlight.com 219 N. Milwaukee St., Suite 2av. 414.272.4477 Milwaukee, Wisconsin 53202 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Public Key for Cyrus IMAPD
On 20/03/2013, at 11:53, Gene Leung wrote: > It seems no one care about the public key. Then, why still put the signature > file there for download? Or any other way for verify the integrity of the > download. The key is available from gpg.mit.edu [midget 9:53] ~ >gpg --recv-keys 9342BF08 gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/documentation/faqs.html for more information gpg: requesting key 9342BF08 from hkp server pgp.mit.edu gpg: key 9342BF08: public key "Jeroen van Meeuwen (kanarip) " imported gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model gpg: depth: 0 valid: 1 signed: 3 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: depth: 1 valid: 3 signed: 0 trust: 0-, 0q, 0n, 3m, 0f, 0u gpg: Total number processed: 1 gpg: imported: 1 [midget 9:55] ~ >gpg --verify cyrus-imapd-2.4.17.tar.gz.sig cyrus-imapd-2.4.17.tar.gz gpg: WARNING: using insecure memory! gpg: please see http://www.gnupg.org/documentation/faqs.html for more information gpg: Signature made Sun 2 Dec 06:33:32 2012 CST using DSA key ID 9342BF08 gpg: Good signature from "Jeroen van Meeuwen (kanarip) " gpg: aka "Jeroen van Meeuwen (GMail) " gpg: aka "Jeroen van Meeuwen (OGD) " gpg: aka "Jeroen van Meeuwen (XS4All) " gpg: aka "Jeroen van Meeuwen (GameDrome) " gpg: aka "Jeroen van Meeuwen (PC Zone Clan) " gpg: aka "Jeroen van Meeuwen (Fedora Unity) " gpg: aka "Jeroen van Meeuwen (Fedora Project) " gpg: aka "Jeroen van Meeuwen (Kolab Systems) (Kolab Systems AG) " gpg: aka "Jeroen van Meeuwen (Ergo Project) (Ergo Project) " gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08 -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: Public Key for Cyrus IMAPD
Hi Daniel, Really appreciate your help and give me an idea how to get the key from the pgp server.. I only used Ken's key for my last installed version 2.3.16 gpg --verify cyrus-imapd-2.3.16.tar.gz.sig gpg: Signature made Mon 21 Dec 2009 09:34:05 PM HKT using DSA key ID 6581B5F1 gpg: Good signature from "Kenneth S Murchison " gpg: WARNING: This key is not certified with a trusted signature! gpg: There is no indication that the signature belongs to the owner. Primary key fingerprint: 11C3 B2A6 BF9C F06C 216F 76E7 D0AB 95C1 6581 B5F1 It is hard to find those latest information regarding verification of the software integrity. Thanks. B/R Gene Leung On Thu, Mar 21, 2013 at 7:26 AM, Daniel O'Connor wrote: > > On 20/03/2013, at 11:53, Gene Leung wrote: > > It seems no one care about the public key. Then, why still put the > signature file there for download? Or any other way for verify the > integrity of the download. > > The key is available from gpg.mit.edu > > [midget 9:53] ~ >gpg --recv-keys 9342BF08 > gpg: WARNING: using insecure memory! > gpg: please see http://www.gnupg.org/documentation/faqs.html for more > information > gpg: requesting key 9342BF08 from hkp server pgp.mit.edu > gpg: key 9342BF08: public key "Jeroen van Meeuwen (kanarip) < > kana...@kanarip.com>" imported > gpg: 3 marginal(s) needed, 1 complete(s) needed, classic trust model > gpg: depth: 0 valid: 1 signed: 3 trust: 0-, 0q, 0n, 0m, 0f, 1u > gpg: depth: 1 valid: 3 signed: 0 trust: 0-, 0q, 0n, 3m, 0f, 0u > gpg: Total number processed: 1 > gpg: imported: 1 > [midget 9:55] ~ >gpg --verify cyrus-imapd-2.4.17.tar.gz.sig > cyrus-imapd-2.4.17.tar.gz > gpg: WARNING: using insecure memory! > gpg: please see http://www.gnupg.org/documentation/faqs.html for more > information > gpg: Signature made Sun 2 Dec 06:33:32 2012 CST using DSA key ID 9342BF08 > gpg: Good signature from "Jeroen van Meeuwen (kanarip) < > kana...@kanarip.com>" > gpg: aka "Jeroen van Meeuwen (GMail) " > gpg: aka "Jeroen van Meeuwen (OGD) " > gpg: aka "Jeroen van Meeuwen (XS4All) " > gpg: aka "Jeroen van Meeuwen (GameDrome) < > kana...@gamedrome.com>" > gpg: aka "Jeroen van Meeuwen (PC Zone Clan) < > kana...@pczone-clan.nl>" > gpg: aka "Jeroen van Meeuwen (Fedora Unity) < > kana...@fedoraunity.org>" > gpg: aka "Jeroen van Meeuwen (Fedora Project) < > kana...@fedoraproject.org>" > gpg: aka "Jeroen van Meeuwen (Kolab Systems) (Kolab > Systems AG) " > gpg: aka "Jeroen van Meeuwen (Ergo Project) (Ergo Project) > " > gpg: WARNING: This key is not certified with a trusted signature! > gpg: There is no indication that the signature belongs to the > owner. > Primary key fingerprint: C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08 > > -- > Daniel O'Connor software and network engineer > for Genesis Software - http://www.gsoft.com.au > "The nice thing about standards is that there > are so many of them to choose from." > -- Andrew Tanenbaum > GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C > > > > > > > Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
