[Dovecot] Another 1.1rc1 signal 6 crash (with backtrace)
Core was generated by /usr/local/libexec/dovecot/imap'. Program terminated with signal 6, Aborted. #0 0xb7fb6410 in __kernel_vsyscall () (gdb) bt #0 0xb7fb6410 in __kernel_vsyscall () #1 0xb7e85f15 in raise () from /lib/i686/cmov/libc.so.6 #2 0xb7e87891 in abort () from /lib/i686/cmov/libc.so.6 #3 0x080ce499 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80e8f54 Trying to close mailbox %s with open transactions, args=0xbfbcb174 ��\020\b\230�\005\b�s\020\b\207\025\016\b\n) at failures.c:415 #4 0x080ce0ec in i_panic (format=0x80e8f54 Trying to close mailbox %s with open transactions) at failures.c:187 #5 0x0809fad6 in mailbox_close (_box=0x6) at mail-storage.c:471 #6 0x0805f9db in cmd_logout (cmd=0x81079c0) at cmd-logout.c:18 #7 0x08061c59 in client_command_input (cmd=0x81079c0) at client.c:546 #8 0x08061cee in client_command_input (cmd=0x81079c0) at client.c:595 #9 0x08062483 in client_handle_input (client=0x8107388) at client.c:636 #10 0x0806269e in client_input (client=0x8107388) at client.c:691 #11 0x080d5d87 in io_loop_handler_run (ioloop=0x81039b0) at ioloop-epoll.c:201 #12 0x080d5038 in io_loop_run (ioloop=0x81039b0) at ioloop.c:301 #13 0x08069f3d in main (argc=Cannot access memory at address 0x405e ) at main.c:293 Corresponding log: Feb 27 07:01:45 postamt dovecot: IMAP(sriese): Trying to close mailbox CharitAOk- with open transactions Feb 27 07:01:45 postamt dovecot: IMAP(sriese): Raw backtrace: /usr/local/libexec/dovecot/imap [0x80ce490] - /usr/local/libexec/dovecot/imap [0x80ce0ec] - /usr/local/libexec/dovecot/imap [0x809fad6] - /usr/local/libexec/dovecot/imap(cmd_logout+0x3b) [0x805f9db] - /usr/local/libexec/dovecot/imap [0x8061c59] - /usr/local/libexec/dovecot/imap [0x8061cee] - /usr/local/libexec/dovecot/imap [0x8062483] - /usr/local/libexec/dovecot/imap(client_input+0x5e) [0x806269e] - /usr/local/libexec/dovecot/imap(io_loop_handler_run+0xf7) [0x80d5d87] - /usr/local/libexec/dovecot/imap(io_loop_run+0x28) [0x80d5038] - /usr/local/libexec/dovecot/imap(main+0x45d) [0x8069f3d] - /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7e71450] - /usr/local/libexec/dovecot/imap [0x805c361] Feb 27 07:01:45 postamt dovecot: child 16478 (imap) killed with signal 6 -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Computer /nm./: a device designed to speed and automate errors. -- From the Jargon File.
[Dovecot] maildir directory structure
Hi list, I would like my mail directory structure to be like this: /var/vmail/firstletterdomain/domain/username what would be the syntax in dovecot.conf? Thanks, chantal
[Dovecot] Quota Warning problems
Hello, list!
Seems that quota warning feature doesn't work for me.
I have dovecot-1.0.9 with quota-rewrite patch
(http://dovecot.org/patches/1.0/quota-rewrite-1.0.9.diff). Dovecot works as
imap, pop3 server and lda for postfix.
Here is plugin section in dovecot.conf
/etc/dovecot.conf
...
plugin {
quota = maildir
quota_rule = *:storage=10M
quota_warning = storage=50%% /usr/local/bin/quota-warning.sh 50
quota_warning2 = storage=20%% /usr/local/bin/quota-warning.sh 80
}
cut
/usr/local/bin/quota-warning.sh
#!/bin/sh
echo Test /tmp/script.txt
cut
shell
# /usr/local/dovecot-1.0.9/sbin/dovecot -c
/usr/local/dovecot-1.0.9/etc/dovecot.conf
ILoading modules from directory: /usr/local/dovecot-1.0.9/lib/dovecot/imap
IModule loaded: /usr/local/dovecot-1.0.9/lib/dovecot/imap/lib10_quota_plugin.so
IModule loaded:
/usr/local/dovecot-1.0.9/lib/dovecot/imap/lib11_imap_quota_plugin.so
IEffective uid=65534, gid=65534, home=
IQuota root: name= backend=maildir args=
IQuota rule: root= mailbox= bytes=10485760 messages=0
IQuota warning: bytes=5242880 messages=0
command=/usr/local/bin/quota-warning.sh 50
IQuota warning: bytes=2097152 messages=0
command=/usr/local/bin/quota-warning.sh 80
cut
But when user accept 8MB size mail script doesn't execute. There is no
script.txt in /tmp.
Permissions on /usr/local/bin/quota-warning.sh is 755, owner root.
shell
# cat /home/virtual/devel.sitek.net/tolya/Maildir/maildirsize
10485760S,0C
7983577 1
cut
How can I debug and find out why script doesn't work?
Thank you.
P.S. Sorry for my English.
P.P.S. Quota rules work perfectly.
--
Best regards,
Anatoly Bashmakov
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
This is included in my patch already, but Timo didn't want to commit it, since [0] is gcc specific, and [] is C99 standard. Kevin A. McGrail schrieb: As a follow-up on this, these two lines also helped me to compile the 1.1rc1 on gcc 2.96: diff -ru dovecot-1.1.beta13/src/lib/str-find.c dovecot-1.1.beta13.patched/src/lib/str-find.c --- dovecot-1.1.beta13/src/lib/str-find.c Tue Oct 23 16:01:16 2007 +++ dovecot-1.1.beta13.patched/src/lib/str-find.c Thu Jan 17 14:08:03 2008 @@ -12,7 +12,7 @@ unsigned int match_count; int badtab[UCHAR_MAX+1]; - int goodtab[]; + int goodtab[0]; }; static void init_badtab(struct str_find_context *ctx) diff -ru dovecot-1.1.beta13/src/lib-imap/imap-match.c dovecot-1.1.beta13.patched/src/lib-imap/imap-match.c --- dovecot-1.1.beta13/src/lib-imap/imap-match.cSun Dec 9 19:14:27 2007 +++ dovecot-1.1.beta13.patched/src/lib-imap/imap-match.cThu Jan 17 14:09:02 2008 @@ -19,7 +19,7 @@ struct imap_match_pattern *patterns; char sep; - char patterns_data[]; + char patterns_data[0]; }; -- http://sven.anderson.deBelieve those who are seeking the truth. tel:+49-551-9969285 Doubt those who find it. mobile: +49-179-4939223 (André Gide)
Re: [Dovecot] Another 1.1rc1 signal 6 crash (with backtrace)
* Ralf Hildebrandt [EMAIL PROTECTED]: Core was generated by /usr/local/libexec/dovecot/imap'. Client: Microsoft Office Outlook 2003 SP2 (Microsoft Office Professional Edition 2003) -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de Penguins are knocking at the door. Check your winter equipment, Bill
[Dovecot] How can I see the last login time vuserinfo when I login to imap server ?
Hello I use dovecot-1.0.7 for imap. I also use vpopmail5.4.x. on qmail. It works well so far. But when I log in to imap server, I could not see the last login time vuserinfo command in vpopmail. How can I correct that ? Thanks.
Re: [Dovecot] maildir directory structure
Have a read of http://wiki.dovecot.org/Variables On Wed, 2008-02-27 at 09:46 +0100, Chantal Rosmuller wrote: Hi list, I would like my mail directory structure to be like this: /var/vmail/firstletterdomain/domain/username what would be the syntax in dovecot.conf? Thanks, chantal Please consider the environment before printing this email. GAME Stores Group Ltd has been awarded Retailer of the Year at the 2006 Golden Joystick Awards and 'Thames Valley Business Award' for Outstanding Employer of Choice 2006. This e-mail and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this e-mail in error please notify the system manager at: mailto:[EMAIL PROTECTED] The recipient acknowledges that the transmissions made via the Internet can be corrupted and therefore THE GAME GROUP PLC and any of its subsidiaries do not give any warranty as to the quality or accuracy of any information contained in the message or assume any liability for it or for its transmission, reception or storage. This footnote also confirms that this e-mail message has been swept by anti-virus software for the presence of computer viruses. http://www.game.co.uk http://www.gamegroup.plc.uk Registered Number: 1937170 Registered Office: Unity House, Telford Road, Basingstoke, Hampshire. RG21 6YJ Registered in England and Wales.
[Dovecot] nur update behind compiling to 1.1rc1
hi together, behind the update on suse 10.3 to 1.1rc1 from http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc1.tar.gz there was now change aof dovecot version. (./configure make make install) dovecot --version 1.0.5 there was no error at compiling. -- Die Frau zum Mann, der in der Theaterpause im Foyer ein großes Bier bestellt: Du hast doch versprochen, zwei Monate lang keinen Alkohol zu trinken! Darauf der Gatte: Schatz, laut Theaterzettel liegt zwischen dem ersten und dem zweiten Akt ein Zeitraum von einem Jahr! * Dies ist ein Zufallstext und hat nichts mir dem Empfänger der Mail zu tun
[Dovecot] Index corruption with squirrelmail.
Hi. I don't know if the problem is related with squirrelmail or not, but I started to have index corruption when I started to try squirrelmail. Some informaton about my instalation: dovecot 1.0.5-1 debian package with maildir squirrelmail 1.4.9a-2 debian package Some log information: dovecot: 2008-02-27 08:39:39 Warning: IMAP(please don't send spam to me): fscking index file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index dovecot: 2008-02-27 08:39:39 Error: IMAP(please don't send spam to me): Unexpected transaction log desync with index /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index I'm not pretty sure, but it looks like that if I keep my thunderbird open, receive a message and a rule move the message from INBOX to some other folder and then, finally, I try to login in squirrelmail I reveive a message like this: Query: EXPUNGE And in my log file the above message appears. I already deleted dovecot.* files, but the error ocurred again. Any suggestion? Thanks!
Re: [Dovecot] Index corruption with squirrelmail.
On 2/27/2008, Fábio M. Catunda ([EMAIL PROTECTED]) wrote: dovecot 1.0.5-1 debian package with maildir squirrelmail 1.4.9a-2 debian package They're both older... The first thing I always do if I am having a problem with a certain app is make sure I'm running current versions. Backports will have current versions of both of these... -- Best regards, Charles
Re: [Dovecot] Index corruption with squirrelmail.
Charles Marcus escreveu: On 2/27/2008, Fábio M. Catunda ([EMAIL PROTECTED]) wrote: dovecot 1.0.5-1 debian package with maildir squirrelmail 1.4.9a-2 debian package They're both older... The first thing I always do if I am having a problem with a certain app is make sure I'm running current versions. Backports will have current versions of both of these... Yeap, but they are in stable tree. Do you believe that this is a version problem? Thanks!
Re: [Dovecot] Index corruption with squirrelmail.
On Feb 27, 2008, at 2:24 PM, Fábio M. Catunda wrote: dovecot: 2008-02-27 08:39:39 Warning: IMAP(please don't send spam to me): fscking index file /var/virtual/contactnet.com.br/fcatunda/ Maildir/dovecot.index There isn't anything else before this line? Something causes fsck, which causes: dovecot: 2008-02-27 08:39:39 Error: IMAP(please don't send spam to me): Unexpected transaction log desync with index /var/virtual/ contactnet.com.br/fcatunda/Maildir/dovecot.index What filesystem do you use? Do you use NFS? Show your dovecot -n output? PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Another 1.1rc1 signal 6 crash (with backtrace)
* Timo Sirainen [EMAIL PROTECTED]: On Feb 27, 2008, at 10:26 AM, Ralf Hildebrandt wrote: fmt=0x80e8f54 Trying to close mailbox %s with open transactions, Was this with or without http://hg.dovecot.org/dovecot-1.1/rev/0917df31efec ? With! -- Ralf Hildebrandt ([EMAIL PROTECTED]) [EMAIL PROTECTED] Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de ...Yet terrible as UNIX addiction is, there are worse fates. If UNIX is the heroin of operating systems, then VMS is barbiturate addiction, the Mac is MDMA, and MS-DOS is sniffing glue. (Windows is filling your sinuses with lucite and letting it set.) You owe the Oracle a twelve-step program. -- The Usenet Oracle
Re: [Dovecot] Dovecot NFS Indexes and IMAP Migration
On Feb 27, 2008, at 8:49 AM, Andy Dills wrote: From reading the docs, it appears I would not be able to use the dovecot LDA due to locking issues (bummer), and I should configure dovecot to store index files on a local disk of the primary pop/imap server rather than on the netapp. I don't think locking is an issue. NFS caching is more problematic. But with v1.1's mail_nfs_*=yes settings there should be no problems with storing indexes on NFS. My first question would be, how much of a performance hit should I expect from having to update the indexes when mail is checked rather then when mail is delivered since I can't use the LDA? Is this a minor issue like I expect, or can it be something the user actually notices when checking mail? It's a minor issue usually. In a worst case scenario, if the pop/imap server is down, and another server is used, how long would it take to create an index for an account with a few hundered megs, several thousand messages? I'm wondering if, since I have plenty of overhead available on the netapp, I should just store the indexes there in case another server must be used. The actual index file creation is really fast. More problematic is losing dovecot.index.cache file for clients that want to fetch/search old data. But Courier/Binc did no caching at all, so Dovecot wouldn't be any worse. First off, I can't seem to find any info on a way to create an initial index file for all of the mailboxes. Can anybody suggest a command I can use for this? I'm sure I just overlooked it. I don't think you should worry about it. Like I said, the dovecot.index.cache file generation is the slow part. But since its generation depends entire on what fields client is using, you can't really pregenerate it properly anyway. http://wiki.dovecot.org/IndexFiles tries to describe this. http://imapwiki.org/Benchmarking might have more understandable explanation as well. Fortunately, courier is used for normal imap on 143, bincimap is only used for webmail. So, it would seem that metadata from bincimap could be ignored; the only thing it would seem important to preserve is mailbox subscriptions. Please correct this assumption if I'm wrong. Right. So, it seems like my best option is to modify the courier-dovecot-migrate.pl script to consider the mailboxes subscribed to via bincimap. Here's a modified convert_subscriptions that seems to work well in limited testing, feel free to point out any idiot mistakes, it's been a while since I've done anything substantial in perl. I'm not that great perl coder either. :) PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] deliver procmail
On Feb 27, 2008, at 4:36 PM, Carsten Henkel wrote: procmail: Program failure (64) of /usr/local/libexec/dovecot/deliver #define EX_USAGE64 /* command line usage error */ How do you call deliver? PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] deliver procmail
On Feb 27, 2008, at 4:49 PM, Carsten Henkel wrote: DELIVER=/usr/local/libexec/dovecot/deliver :0 w | $DELIVER Maildir There shouldn't be Maildir in there. deliver reads dovecot.conf to figure out where your mails are located. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Dovecots default NTLM Version
On 056, 02 25, 2008 at 12:57:19PM +0200, Timo Sirainen wrote: On Feb 24, 2008, at 11:21 PM, [EMAIL PROTECTED] wrote: I'm not sure what NTLM version is used as default by authentication between Outlook and dovecot and I couldn't find it out with a packet sniffer. I think its NTLMv2 but I'm not sure so I'm asking here. I know that NTLMv1 is not secure against a man in the middle. I didn't write the NTLM code, but as far as I understand it, NTLMv2 is used if both client and server negotiates it. But then again I'd think a MITM could force v1 to be negotiated and then attack that, so it doesn't seem all that secure that way either.. Maybe it's prevented in some way. I think the password hashes also affect this somehow. Maybe NTLM passwords work for v2 and LM passwords for v1? Maybe Andrey can shed some light into this? :) Ugh, I need to recall all this crap myself first :) Actually there is 4 authentication submethods inside the NTLM: LM - server nonce only, highly vulnerable to MITM and rogue server attacks; NTLM- different algorithm, almost equally vulnerable as LM today; NTLM2 - server and client nonce, but MITM can force downgrade to NTLM/LM; NTLMv2 - server and client nonce, MITM can't force downgrade. NTLM password hash is required for NTLM, NTLM2 and NTLMv2. NTLMv2 can not be negotiated. It must be explicitly enabled on the client side by setting registry key below to at least 3. Win9x: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\LMCompatibility WinNT: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA\LMCompatibilityLevel If you want more info about ugly NTLM internals, you can find them here: http://ubiqx.org/cifs/ and here http://davenport.sourceforge.net/ntlm.html Dovecot uses logic outlined below to handle all this insanity: 1. If we have only LM password hash, try LM authentication; 2 If client sends LM response only (some very old clients do it), try LM too; 3. If NTLMv2 is guessed (using client response length), try NTLMv2; 4. If NTLM2 was negotiated, try it; 5. Otherwise try NTLM. Best regards. -- Andrey Panin| Linux and UNIX system administrator [EMAIL PROTECTED] | PGP key: wwwkeys.pgp.net signature.asc Description: Digital signature
Re: [Dovecot] Index corruption with squirrelmail.
Timo Sirainen escreveu: On Feb 27, 2008, at 2:24 PM, Fábio M. Catunda wrote: There isn't anything else before this line? Something causes fsck, which causes: Now I have some more messages: dovecot: 2008-02-27 10:30:18 Error: IMAP(e-mail address): Corrupted index cache file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index.cache: indexid changed dovecot: 2008-02-27 10:31:06 Error: IMAP(e-mail address): Corrupted transaction log file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index.log: invalid indexid (1204119018 != 1204118656) dovecot: 2008-02-27 10:31:06 Warning: IMAP(e-mail address): fscking index file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index dovecot: 2008-02-27 10:31:06 Error: IMAP(e-mail address): Transaction log file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index.log: marked corrupted dovecot: 2008-02-27 10:31:06 Error: IMAP(e-mail address): Corrupted transaction log file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index.log: invalid new transaction log sequence (3 = 3) dovecot: 2008-02-27 10:31:06 Warning: IMAP(e-mail address): fscking index file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index dovecot: 2008-02-27 10:31:06 Error: IMAP(e-mail address): file mail-transaction-log-view.c: line 107 (mail_transaction_log_view_set): assertion failed: (min_file_seq = max_file_seq) dovecot: 2008-02-27 10:31:06 Error: IMAP(e-mail address): Raw backtrace: imap [0x80ae0e1] - imap [0x80adffc] - imap(mail_transaction_log_view_set+0x55a) [0x809c72a] - imap [0x80971e2] - imap(mail_index_view_sync_begin+0xa6) [0x8097526] - imap(index_mailbox_sync_init+0x84) [0x80863b4] - imap(maildir_storage_sync_init+0x8a) [0x806ac7a] - imap(imap_sync_init+0x40) [0x8063dd0] - imap(cmd_sync+0x7b) [0x8063f0b] - imap [0x805992f] - imap(cmd_fetch+0x2ca) [0x8059c7a] - imap(cmd_uid+0x50) [0x805cb60] - imap [0x805d0ef] - imap [0x805d17c] - imap(_client_input+0x6f) [0x805d81f] - imap(io_loop_handler_run+0x107) [0x80b3ed7] - imap(io_loop_run+0x1c) [0x80b315c] - imap(main+0x47c) [0x80657ac] - /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7e01450] - imap [0x8058391] dovecot: 2008-02-27 10:31:06 Error: child 4281 (imap) killed with signal 6 dovecot: 2008-02-27 10:31:06 Error: IMAP(e-mail address): Transaction log file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index.log: marked corrupted This is the first time that I see this mail-transaction-log-view.c line. What filesystem do you use? Do you use NFS? Show your dovecot -n output? ext3 filesystem, it's not a NFS mount. And here it goes dovecot -n output: # 1.0.5: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/error.log info_log_path: /var/log/dovecot/info.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: no version_ignore: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_greeting: Bem Vindo. login_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_process_size: 128 login_processes_count: 4 login_max_processes_count: 64 first_valid_uid: 0 last_valid_uid: first_valid_gid: 0 last_valid_gid: mail_extra_groups: mail mailsystem mail_location: maildir:/var/virtual/%d/%n/Maildir mail_cache_fields: mail_never_cache_fields: maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_process_size: 512 mail_plugins(default): lazy_expunge mail_log mail_plugins(imap): lazy_expunge mail_log mail_plugins(pop3): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_log_max_lines_per_sec: 0 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private prefix: INBOX. inbox: yes namespace: type: private separator: / prefix: .EXPUNGED/ location: maildir:/var/virtual/%d/%n/Maildir/expunged hidden: yes namespace: type: private separator: / prefix: .DELETED/ location: maildir:/var/virtual/%d/%n/Maildir/deleted hidden: yes namespace: type: private separator: / prefix: .DELETED/.EXPUNGED/ location: maildir:/var/virtual/%d/%n/Maildir/deleted/expunged auth default: username_format: %u passdb: driver: ldap
Re: [Dovecot] Auth_cache not working?
On Wed, 2008-02-27 at 17:33 +0100, Jan van den Berg wrote: Sort of the same thing: but more inconsistent. Sometimes I click five folders and OE will have done 3 logins sometimes 2. So new IMAP logins for (more or less) every click in Thunderbird and OE; this is what auth_cache_size should solve right? No. Dovecot can't affect how and when clients create new connections. auth_cache only reduces number of SQL queries when authenticating. You can determine if it works by adding auth_debug=yes and checking Hit and Miss log lines. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Optional Sieve includes
Steffen Kaiser wrote: Well, it's all open source, did you look at it? It shouldn't be too hard to just ignore the result of include, no? Yeah, I did look. I sure could patch something together. Before doing that, though, I hoped to be enlightened with an official way, so I would not have to drag around obscure modifications. Probably the cron script is how it will end up. Anders.
Re: [Dovecot] Optional Sieve includes
On Wed, 2008-02-27 at 20:32 +0100, Anders wrote: Steffen Kaiser wrote: Well, it's all open source, did you look at it? It shouldn't be too hard to just ignore the result of include, no? Yeah, I did look. I sure could patch something together. Before doing that, though, I hoped to be enlightened with an official way, so I would not have to drag around obscure modifications. I don't think there will be any upstream modifications at least: SIEVE implementations MUST handle missing scripts being referenced via an includes in an existing script. An error MUST be generated when a missing included script is descovered during execution. Then again the include draft expired over a year ago. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
On Wed, 27 Feb 2008, Timo Sirainen wrote: On Feb 27, 2008, at 4:22 PM, Kevin A. McGrail wrote: I can't argue with that logic but documenting it in a wiki or INSTALL or including the patches with the distribution might be more agreeable. Why are you people still using so old gcc versions? As an observer, I'd like to remark that it's amazing that twentiety-century known-broken non-releases http://gcc.gnu.org/gcc-2.96.html of GCC are in use in 2008. I'm honestly curious what keeps you guys on them. -- Asheesh. -- Maybe you can't buy happiness, but these days you can certainly charge it.
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
Well, for me, it's a vast number of boxes deployed and often maintained by others that are running stabling for 8+ years making the nuance of upgrading to a newer version of GCC fairly mute from a lay persons perspective. Seriously, how can you argue with a non-technical user that their box installed in 2001 has a problem when everything is working fine? Plus it annoys Timo and that's just an extra bonus ;-) regards, KAM - Original Message - From: Asheesh Laroia [EMAIL PROTECTED] To: Dovecot Mailing List dovecot@dovecot.org Cc: Kevin A. McGrail [EMAIL PROTECTED]; Sven Anderson [EMAIL PROTECTED] Sent: Wednesday, February 27, 2008 4:35 PM Subject: Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95 On Wed, 27 Feb 2008, Timo Sirainen wrote: On Feb 27, 2008, at 4:22 PM, Kevin A. McGrail wrote: I can't argue with that logic but documenting it in a wiki or INSTALL or including the patches with the distribution might be more agreeable. Why are you people still using so old gcc versions? As an observer, I'd like to remark that it's amazing that twentiety-century known-broken non-releases http://gcc.gnu.org/gcc-2.96.html of GCC are in use in 2008. I'm honestly curious what keeps you guys on them. -- Asheesh. -- Maybe you can't buy happiness, but these days you can certainly charge it.
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
On 2/27/2008, Kevin A. McGrail ([EMAIL PROTECTED]) wrote: Well, for me, it's a vast number of boxes deployed and often maintained by others that are running stabling for 8+ years making the nuance of upgrading to a newer version of GCC fairly mute from a lay persons perspective. Seriously, how can you argue with a non-technical user that their box installed in 2001 has a problem when everything is working fine? Plus it annoys Timo and that's just an extra bonus ;-) All kidding and joking aside... this is pure laziness on the part of the sys admin, nothing more. IF you find this remark offensive, then you must be guilty. The 'client' shouldn't even be involved in such a decision... if you are responsible for a box, it is your responsibility to make sure it is secure - and how can you trust ANYTHING on that box if you are using a broken/buggy compiler? -- Best regards, Charles
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
Am 27.02.2008 um 15:31 schrieb Timo Sirainen: Why are you people still using so old gcc versions? I guess I could accept a patch something like: I'm using an old custom-made vserver system, and it's running fine, so why spend a lot of time to migrate to a newer distribution? Sven -- http://sven.anderson.deBelieve those who are seeking the truth. tel:+49-551-9969285 Doubt those who find it. mobile: +49-179-4939223 (André Gide)
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
on 2/27/2008 2:06 PM Sven Anderson spake the following: Am 27.02.2008 um 15:31 schrieb Timo Sirainen: Why are you people still using so old gcc versions? I guess I could accept a patch something like: I'm using an old custom-made vserver system, and it's running fine, so why spend a lot of time to migrate to a newer distribution? Sven It's running fine until it gets rooted/compromised. Then what do you do? -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Follow-up re: gcc 2.96 - Re: PATCH: compile dovecot-1.1.beta14 with gcc 2.95
on 2/27/2008 1:46 PM Kevin A. McGrail spake the following: Well, for me, it's a vast number of boxes deployed and often maintained by others that are running stabling for 8+ years making the nuance of upgrading to a newer version of GCC fairly mute from a lay persons perspective. Seriously, how can you argue with a non-technical user that their box installed in 2001 has a problem when everything is working fine? How much longer can a system be expected to run? 8+ years at 24/7 is about a half a million hours. Drives are getting old and expensive to replace. Processors are probably slow. Energy use is high. Motherboard capacitors are probably drying up. The systems are past a safe point and are getting closer to the great e-waste pile in the sky. And why would someone install the same old OS on new hardware, and would it support it. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Index corruption with squirrelmail.
Some addional information that I found: This problem started on 02/21/2008 when I moved a message that has id 1191941480.M342094P9293V0903I003B9713_0.cronos from .Spam folder to INBOX and then moved the message back to .Spam folder. Today this message looks to be causing the problem still! See some loggging: dovecot: 2008-02-27 17:55:33 Error: IMAP([EMAIL PROTECTED]): Maildir /var/virtual/contactnet.com.br/fcatunda/Maildir sync: UID inserted in the middle of mailbox (8055 8042, file = 1191941480.M342094P9293V0903I003B9713_0.cronos,S=3129:2,ST) dovecot: 2008-02-27 17:57:46 Error: IMAP([EMAIL PROTECTED]): Corrupted index cache file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index.cache: indexid changed dovecot: 2008-02-27 20:17:57 Error: IMAP([EMAIL PROTECTED]): Maildir /var/virtual/contactnet.com.br/fcatunda/Maildir sync: UID inserted in the middle of mailbox (8055 8042, file = 1191941480.M342094P9293V0903I003B9713_0.cronos,S=3129:2,ST) I don't know if it helps or not, but I believe that this is a good tip about the problem. Thanks. Timo Sirainen escreveu: On Feb 27, 2008, at 2:24 PM, Fábio M. Catunda wrote: dovecot: 2008-02-27 08:39:39 Warning: IMAP(please don't send spam to me): fscking index file /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index There isn't anything else before this line? Something causes fsck, which causes: dovecot: 2008-02-27 08:39:39 Error: IMAP(please don't send spam to me): Unexpected transaction log desync with index /var/virtual/contactnet.com.br/fcatunda/Maildir/dovecot.index What filesystem do you use? Do you use NFS? Show your dovecot -n output?
Re: [Dovecot] Dovecot NFS Indexes and IMAP Migration
On Wed, 27 Feb 2008, Timo Sirainen wrote: On Feb 27, 2008, at 8:49 AM, Andy Dills wrote: From reading the docs, it appears I would not be able to use the dovecot LDA due to locking issues (bummer), and I should configure dovecot to store index files on a local disk of the primary pop/imap server rather than on the netapp. I don't think locking is an issue. NFS caching is more problematic. But with v1.1's mail_nfs_*=yes settings there should be no problems with storing indexes on NFS. That's good to know. Do you view 1.1 as production ready now, or should I wait for an official release? It sounds production ready in the RC1 release notes, but I was curious how much remains on your few issues you'd like to fix list and how relevant they are to my environment. Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 ---
Re: [Dovecot] deliver procmail
Timo Sirainen wrote: On Feb 27, 2008, at 4:49 PM, Carsten Henkel wrote: DELIVER=/usr/local/libexec/dovecot/deliver :0 w | $DELIVER Maildir There shouldn't be Maildir in there. deliver reads dovecot.conf to figure out where your mails are located. Sorry for jumping in this thread. I am currently using Dovecot as my IMAP and POP server. I am using Sendmail as my MTA and Procmail as my LDA. Would I gain anything by using Deliver through Procmail like the above example is? My server is just a small home server with very little e-mail traffic. Thanks, Jeff
Re: [Dovecot] too little data error still occurring in 1.0.10
Timo Sirainen wrote: On Tue, 2008-02-12 at 20:28 -0700, Mike Brown wrote: Timo Sirainen wrote: On Feb 12, 2008, at 1:14 AM, Mike Brown wrote: Timo Sirainen wrote: On Sat, 2008-02-09 at 02:53 -0700, Mike Brown wrote: I'm running dovecot 1.0.10, but am seeing the too little data error that was supposedly fixed in 1.0.9. Not sure how long it's been going on. Did you try deleting dovecot.index.cache files from those mailboxes and see if it comes back? I tried that just now, and so far, things are back to normal. Thanks! I guess I don't need the patch. Do you want me to try it anyway? Try the patch if the problem comes back. The problem came back, so I will apply the patch. :( Did the patch fix it? As far as I can tell. The problem hasn't returned since I applied the patch 2 weeks ago. Thanks!
[Dovecot] imaptest update
I've finally added support for normal command/reply tests for my
imaptest program (http://imapwiki.org/ImapTest).
My plan is that imaptest will include some generic IMAP compliancy tests
and Dovecot will include some more strict Dovecot-specific checks. make
dist will run all these tests before building a tarball, so in future I
shouldn't be able to release horribly broken versions. :)
I haven't yet had time to implement all the features that I'd like (e.g.
unordered list handling needs support), but I think the current features
will allow testing quite a lot already.
http://imapwiki.org/ImapTest/Tests explains how it works.
There are currently two files: the actual test file and *.mbox file
where the mails are appended from to the test mailbox. I'm going to also
add *.conf file which allows specifying specific dovecot.conf settings.
This way I can test all these different namespace (etc.) variations as
well.
A couple of examples to show what's possible:
# Check that EXAMINE and STATUS return same UIDVALIDITY
examine $mailbox
* ok [uidvalidity $uidvalidity]
ok [read-only]
ok status $mailbox (uidvalidity)
* status $mailbox (uidvalidity $uidvalidity)
# Test EXPUNGE handling with 2 connections:
connections: 2
1 ok fetch * uid
* $seq fetch (uid $uid)
1 ok store $seq flags \deleted
* $seq fetch (flags (\deleted \recent))
1 ok expunge
* $seq expunge
2 ok fetch $seq uid
* $seq fetch (uid $uid)
2 ok noop
* $seq expunge
# LIST testing:
state: auth
ok list
* list (\noselect) $sep
# means that delete can return anything
# (although restricting it to ok or no would be better)
delete $mailbox${sep}test
delete $mailbox${sep}test2
ok create $mailbox${sep}test
ok create $mailbox${sep}test2
ok list $mailbox$sep%
* list (\hasnochildren) $sep $mailbox${sep}test
* list (\hasnochildren) $sep $mailbox${sep}test2
signature.asc
Description: This is a digitally signed message part
