Re: [Dovecot] Indexes to MLC-SSD
I can't imagine running any kind of performance critical app on linux using fuse! There is a native ZFS port going on, but I don't know how stable it is yet. -Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Patrick Westenberg Sent: Tuesday, November 01, 2011 5:19 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] Indexes to MLC-SSD Dovecot-GDH schrieb: > If I/O performance is a concern, you may be interested in ZFS and Flashcache. > > Specifically, ZFS' ZIL (ZFS Intent Log) and its L2ARC (Layer 2 Adaptive Read Cache) > ZFS does run on Linux http://zfs-fuse.net I'm using NexentaStor (Solaris, ZFS) to export iSCSI-LUNs and I was thinking about a SSD based LUN for the indexes. As I'm using multiple servers this LUN will use OCFS2.
Re: [Dovecot] Indexes to MLC-SSD
Dovecot-GDH schrieb: If I/O performance is a concern, you may be interested in ZFS and Flashcache. Specifically, ZFS' ZIL (ZFS Intent Log) and its L2ARC (Layer 2 Adaptive Read Cache) ZFS does run on Linux http://zfs-fuse.net I'm using NexentaStor (Solaris, ZFS) to export iSCSI-LUNs and I was thinking about a SSD based LUN for the indexes. As I'm using multiple servers this LUN will use OCFS2.
Re: [Dovecot] Indexes to MLC-SSD
If I/O performance is a concern, you may be interested in ZFS and Flashcache. Specifically, ZFS' ZIL (ZFS Intent Log) and its L2ARC (Layer 2 Adaptive Read Cache) ZFS does run on Linux http://zfs-fuse.net Flashcache: https://github.com/facebook/flashcache/ Both of these techniques can use a pair of SSDs in RAID1 rather than a single SSD. On Oct 27, 2011, at 1:31 AM, Ed W wrote: > On 27/10/2011 03:36, Stan Hoeppner wrote: >> On 10/26/2011 4:13 PM, Patrick Westenberg wrote: >>> Hi all, >>> >>> is anyone on this list who dares/dared to store his index files on a >>> MLC-SSD? >> I have not. But I can tell you that a 32GB Corsair MLC SSD in my >> workstation died after 4 months of laughably light duty. It had nothing >> to do with cell life but low product quality. This was my first foray >> into SSD. The RMA replacement is still kickin after 2 months, >> thankfully. I'm holding my breath... >> >> Scanning the reviews on Newegg shows early MLC SSD failures across most >> brands, early being a year or less. Some models/sizes are worse than >> others. OCZ has a good reputation overall, but reviews show some of >> their models to be grenades. >> >> Thus, if you were to put indexes on SSD, you should strongly consider >> using a mirrored pair. >> > > I don't think you are saying that the advice varies here compared with > HDDs? I do agree that some SSDs are showing very early failures, but > it's only a tweak to the probability parameter compared with any other > storage medium. They ALL fail at some point, and generally well within > the life of the rest of the server. Some kind of failure planning is > necessary > > Caveat the potentially higher failures vs HDDs I don't see any reason > why an SSD shouldn't work well? (even more so if you are using maildir > where indexes can be regenerated). > > More interestingly: for small sizes like 32GB, has anyone played with > the "compressed ram with backing store" thing in newer kernels (that I > forget the name of now). I think it's been marketed for swap files, but > assuming I got the theory it could be used as a ram drive with slow > writeback to permanent storage? > > Good luck > > Ed W
[Dovecot] looking for Dovecot-code + SQL consultants
Hi, We're using Dovecot2. Trying, given our own spread-too-thin bandwidth, to make it work within our evolving SQL application environment. When there's a problem, we post to this list (e.g., http://www.dovecot.org/list/dovecot/2011-October/061609.html), but aren't getting any/timely responses. We've decided to look for a consultant (hourly or retainer) that can be available for working with our in-house staff to straighten these issues out -- by helping us identify & fix our own mess, and by working to get fixes pushed to Dovecot project code, where appropriate. If you provide these services, rather than simply deployment or hosting, and are available, please drop me a line *offlist*. We're in the San Francisco area, and local is best, but remote work is certainly an option. Thanks, Rich
Re: [Dovecot] setting namespaces using script-login environment in 2.0
On 10/31/2011 06:41 PM, e-frog wrote: > On 31.10.2011 18:00, wrote Alexander 'Leo' Bergolth: >> Have environment based namespace settings been abandoned in 2.0? >> > I think you need to add them to USERDB_KEYS now... > > http://wiki2.dovecot.org/PostLoginScripting#Running_environment I have added NAMESPACE_1 NAMESPACE_1_SEP NAMESPACE_1_TYPE NAMESPACE_1_LIST NAMESPACE_1_PREFIX to USERDB_KEYS. Unfortunately the namespace still isn't used. :-( --leo -- e-mail ::: Leo.Bergolth (at) wu.ac.at fax ::: +43-1-31336-906050 location ::: IT-Services | Vienna University of Economics | Austria
[Dovecot] LDAP w/SASL "Active Directory" authentication failing.
Hello, I am running a Dovecot server (version 1.2.17) on FreeBSD 8.2, using LDAP to authenticate Active Directory users. I can successfully bind and authenticate using PLAIN and LDAP without SASL, but obviously passwords for the bind user and the user being authenticated are being passed in plain text. I've attempted to configure my server to us SASL however when I attempt to authenticate a user I see authentication failures. I reviewed the security log on my domain controller and see that the bind user is binding properly, so the issue appears to be orginating from the user authentication, however I cannot determine what the issue is. Here is all the information regarding my configuration, along with the logs from the server: Dovecot -n # 1.2.17: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-RELEASE i386 ufs log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot_info.log protocols: imap pop3 imaps pop3s ssl_cert_file: /etc/ssl/dovecot/cert.pem ssl_key_file: /etc/ssl//dovecot/key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login valid_chroot_dirs: /usr/data/vmail verbose_proctitle: yes first_valid_uid: 1001 last_valid_uid: 1001 first_valid_gid: 1001 last_valid_gid: 1001 mail_privileged_group: mail mail_location: maildir:/usr/data/vmail/%u mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh lda: sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain gssapi ntlm login username_format: %Ln winbind_helper_path: /usr/local/bin/ntlm_auth verbose: yes debug: yes debug_passwords: yes use_winbind: yes passdb: driver: ldap args: /usr/local/etc/dovecot-ldap.conf userdb: driver: static args: uid=vmail gid=vmail home=/usr/data/vmail/%u socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 dovecot-ldap.conf hosts = 192.168.0.240:3268 dn = cn=PostfixBind,ou=IT,ou=Central Office,ou=LMC,dc=smallmountain,dc=Local dnpass = y0urm0mma sasl_bind = yes #sasl_mech = GSSAPI #sasl_realm = smallmountain.local #sasl_authz_id = debug_level = -1 #auth_bind = yes ldap_version = 3 base = dc=smallmountain,dc=Local deref = never scope = subtree user_filter = (&(objectClass=person)(mail=%u)) pass_attrs = mail=user pass_filter = (&(objectClass=person)(sAMAccountName=%n)) dovecot.log Nov 01 09:09:48 dovecot: Warning: Killed with signal 15 (by pid=99758 uid=0 code=kill) Nov 01 09:09:48 auth(default): Error: ldap_pvt_sasl_getmech Nov 01 09:09:48 auth(default): Error: ldap_search Nov 01 09:09:48 auth(default): Error: put_filter: "(objectclass=*)" Nov 01 09:09:48 auth(default): Error: put_filter: simple Nov 01 09:09:48 auth(default): Error: put_simple_filter: "objectclass=*" Nov 01 09:09:48 auth(default): Error: ldap_build_search_req ATTRS: supportedSASLMechanisms Nov 01 09:09:48 auth(default): Error: ldap_send_initial_request Nov 01 09:09:48 auth(default): Error: ldap_new_connection 1 1 0 Nov 01 09:09:48 auth(default): Error: ldap_int_open_connection Nov 01 09:09:48 auth(default): Error: ldap_connect_to_host: TCP 192.168.0.240:3268 Nov 01 09:09:48 auth(default): Error: ldap_new_socket: 11 Nov 01 09:09:48 auth(default): Error: ldap_prepare_socket: 11 Nov 01 09:09:48 auth(default): Error: ldap_connect_to_host: Trying 192.168.0.240:3268 Nov 01 09:09:48 auth(default): Error: ldap_pvt_connect: fd: 11 tm: -1 async: 0 Nov 01 09:09:48 auth(default): Error: ldap_open_defconn: successful Nov 01 09:09:48 auth(default): Error: ldap_send_server_request Nov 01 09:09:48 auth(default): Error: ldap_result ld 0x18611700 msgid 1 Nov 01 09:09:48 auth(default): Error: wait4msg ld 0x18611700 msgid 1 (infinite timeout) Nov 01 09:09:48 auth(default): Error: wait4msg continue ld 0x18611700 msgid 1 all 1 Nov 01 09:09:48 auth(default): Error: ** ld 0x18611700 Connections: Nov 01 09:09:48 auth(default): Error: * host: 192.168.0.240 port: 3268 (default) Nov 01 09:09:48 auth(default): Error: refcnt: 2 status: Connected Nov 01 09:09:48 auth(default): Error: last used: Tue Nov 1 09:09:48 2011 Nov 01 09:09:48 auth(default): Error: Nov 01 09:09:48 auth(default): Error: Nov 01 09:09:48 auth(default): Error:
Re: [Dovecot] antispam for dovecot 2.0
Am Tue, 1 Nov 2011 07:34:30 -0500 (CDT) Duane Hill schrieb: > On Tue, 1 Nov 2011, Lars Täuber wrote: > > > Hi! > > > > Is there anybody out there who has ported the antispam-storage-1.x.c to > > antispam-storage-2.0.c? > > > > Or is there an alternative to the antispam plugin? > > Don't know anything about antispam-storage. From searching I assume you > mean the antispam plugin for Dovecot 2.x. > > http://wiki2.dovecot.org/Plugins/Antispam shows where you can get it from > and compile. Hallo Duane, thank you very much. This is what I was searching for. Thanks Lars
Re: [Dovecot] antispam for dovecot 2.0
On Tue, 1 Nov 2011, Lars Täuber wrote: Hi! Is there anybody out there who has ported the antispam-storage-1.x.c to antispam-storage-2.0.c? Or is there an alternative to the antispam plugin? Don't know anything about antispam-storage. From searching I assume you mean the antispam plugin for Dovecot 2.x. http://wiki2.dovecot.org/Plugins/Antispam shows where you can get it from and compile.
[Dovecot] antispam for dovecot 2.0
Hi! Is there anybody out there who has ported the antispam-storage-1.x.c to antispam-storage-2.0.c? Or is there an alternative to the antispam plugin? Thanks Lars
Re: [Dovecot] Bad creation timestamp of migrated mails (maildir format)?
On Tue, 1 Nov 2011 08:32:47 +0200, Timo Sirainen wrote:
> On
30.10.2011, at 13.53, Lukas Weiß wrote:
>
>> ive just switched to
dovecot imap because dbmail i used before is not developed any further
>
Oh? It doesn't yet seem dead to me.
>
>> and sql storage is difficult
to backup. Ive done that, by setting up dovecot with maildir format and
copy mails from old dbmail to new dovecot imap server with my mail
client (thunderbird).
> Thunderbird probably changes the INTERNALDATE of
the messages. Copy the mails some other way, like offlineimap or maybe
some other IMAP client.
What is INTERNALDATE? The modification
timestamp is correct ("ls -l"), and the "Date: ... " line, too.
@dbmail: Dead is the wrong designation. But since the last 5 years i
only noticed bugfixes, the most "ideas for developement" (STARTTLS for
example) mentioned here [1] are still ideas.
Links:
--
[1]
http://www.dbmail.org/dokuwiki/doku.php/2.3
