Re: [Dovecot] Account Migration Tool
Hello, goto http://www.linux-france.org/prj/imapsync/ and read the description in the README file. I've never tested this tool. But I think the description matches your 'requirements'. I used to tool to convert dozen of email account with up to 9GB each. No problem at all. Just do not forget to use the --subscribe option :) I also have a little script converting vpasswd files of vpopmail into mysql based accounts which is using imapsync tools to move the existing accounts from the old server to the new one. -- www.stonki.de www.proftpd.de www.kbarcode.net www.krename.net
Re: [Dovecot] Account Migration Tool
* Stefan Onken supp...@stonki.de: Hello, goto http://www.linux-france.org/prj/imapsync/ and read the description in the README file. I've never tested this tool. But I think the description matches your 'requirements'. I used to tool to convert dozen of email account with up to 9GB each. No problem at all. Just do not forget to use the --subscribe option :) Definitely our preferred tool. The last time we used it, we migrated 25.000+ accounts and yes, we enabled --subscribe on the second run too... ;) We also disabled syncing shared folders from the Exchange Servers; they weren't needed on the new system. It's also nice to have a wrapper script that tracks exit codes and writes errors to a log, so you can attend them once the first run has passed through. p...@rick
Re: [Dovecot] Problems with listescape and mutt
Daniel Spannbauer d...@marco.de writes: my ~.muttrc is completly empty. But in my globnal /etc/Muttrc there are some configs. IMHO, there is a script somewhere in your configuration generating the list of mailboxes, and it generates it wrong, probably because it thinks that the maildir structure is of the type LAYOUT=FS, and not Maildir++. folder=imap://d...@homedirs/ spoolfile=imap://d...@homedirs/INBOX This is fine. postponed=imap://d...@homedirs/.Drafts record=imap://d...@homedirs/.Sent This is wrong. imap_list_subscribed is set Not sure about this one, because you told that there were no dots in the subscription file. -- Nicolas
Re: [Dovecot] Problems with listescape and mutt
Nicolas KOWALSKI schrieb: Daniel Spannbauer d...@marco.de writes: my ~.muttrc is completly empty. But in my globnal /etc/Muttrc there are some configs. IMHO, there is a script somewhere in your configuration generating the list of mailboxes, and it generates it wrong, probably because it thinks that the maildir structure is of the type LAYOUT=FS, and not Maildir++. Hmmm, there is truely a small script, which lets mutt find the folders: mailboxes `echo -n + ; find ~/.maildir -maxdepth 1 -type d -name .* -printf +'%f' ` Hmm, I think this is the error Regards Daniel folder=imap://d...@homedirs/ spoolfile=imap://d...@homedirs/INBOX This is fine. postponed=imap://d...@homedirs/.Drafts record=imap://d...@homedirs/.Sent This is wrong. imap_list_subscribed is set Not sure about this one, because you told that there were no dots in the subscription file. -- Daniel Spannbauer Software Entwicklung marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11 Rechbergstr. 4 - 6, D 87727 Babenhausen Mobil +49 171 4033220 http://www.marco.de/ Email d...@marco.de Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
Re: [Dovecot] quote warning not being triggered (yet again)
* Timo Sirainen t...@iki.fi: On Tue, 2009-12-08 at 23:27 +0100, Ralf Hildebrandt wrote: Oh, that could be it. Although there is code to update these % limits when the actual quota limit is read, so in theory it should have worked at least. I'll test it later.. ANy news on that? I have a lot of unhappy users exceeding their quota with no impending DOOM-warning whatsoever Fixed: http://hg.dovecot.org/dovecot-1.2/rev/a9b469e1c8de Yes, it's fixed and working again!! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
[Dovecot] More logging for Deliver (eg file name)
Hello, I can't see from the wiki if it's possible to log extra information with Deliver - such as the file name it's using to save the message in (Maildir). Currently I get the date, address, ID and folder, eg: Dec 09 12:07:06 deliver(my_addr...@invalid): Info: msgid=302ce8b50912090406y634d1340j96ebd54466a2d...@mail.gmail.com: saved mail to INBOX.Lists.centos Thanks. -- Andrew
[Dovecot] [dovecot] Compiling dovecot 2.0 revision 10435:73679e39f072 on AIX
Trying to compile and getting this error: process-title.c, line 139.14: 1506-045 (S) Undeclared identifier argv_memblock. process-title.c, line 140.14: 1506-045 (S) Undeclared identifier environ_memblock. gmake[4]: *** [process-title.lo] Error 1 HAVE_SETPROCTITLE is undefined in config.h -Jonathan smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] More logging for Deliver (eg file name)
On 12/09/2009 01:44 PM Andrew Hearn wrote: Hello, I can't see from the wiki if it's possible to log extra information with Deliver - such as the file name it's using to save the message in (Maildir). The dovecot-example.conf file contains: # Format to use for logging mail deliveries. You can use variables: # %$ - Delivery status message (e.g. saved to INBOX) # %m - Message-ID # %s - Subject # %f - From address #deliver_log_format = msgid=%m: %$ Regards, Pascal -- The trapper recommends today: 5e1f1e55.0934...@localdomain.org
Re: [Dovecot] Max IMAP fodlers
On Dec 8, 2009, at 12:41 AM, Steffen Kaiser wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 7 Dec 2009, Jeffrey Nikoletich wrote: Also is there is hard limit on the amount of folders dovecot can handle? I have a user who has over 3000 folder (including subfolders) that is having issues with delays in loading, moving, and deleting messages. I cannot believe that ext3 chokes on just 3000 directory entries in such situation. I would think that one would notice the same with 20,000 messages per mailbox. Yeah... like i said... it is really weird How about really use another mail client for testing, as Marcus suggested, e.g. some brain-dead MUA, that does not try to be smart, for example Alpine or Mutt :) I have tried... macmail. outlook, thunderbird, entourage... I havent tried mutt but I will now. Also, try to log the session, maybe the user watches all 3000 folders for changes. So they all will be selected in a (short?) period of time again and again. Maybe a firewall in between is casuing a throttle, because of too many connections or something? I have an strace running on the process now just as Timo suggested. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSx4RKnWSIuGy1ktrAQJF4Af/diS3UqhWWiJONM8SntptVn3UH0rLvT+p NoSYfS2/0aVTstuU6vGhntGPsGCPXmSRVuGbW+ERS4U/6C7V9JQuo8Fdf2aYjGKe 2U/LxaodeKBc/c7cZdf4Uthu0z8NScWZJU8nG23EK31e9nlcte0D/eHF132i2zPZ mw+ZxFdgveTA+V4hnRVbUO49mYu3EmePkdbCMwhPOGo9oX5tlgsLzWIuZ5aQ9eph 3bjhH9TPgpWDphEab79pDBjV3WeS5je27L5+58kwW7g3cGneL02BaNztu96w8BPd 9eF+YXVBX3QkbhG3xEwCDdSTrKBYjPF6w4hExMl6ifFHihMNpDi9sg== =NK/w -END PGP SIGNATURE-
[Dovecot] Developer Documentation
Hi Everyone I Try to make a modification in dovecot Maildir system I want to include lines from another file into every email when the user request to read this email. Is Like put some extras itens email. I try to find how to do this but what i understand is, every email is read on the fly, but i dont find exactly where... i didnt find some read to do this. Some one can help me to do this ? Tks !
[Dovecot] Want to simplify [Was:Re: How do i translate the old default_mail_env setting?]
On Mon, Dec 07, 2009 at 03:29:44PM -0800, Gary Kline wrote: On Mon, Dec 07, 2009 at 11:35:43AM -0500, Timo Sirainen wrote: On Sun, 2009-12-06 at 17:13 -0800, Gary Kline wrote: Appreciate it. Is there an overview of your IMAP/POP3 server? Overview, tuturial, what dovecot does? newest features, etc? Well, there's http://wiki.dovecot.org/MailServerOverview and http://dovecot.org/talks/ The fellow who set up dovecoat origially has [ what I believe to be] an unnecessary SASL service. I would like to avoid all redundancies, save CPU, troubles, and so on. ... Your SMTP server might be authenticating using the SASL service. Yes, but because much of this was new I simply followed my friend's guidelines blindly. Here are what I did (cut-and-pasted) without understand much: Let me rephrase my previous post: I had installed the cyrus-sasl2 port. Can I safely remove this now and reply on the builtin dovecot SASL? -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php
Re: [Dovecot] Want to simplify [Was:Re: How do i translate the old default_mail_env setting?]
On Wed, 2009-12-09 at 10:39 -0800, Gary Kline wrote: Your SMTP server might be authenticating using the SASL service. .. Let me rephrase my previous post: I had installed the cyrus-sasl2 port. Can I safely remove this now and reply on the builtin dovecot SASL? You said you built Sendmail with SASL support. Sendmail doesn't support Dovecot SASL. So you need to keep using Cyrus SASL. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
Hi Timo, At 07:32 PM 12/8/2009, Timo wrote: On Dec 8, 2009, at 7:01 PM, Richard Stockton wrote: Here is what we are using with 1.1.19: password_query = SELECT password, home as userdb_home, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox where userid = '%n' mail_location = maildir:/mail/%h:INDEX=MEMORY So you're using relative home directories. Will this still work in 1.2? No. Change it to: password_query = .., '/mail/' || home as userdb_mail, .. Then the mail_location in dovecot.conf will be completely ignored. I assume you meant to have me change it to: password_query = .., '/mail/' || home as userdb_home, .. since there is no mail field in my DB table. This does not appear to work in Dovecot 1.1.19. Sadly, if I can't make a change that works for 1.1.19 as well as 1.2.x, I will be unable to update at this time. Please let me know if my assumptions about 1.1.19 vs 1.2.x are true. Thank you. - Richard
Re: [Dovecot] [dovecot] Compiling dovecot 2.0 revision 10435:73679e39f072 on AIX
On Wed, 2009-12-09 at 07:59 -0500, Jonathan Siegle wrote: Trying to compile and getting this error: process-title.c, line 139.14: 1506-045 (S) Undeclared identifier argv_memblock. process-title.c, line 140.14: 1506-045 (S) Undeclared identifier environ_memblock. gmake[4]: *** [process-title.lo] Error 1 Fixed. HAVE_SETPROCTITLE is undefined in config.h If you want verbose_proctitle=yes, you could try if defining PROCTITLE_HACK manually in config.h makes it work well. I could then make it the default for AIX too. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
On Wed, 2009-12-09 at 11:13 -0800, Richard Stockton wrote: password_query = .., '/mail/' || home as userdb_mail, .. Then the mail_location in dovecot.conf will be completely ignored. I assume you meant to have me change it to: password_query = .., '/mail/' || home as userdb_home, .. since there is no mail field in my DB table. No, I meant userdb_mail. The mail field isn't about having such field in database, but about presenting the mail field to Dovecot. Or actually I messed it up anyway, I meant: password_query = .., 'maildir:/mail/' || home as userdb_mail, .. signature.asc Description: This is a digitally signed message part
[Dovecot] SASL plain authentication failed; unable to lookup user record
i'll guess the solution to my problem will be something simple and obvious, because i know i ain't the first person to do this and it ain't all that complicated, but i've been staring at it for days and can't see what's wrong. new installation; os x snow leopard server; postfix 2.5.5; dovecot 1.1.17apple0.5 i'm trying to get SMTP auth working via SASL. using a plain password scheme and plain auth scheme over SSL. client is apple mail. deliveries are working, and dovecot's pop3s and imaps are working just fine. my configuration is the same simple config that is well documented on both the postfix and dovecot sites. when i attempt to use smtp auth from a mail client, postfix says SASL plain authentication failed unable to lookup user record smtp authentication also fails if i use the usual command line method: # telnet localhost 25 Escape character is '^]'. 220 osx-106.example.com ESMTP Postfix EHLO foobie.example.com 250-osx-106.example.com 250-PIPELINING 250-SIZE 10485760 250-VRFY 250-ETRN 250-AUTH LOGIN PLAIN CRAM-MD5 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH PLAIN blah blah blah 535 Error: authentication failed i've scoured months worth of postfix and dovecot list archives and although there are many sasl related issues i didn't see anything specific to this. as expected, the socket is srw-rw 1 _postfix _postfix 0 Dec 4 08:51 /var/spool/postfix/private/auth lsof shows the socket is open by dovecot-auth (which is running as root): dovecot-a 63614 root5u unix 0x0888b990 0t0 /var/spool/postfix/private/auth i have not seen the socket opened by postfix, but i'm assuming that is a transient event and would be difficult to capture (at least with lsof). so both postfix and dovecot have read/write access to the socket. the credentials sent are the same whether they're sent via a true pop3 client or via the command line. when sent via the command line, they're generated via perl -MMIME::Base64 -e 'print encode_base64(\0username\0password);'and i've verified they're correct via decode_base64 config stuff: # postconf -n biff = no command_directory = /usr/sbin config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 daemon_directory = /usr/libexec/postfix debug_peer_level = 2 enable_server_options = yes header_checks = pcre:/etc/postfix/custom_header_checks html_directory = /usr/share/doc/postfix/html inet_interfaces = all mail_owner = _postfix mailbox_size_limit = 0 mailbox_transport = dovecot mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man message_size_limit = 10485760 mydomain = example.com mydomain_fallback = localhost mynetworks = 127.0.0.0/8,192.168.61.0/24 newaliases_path = /usr/bin/newaliases queue_directory = /private/var/spool/postfix readme_directory = /usr/share/doc/postfix recipient_delimiter = + relayhost = sample_directory = /usr/share/doc/postfix/examples sendmail_path = /usr/sbin/sendmail setgid_group = _postdrop smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject smtpd_enforce_tls = no smtpd_helo_required = yes smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname smtpd_pw_server_security_options = plain, login cram-md5 smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination check_policy_service unix:private/policy reject smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_tls_CAfile = /etc/certificates/osx-106.example.com.E2FA6EFB8203E2E09C605D30A179669E4B4F69EB.chain.pem smtpd_tls_cert_file = /etc/certificates/osx-106.example.com.E2FA6EFB8203E2E09C605D30A179669E4B4F69EB.cert.pem smtpd_tls_exclude_ciphers = SSLv2, aNULL, ADH, eNULL smtpd_tls_key_file = /etc/certificates/osx-106.example.com.E2FA6EFB8203E2E09C605D30A179669E4B4F69EB.key.pem smtpd_use_pw_server = yes smtpd_use_tls = yes unknown_local_recipient_reject_code = 550 virtual_alias_maps = virtual_gid_maps = static:5000 virtual_mailbox_base = /etc/postfix/datastore virtual_mailbox_domains = osx.example.com virtual_mailbox_maps = hash:/etc/postfix/datausers virtual_minimum_uid = 100 virtual_uid_maps = static:5000 # dovecotd -n # 1.1.17apple0.5: /private/etc/dovecot/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 456). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: Darwin 10.2.0 i386 hfs base_dir: /var/run/dovecot syslog_facility: local6 protocols: pop3s imaps ssl_cert_file: /etc/certificates/osx-106.example.com.E2FA6EFB8203E2E09C605D30A179669E4B4F69EB.cert.pem ssl_key_file: /etc/certificates/osx-106.example.com.E2FA6EFB8203E2E09C605D30A179669E4B4F69EB.key.pem ssl_cipher_list: ALL:!LOW:!SSLv2:!aNULL:!ADH:!eNULL disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap):
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
On Wed, 2009-12-09 at 11:13 -0800, Richard Stockton wrote: I assume you meant to have me change it to: password_query = .., '/mail/' || home as userdb_home, .. since there is no mail field in my DB table. Although this should work too with: mail_location = maildir:~/ That's actually better than what I was first thinking about anyway. This does not appear to work in Dovecot 1.1.19. If it doesn't work with the above mail_location, what exactly fails then? auth_debug=yes and mail_debug=yes logs could be helpful. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Want to simplify [Was:Re: How do i translate the old default_mail_env setting?]
On Wed, Dec 09, 2009 at 02:08:34PM -0500, Timo Sirainen wrote: On Wed, 2009-12-09 at 10:39 -0800, Gary Kline wrote: Your SMTP server might be authenticating using the SASL service. .. Let me rephrase my previous post: I had installed the cyrus-sasl2 port. Can I safely remove this now and reply on the builtin dovecot SASL? You said you built Sendmail with SASL support. Sendmail doesn't support Dovecot SASL. So you need to keep using Cyrus SASL. Thanks much. I thought this might be the case; and, looking over my friend's write-up, I see that he links cyrus into things-sendmail. ---I've used sendmail for too long to give it up now. But a final question: do you ever think that dovecot might integrate sendmail?? -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php
Re: [Dovecot] Developer Documentation
On Tue, 2009-12-08 at 21:42 -0200, Alex Baule wrote: I want to include lines from another file into every email when the user request to read this email. Why do you want this? Why not add the extra contents on the SMTP server side when the mail is being delivered? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Want to simplify [Was:Re: How do i translate the old default_mail_env setting?]
On Wed, 2009-12-09 at 11:26 -0800, Gary Kline wrote: Thanks much. I thought this might be the case; and, looking over my friend's write-up, I see that he links cyrus into things-sendmail. ---I've used sendmail for too long to give it up now. But a final question: do you ever think that dovecot might integrate sendmail?? I've no idea. Sendmail people are free to add Dovecot support if they want to, but I've no interest in doing that work. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] different views of a imap account
On Wed, 2009-12-02 at 15:21 -0800, Ajaxster wrote:
I have some smart phones that support imap mail servers, but when I set
them up to connect to my server, the client seems to have to sync up data
on all the mailboxes (lots of headers to download). All I really want on
my remote (phone based) imap clients is to view my inbox.
Use a symlink to your inbox, for example if your normal maildir is in
~/Maildir/ create:
mkdir ~/Maildir/mobile
ln -s .. ~/Maildir/mobile/.INBOX
Then make the Maildir/mobile/ accessible. If your IMAP client supports
configurable namespace prefix, you could create another namespace:
namespace private {
prefix = mobile.
location = maildir:~/Maildir/mobile
list = no
hidden = yes
}
Or alternatively create another user account that only sees the INBOX.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
At 11:21 AM 12/9/2009, Timo Sirainen wrote: On Wed, 2009-12-09 at 11:13 -0800, Richard Stockton wrote: password_query = .., '/mail/' || home as userdb_mail, .. Then the mail_location in dovecot.conf will be completely ignored. I assume you meant to have me change it to: password_query = .., '/mail/' || home as userdb_home, .. since there is no mail field in my DB table. No, I meant userdb_mail. The mail field isn't about having such field in database, but about presenting the mail field to Dovecot. Or actually I messed it up anyway, I meant: password_query = .., 'maildir:/mail/' || home as userdb_mail, .. Sorry, that doesn't work either. I get an imap protocol error in squirrelmail. I see your other mail suggesting mail_location = maildir:~/, but I don't understand that one either. Doesn't the tilde refer to a local user on the server? We have no local users, just users in the DB, so how would maildir:~/ work? I hesitate to turn on debugging because these servers are in heavy use. Sorry to be a pain. - Richard
Re: [Dovecot] mailboxcasecmp()
On Wed, 2009-12-02 at 02:19 -0800, Frank Cusack wrote: I remember way back, i'd modified the dspam training plugin to compare mailbox names case-insensitively. that patch wasn't accepted. i didn't understand why since it was obviously correct and had no negative impact, at least i didn't think so. I guess I didn't like that it was ascii-only. Nowadays Dovecot supports i;unicode-casemap to do Unicode case insensitive checks. That could be used.. But that could be done internally by dspam too. I'm not sure if there's much point in adding mailboxcasecmp() that does exactly the same as unicode_casecmp() (although a simple version of that doesn't exist yet either). Now I've hit another case where case-insensitive mailbox names would be useful: +addressing. If I have a mailbox 'Ext' and I send mail to frank+Ext@, the LHS is lowercased to 'frank+ext' and the +extension delivery doesn't find the 'Ext' mailbox. If the +extension is going to be lowercased, then the mailbox names should be lowercased when looking for them. Or, since 'ext' and 'Ext' can co-exist, the +extension shouldn't be lowercased when looking for the mailbox. Well.. I suppose the logic could be like: 1) Try opening the mailbox. If it exists, great, use it. 2) If it doesn't exist, try to find the mailbox case-insensitively. There may be multiple levels, like user+work/foo/st...@domain.org so it would have to match all work, foo and stuff case-insensitively separately. Mailbox listing also makes it slower, but if this isn't done often it's probably not such a big deal. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
On Wed, 2009-12-09 at 11:38 -0800, Richard Stockton wrote: password_query = .., 'maildir:/mail/' || home as userdb_mail, .. Sorry, that doesn't work either. I get an imap protocol error in squirrelmail. And what did Dovecot's logs say? http://wiki.dovecot.org/Logging I see your other mail suggesting mail_location = maildir:~/, but I don't understand that one either. Doesn't the tilde refer to a local user on the server? No. It refers to home returned by userdb lookup. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] irregular problem on outlook + imap
On Tue, 2009-12-01 at 16:19 +0100, Michele Petrazzo - Unipex wrote:
* LSUB () . folder.with.dots and spaces and numbers
This means it's in the subscriptions file.
lylu APPEND folder.with.dots and spaces and numbers (\Seen)
30-Nov-2009 10:34:00 +0100 {280844}
lylu NO [TRYCREATE] Mailbox doesn't exist: folder.with.dots and spaces
and numbers
This means it doesn't really exist, even though it's subscribed.
On the maildir home (maildir:~/mail/), it's present the folder.with.dots
and spaces and numbers and the same into the subscriptions file
Are you sure it's really in the ~/mail/ directory exactly the same? You
could try also talking IMAP directly:
telnet localhost 143
a login user pass
b list folder.with.dots*
Is it listed?
Anyway it should work fine:
a create folder.with.dots and spaces and num1234
a OK Create completed.
b append folder.with.dots and spaces and num1234 {10}
+ OK
From: foo
b OK Append completed.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] dovecot v 1.28 and virtual folders
On Sat, 2009-11-28 at 22:25 -0200, Jim Richard wrote:
now, when I try to add a virtual namespace
namespace private {
subscriptions = yes
Doesn't matter much, but I'd prefer subscriptions=no so that all
subscriptions are in a single file in ~/Maildir/subscriptions.
~/Maildir/virtual does exist in the filesystem, I can subscribe to
virtual but if I try to create a sub folder of it I get
ERROR: Could not complete request.
Query: CREATE virtual.test
Reason Given: [CANNOT] Can't create virtual mailboxes
You can't create virtual folders via IMAP client. You need to configure
them manually by creating the directories and dovecot-virtual files.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] Lazyexpunge and Segmentation fault
On Mon, 2009-11-30 at 19:52 +0100, mail...@securitylabs.it wrote: strace is almost useless for figuring out why program crashes. Could you get gdb backtrace? See http://dovecot.org/bugreport.html Hello, Timo here gdb backtrace: You still happen to have the core file? I'd like to know a few more things: #0 lazy_expunge_mail_expunge (_mail=0x9907ae8) at lazy-expunge-plugin.c:116 116 lt-expunge_box = p *lt p *deststorage p *_mail p *_mail.box Anyway there's something weird going on there. It shouldn't crash on that line. So either gcc optimizations confused gdb and it's actually crashing elsewhere (recompiling+reinstalling the plugin without -O2 parameter would help with this), or there is some memory corruption which is probably going to be tricky to find without valgrind. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] FTBFS with binutils-gold
On Fri, 2009-11-27 at 14:10 +0100, Marco Nenciarini wrote: As reported in debian bug #554306 [1] dovecot fails to build with GNU binutils-gold or setting LDFLAGS=-Wl,--no-add-needed http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554306 The problem is that liblber isn't explicitly declared as a dependence when dovecot is compiled with ldap support. The attached patch fixes this little error. Thanks, applied to v1.2 and v2.0. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] LDA: handling non-existent mail dirs
On Thu, 2009-11-26 at 20:25 +0100, Edgar Fuß wrote: We have users existing in LDAP but not supposed to receive mail. We used to handle that (somewhat ungracefully) by simply not creating the top mail directory for those accounts. Since switching to Dovecots LDA, these non-existing dirs are considered temporary failures and so the junk mails pile up in postfix' queue Would it be possible for deliver to optionally treat this as a permanent error? You can patch the code, but I think adding an extra option just for that won't benefit much more other people than you.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] irregular problem on outlook + imap
On Wed, Dec 09, 2009 at 02:52:00PM -0500, Timo Sirainen wrote:
On Tue, 2009-12-01 at 16:19 +0100, Michele Petrazzo - Unipex wrote:
* LSUB () . folder.with.dots and spaces and numbers
Hi Folks,
This may relate to one of the few problems I see with dovecot.
This had nothing to do with outlook; rather mutt or kmail.
A couple years ago, sendmail delivered my mail to
~/Mail/user and I could cd to ~/Mail and grep and find the
string(s) sought.
Dovecot seems to save its mail on my mailserver as
~/Mailbox/dotuser/*. What do I change in the conf file to
get rid of the directory DOT prefixes?
If there is any documentation on this, please point me at it?
tia.
This means it's in the subscriptions file.
lylu APPEND folder.with.dots and spaces and numbers (\Seen)
30-Nov-2009 10:34:00 +0100 {280844}
lylu NO [TRYCREATE] Mailbox doesn't exist: folder.with.dots and spaces
and numbers
This means it doesn't really exist, even though it's subscribed.
On the maildir home (maildir:~/mail/), it's present the folder.with.dots
and spaces and numbers and the same into the subscriptions file
Are you sure it's really in the ~/mail/ directory exactly the same? You
could try also talking IMAP directly:
telnet localhost 143
a login user pass
b list folder.with.dots*
Is it listed?
Anyway it should work fine:
a create folder.with.dots and spaces and num1234
a OK Create completed.
b append folder.with.dots and spaces and num1234 {10}
+ OK
From: foo
b OK Append completed.
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
http://jottings.thought.org http://transfinite.thought.org
The 7.31a release of Jottings: http://jottings.thought.org/index.php
Re: [Dovecot] SASL plain authentication failed; unable to lookup user record
On Wed, Dec 09, 2009 at 11:21:56AM -0800, JP wrote: i'll guess the solution to my problem will be something simple and obvious, I think so. [snip] config stuff: # postconf -n mail_owner = _postfix That strange non-default setting might be one of the problems. queue_directory = /private/var/spool/postfix That's equally strange and also a likely part of the problem. smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject This is not suitable for mail exchange, and not needed anyway. This says you reject anything which has not authenticated or is not in mynetworrks. smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname These are good restrictions to use, but they will block some MUA submission. They belong __ | below v smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination check_policy_service unix:private/policy reject in here after the two permit_* restrictions. smtpd_pw_server_security_options = plain, login cram-md5 smtpd_use_pw_server = yes postconf: warning: smtpd_pw_server_security_options: unknown parameter postconf: warning: smtpd_use_pw_server: unknown parameter This is patched. Talk to Apple for support. The patching could be a part of the problem as well. smtpd_sasl_path = private/auth This pathname, as documented, is relative to $queue_directory. See above for your strange non-default setting. virtual_mailbox_base = /etc/postfix/datastore This is really bizarre. Sure, files can go anywhere you want, but is there anything wrong with traditional Unix standards? I'm reminded of the famous quote: Those who don't understand Unix are doomed to reinvent it, poorly. # dovecotd -n # 1.1.17apple0.5: /private/etc/dovecot/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 456). Either grow the limit or change login_max_processes_count and max_mail_processes settings Hmmm, that sounds like something you might want to consider. auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: username_format=%n /etc/postfix/datastore/%d-passwd userdb: driver: passwd-file args: username_format=%n /etc/postfix/datastore/%d-passwd socket: type: listen client: path: /var/spool/postfix/private/auth I see a problem in that path! mode: 432 user: postfix group: postfix I see a problem in that user (and maybe group)! it would seem that something's not right between postfix and dovecot. Perhaps Dovecot should create a socket in the place Postfix needs it, with ownership such that Postfix can use it. -- Offlist mail to this address is discarded unless /dev/rob0 or not-spam is in Subject: header
Re: [Dovecot] irregular problem on outlook + imap
On Wed, 2009-12-09 at 12:16 -0800, Gary Kline wrote: A couple years ago, sendmail delivered my mail to ~/Mail/user and I could cd to ~/Mail and grep and find the string(s) sought. Dovecot seems to save its mail on my mailserver as ~/Mailbox/dotuser/*. What do I change in the conf file to get rid of the directory DOT prefixes? What do you mean by user? You mean different mailboxes? If there is any documentation on this, please point me at it? Apparently you want LAYOUT=fs, not Maildir++. http://wiki.dovecot.org/MailLocation/Maildir#Directory_layout signature.asc Description: This is a digitally signed message part
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
At 11:45 AM 12/9/2009, Timo Sirainen wrote: On Wed, 2009-12-09 at 11:38 -0800, Richard Stockton wrote: password_query = .., 'maildir:/mail/' || home as userdb_mail, .. Sorry, that doesn't work either. I get an imap protocol error in squirrelmail. And what did Dovecot's logs say? http://wiki.dovecot.org/Logging mail_location: Ambiguous mail location setting, don't know what to do with it: 0 (try prefixing it with mbox: or maildir:) and then IMAP(my_name): Namespace initialization failed I believe these errors were from my first attempt, when I just had '/mail/' || home as userdb_home. When I added the 'maildir:/mail/' || home as userdb_mail, I didn't see any errors in the dovecot-info.log, just the imap protocol error in squirrelmail. I see your other mail suggesting mail_location = maildir:~/, but I don't understand that one either. Doesn't the tilde refer to a local user on the server? No. It refers to home returned by userdb lookup. Hmmm, okay I see how that is supposed to work. Unfortunately I had a couple of client complaints with my previous one minute (or so) tests, so I won't be able to do anything more with this until later today, or perhaps tomorrow. Thanks for your help so far, I'll keep beating on it. ;-) - Richard
Re: [Dovecot] PostgreSQL connection bug
On Sun, 2009-11-29 at 06:00 +, Daniel Howard wrote: In these cases, Dovecot would still fall back to PAM authentication, and the user would log in, but the postgres connection would remain stuck. Gradually the number of connections would increase until postgres failed. This sounds weird. You mean if password_query doesn't return any results Dovecot somehow completely hangs/leaks a PostgreSQL connection and creates a new one? Did it log any errors? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
On Wed, 2009-12-09 at 12:22 -0800, Richard Stockton wrote:
At 11:45 AM 12/9/2009, Timo Sirainen wrote:
On Wed, 2009-12-09 at 11:38 -0800, Richard Stockton wrote:
password_query = .., 'maildir:/mail/' || home as userdb_mail, ..
Sorry, that doesn't work either. I get an imap protocol error in
squirrelmail.
And what did Dovecot's logs say? http://wiki.dovecot.org/Logging
mail_location: Ambiguous mail location setting, don't know what to
do with it: 0 (try prefixing it with mbox: or maildir:)
Oh. || wasn't concat operator in MySQL after all. I just recently tested
that it didn't give an error so I assumed it was concat, not logical
or. :)
I believe these errors were from my first attempt, when I just had
'/mail/' || home as userdb_home.
You should have used instead: concat('mail', home) as userdb_home
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] postfix+sasl+dovecot script help!
On Thu, 2009-11-26 at 01:49 -0800, Tudod Ki wrote: 1.) But: when I want to get the e-mails through imap, with Thunderbird, on another machine, it just waits, and waits, and waits...[and finally it gives this: Connection to server debian.lan timed out.] :\ The port is firewalled? 2.) When I want to send a message from a testuser to a testuser, with Thunderbird, on the client, it just keeps asking for the password, when I want click send. :S Enable auth_debug=yes in Dovecot and it should log why authentication fails. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Problem using LDAP generating Userhome
On Tue, 2009-11-24 at 15:03 +0100, Thorsten Habich wrote:
Hi there,
I'm trying to let dovecot generate the userhome directory dynamicly via
user_attr.
If uid is returned from LDAP before mail everything is fine, but if
mail is delivered
before uid the localpart of the mailaddress is used in home path.
e.g.:
Mail: testu...@domain.de
UID : test123
sometimes home is /mail/store/testuser and sometimes /mail/store/test123
depending
on the order the ldap server replies.
I don't think there's a good way to solve this currently.
pass_attrs =
uid=user,userPassword=password,mailMessageStore=home=%$/telefonica.de/%Ln,mailFilterStore=sieve_dir=%$/telefonica.de/%Ln
Do mailMessageStore and mailFilterStore return different directories? If
not, maybe you could just put those settings into plugin {} section.
Then the %Ln is guaranteed to be what you want.
signature.asc
Description: This is a digitally signed message part
[Dovecot] Adding capacity by simply migrating to dovecot -- thank you
We run a mail service with some hundreds of domains and thousands of users. Xeon 2 CPU server hosting the imap, pop, webmail, db and all trimmings (sepparate servers scanning for spam/viri) The server was io saturated and performing poorly, especially for large webmail users. A constant queue of hundreds of ops per second were taking too many miliseconds each (gstat.) Load average often spiked over 15! We planned to add a second backend imap/pop machine but first migrated to dovecot (from courier.) Like a miracle, the load average stays below 1 now, nor do the disks saturate! All's well and webmail performs snappily even during peak usage! Granted we also upgraded freebsd which supposedly has made leaps to better schedule tasks across multiple processors, but this is not a many core machine - just 2. We almost don't need to scale up our architecture, tho will, thanks so very much for this wonderful software Timo!
Re: [Dovecot] irregular problem on outlook + imap
On Wed, Dec 09, 2009 at 03:21:54PM -0500, Timo Sirainen wrote: On Wed, 2009-12-09 at 12:16 -0800, Gary Kline wrote: A couple years ago, sendmail delivered my mail to ~/Mail/user and I could cd to ~/Mail and grep and find the string(s) sought. Dovecot seems to save its mail on my mailserver as ~/Mailbox/dotuser/*. What do I change in the conf file to get rid of the directory DOT prefixes? What do you mean by user? You mean different mailboxes? That depends upon the definition of mailbox. Mail to me from, say, smith was stored as ~/Mail/smith; mail from jones was stored as ~/Mail/jones. In early '08, using dovecot, that became ~Maildir/.smith/* and ~/Maildir/.jones/*. It would be nice to get rid of the leading dot. If there is any documentation on this, please point me at it? Apparently you want LAYOUT=fs, not Maildir++. Hm, I have no clue; I'm too new right now. http://wiki.dovecot.org/MailLocation/Maildir#Directory_layout thanks much; i'll check this page. -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php
Re: [Dovecot] fts squat non-english search for 2 words
On Thu, 2009-11-26 at 00:00 +0700, vus...@test123.ru wrote: Timo Sirainen t...@iki.fi: On Sun, 2009-11-22 at 20:35 +0700, vus...@test123.ru wrote: Timo, thank you for answer. Meanwhile I was trying to setup horde+dovecot+search. Next step was dovecot 1.2.4 + solr 1.4. It works! Now it can find 2 non-latin words. 1) I cannot search by substrings - neither plane nor plane* does find planet Try if attached patch helps? Quick answer is no 8)). Now the story. I debugged and realized that patched plugin generates - for search xxx yyy: q=body:XXX YYY* With the patch I was trying to make it do: q=body:XXX\ YYY* And actually looks like I wasn't adding \ before the space at all. And I'm not even sure if you could have escaped space like that.. It should be: q=body:XXX* +body:YYY* That would be different. Doing SEARCH TEXT XXX TEXT YYY should produce that, but SEARCH TEXT XXX YYY should produce what I mentioned above. (not q=body:XXX* +body:YYY* - quotation does matter) I know, that's why I thought my patch removed the quotes.. But this does not work as expected. Prefix searches (with asterisk) are case-sensitive. I googled around and found this post - http://michaelkimsal.com/blog/solr-case-sensitivty/comment-page-1/#comment-78198 . It is old - 2007, but it looks SOLR is still case-sensitive for *. Because of dovecot capitalizes query (and this is right, I think), the search will never find a thing. Doesn't Dovecot also capitalize all the text that goes into Solr? If not, perhaps it should and that would be the solution. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Adding capacity by simply migrating to dovecot -- thank you
On Wed, 2009-12-09 at 12:43 -0800, Benjamin Connelly wrote: Like a miracle, the load average stays below 1 now, nor do the disks saturate! All's well and webmail performs snappily even during peak usage! If you still want to reduce disk IO, you can also try (if you haven't already): - deliver: http://wiki.dovecot.org/LDA/Indexing - maildir_very_dirty_syncs=yes: http://wiki.dovecot.org/MailLocation/Maildir signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Want to simplify [Was:Re: How do i translate the old default_mail_env setting?]
On Wed, Dec 09, 2009 at 02:28:19PM -0500, Timo Sirainen wrote: On Wed, 2009-12-09 at 11:26 -0800, Gary Kline wrote: Thanks much. I thought this might be the case; and, looking over my friend's write-up, I see that he links cyrus into things-sendmail. ---I've used sendmail for too long to give it up now. But a final question: do you ever think that dovecot might integrate sendmail?? I've no idea. Sendmail people are free to add Dovecot support if they want to, but I've no interest in doing that work. All right, then it's an MTA-side issue. Maybe I'll hack in the Dovecot support then. Dovecot is just waaay to outstanding to be unsupported. -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
At 12:28 PM 12/9/2009, Timo Sirainen wrote:
Oh. || wasn't concat operator in MySQL after all. I just recently tested
that it didn't give an error so I assumed it was concat, not logical
or. :)
I believe these errors were from my first attempt, when I just had
'/mail/' || home as userdb_home.
You should have used instead: concat('mail', home) as userdb_home
I just tried: concat('mail/', home) as userdb_home
after setting mail_location = maildir:~/:INDEX=MEMORY
Squirrelmail reports: ERROR: Connection dropped by IMAP server.
Query: CAPABILITY
dovecot-info.log reports nothing.
home is defined in the DB as r/l/rls/Maildir/. The DB is MySQL 5.0.26.
OS is Red Hat Enterprise Linux Server release 5.4 (Tikanga)
If I try: concat('maildir:/mail/', home) as userdb_mail
(leaving the old config mail_location = maildir:/mail/:INDEX=MEMORY)
I get the same squirrelmail error and this in dovecot-info.log
Dec 9 12:49:13 webmail02 dovecot: Fatal: Mailbox indexes in
/mail/r/l/rls/Maildir/ are in NFS mount. You must set
mail_nfs_index=yes (and mail_nfs_storage=yes) to avoid index
corruptions. If you're sure this check was wrong, set nfs_check=no.
which I assume is due to there being no INDEX=MEMORY anywhere.
I am really starting to push my luck testing this with our clients
trying to use webmail at the same time. But I'm still open to other
ideas, I just may have to wait a bit before trying them.
Thanks.
- Richard
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
On Wed, 2009-12-09 at 13:05 -0800, Richard Stockton wrote:
At 12:28 PM 12/9/2009, Timo Sirainen wrote:
Oh. || wasn't concat operator in MySQL after all. I just recently tested
that it didn't give an error so I assumed it was concat, not logical
or. :)
I believe these errors were from my first attempt, when I just had
'/mail/' || home as userdb_home.
You should have used instead: concat('mail', home) as userdb_home
I just tried: concat('mail/', home) as userdb_home
Was it really 'mail/', not '/mail/'? I forgot those / characters above..
If I try: concat('maildir:/mail/', home) as userdb_mail
(leaving the old config mail_location = maildir:/mail/:INDEX=MEMORY)
I get the same squirrelmail error and this in dovecot-info.log
Dec 9 12:49:13 webmail02 dovecot: Fatal: Mailbox indexes in
/mail/r/l/rls/Maildir/ are in NFS mount. You must set
mail_nfs_index=yes (and mail_nfs_storage=yes) to avoid index
corruptions. If you're sure this check was wrong, set nfs_check=no.
which I assume is due to there being no INDEX=MEMORY anywhere.
Right, you should have added that to the concat() also. The point of
userdb_mail is that it completely overrides mail_location setting's
value.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] v2.0.alpha3 released
On Tue, 2009-11-24 at 06:44 +0100, Luigi Rosa wrote: It's the intended behavior. Dunno if it's the best. Copying example config directly to /etc/dovecot/ doesn't seem such a good idea. It would be nice to put a text file like configuration files go here or something like that, or just no action at all. Or maybe a message at the end of make install procedure. Maybe it's me, but if I find an empty directory in /etc after an installation, the first think I think is that something went wrong. How about it installs README file containing: Configuration files go to this directory. See example configuration files in /usr/local/share/doc/dovecot/example-config/ signature.asc Description: This is a digitally signed message part
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
At 01:10 PM 12/9/2009, Timo Sirainen wrote:
On Wed, 2009-12-09 at 13:05 -0800, Richard Stockton wrote:
I just tried: concat('mail/', home) as userdb_home
Was it really 'mail/', not '/mail/'? I forgot those / characters above..
Yes, I figured the maildir:~/ was putting in the first /.
If I try: concat('maildir:/mail/', home) as userdb_mail
(leaving the old config mail_location = maildir:/mail/:INDEX=MEMORY)
I get the same squirrelmail error and this in dovecot-info.log
Dec 9 12:49:13 webmail02 dovecot: Fatal: Mailbox indexes in
/mail/r/l/rls/Maildir/ are in NFS mount. You must set
mail_nfs_index=yes (and mail_nfs_storage=yes) to avoid index
corruptions. If you're sure this check was wrong, set nfs_check=no.
which I assume is due to there being no INDEX=MEMORY anywhere.
Right, you should have added that to the concat() also. The point of
userdb_mail is that it completely overrides mail_location setting's
value.
Hey! I think I got it!
concat('maildir:/mail/', home, ':INDEX=MEMORY') as userdb_mail,
seems to do the trick, and should be compatible with 1.2.x, right?
Next step, update to 1.2... Anything else I should be watching out for?
Thanks for sticking with me through all this, I really appreciate it.
- Richard
Re: [Dovecot] After upgrading to 1.2 - absolute path questions
On Wed, 2009-12-09 at 13:23 -0800, Richard Stockton wrote:
At 01:10 PM 12/9/2009, Timo Sirainen wrote:
On Wed, 2009-12-09 at 13:05 -0800, Richard Stockton wrote:
I just tried: concat('mail/', home) as userdb_home
Was it really 'mail/', not '/mail/'? I forgot those / characters above..
Yes, I figured the maildir:~/ was putting in the first /.
No, that simply converted it to:
maildir:mail/.../
Next step, update to 1.2... Anything else I should be watching out for?
Hopefully not.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] SASL plain authentication failed; unable to lookup user record
/dev/rob0 wrote: On Wed, Dec 09, 2009 at 11:21:56AM -0800, JP wrote: i'll guess the solution to my problem will be something simple and obvious, I think so. and yet you haven't really provided any assistance for the problem at hand except some condescending answers for unrelated things and 'look elsewhere'. surprised you didn't tell me to use qmail. [snip] config stuff: # postconf -n mail_owner = _postfix That strange non-default setting might be one of the problems. it's not strange. it's the os x uid/gid scheme. the purpose of the configuration files is to allow folks to configure things to meet their needs. the socket is readable and writable by both _postfix(postfix) and dovecot so i don't understand how that would cause the problem. queue_directory = /private/var/spool/postfix That's equally strange and also a likely part of the problem. that's not strange either. /var is a symlink to /private/var; i have tried setting postfix:smtpd_sasl_path and the dovecot socket path to the full path of /private/var/spool/postfix, and then to /var/spool/postfix and both resulted in the same behaviour. smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated reject This is not suitable for mail exchange, and not needed anyway. This says you reject anything which has not authenticated or is not in mynetworrks. but it's okay for testing and has no effect on sasl authentication. smtpd_helo_restrictions = reject_invalid_helo_hostname reject_non_fqdn_helo_hostname These are good restrictions to use, but they will block some MUA submission. They belong __ | below v smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks reject_unauth_destination check_policy_service unix:private/policy reject in here after the two permit_* restrictions. smtpd_pw_server_security_options = plain, login cram-md5 smtpd_use_pw_server = yes postconf: warning: smtpd_pw_server_security_options: unknown parameter postconf: warning: smtpd_use_pw_server: unknown parameter sorry, these were left in by mistake. This is patched. Talk to Apple for support. The patching could be a part of the problem as well. yes i imagine it is patched by apple. i don't have an apple support contract which is why is was posting to the list. smtpd_sasl_path = private/auth This pathname, as documented, is relative to $queue_directory. See above for your strange non-default setting. it strikes me as odd that you keep calling the non-default settings 'strange' and 'bizarre'. if everyone in the universe should use the default settings then what's the point of the config files? i'm just sayin. any color i want as long as it's black? virtual_mailbox_base = /etc/postfix/datastore This is really bizarre. Sure, files can go anywhere you want, but is there anything wrong with traditional Unix standards? I'm reminded of the famous quote: Those who don't understand Unix are doomed to reinvent it, poorly. i understand unix. this is my first foray into postfix and dovecot. the setting is not bizarre. i'm moving all my virtual mail files onto a separate drive, which just happens to be on that pariticular mount point. for testing. and contrary to what you seem to be attempting to get me to believe, just because i'm not doing it your way does not make it strange or bizarre. # dovecotd -n # 1.1.17apple0.5: /private/etc/dovecot/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 456). Either grow the limit or change login_max_processes_count and max_mail_processes settings Hmmm, that sounds like something you might want to consider. auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: username_format=%n /etc/postfix/datastore/%d-passwd userdb: driver: passwd-file args: username_format=%n /etc/postfix/datastore/%d-passwd socket: type: listen client: path: /var/spool/postfix/private/auth I see a problem in that path! see above about the symlinks. mode: 432 user: postfix group: postfix I see a problem in that user (and maybe group)! see above re: _postfix and postfix. it would seem that something's not right between postfix and dovecot. Perhaps Dovecot should create a socket in the place Postfix needs it, with ownership such that Postfix can use it. thanks for the vague help and the condescending answers. at least you didn't insult my mom. gotta wonder if this is one of the reasons people don't like open source software.
Re: [Dovecot] SASL plain authentication failed; unable to lookup user record
On Wed, 2009-12-09 at 11:21 -0800, JP wrote: dovecot debug:yes and dovecot debug_passwords:yes and i do see debug info in the logs when i authenticate via pop3. but i don't see any debug info in the logs when doing smtp auth. i don't know if that's another symptom, or if dovecot just does not debug smtp auth connections to begin with. If Dovecot logs nothing, it means nothing tried to authenticate to Dovecot. Do you also mean Postfix doesn't log anything? I don't really know what things it logs or doesn't. I'd guess it would log errors about not being able to connect to auth socket, so maybe the problem is some setting that makes Postfix not even attempt an actual authentication. signature.asc Description: This is a digitally signed message part
[Dovecot] Cannot read mdir inbox.
Problem: Dovecot is totally and merrily oblivious to maildir INBOX installed in the usual /var/spool/mail/%u Software/system: Dovecot 1.2.8 running under Fedora 12 with 1.9 gig RAM + AMD Athlon LE-1640 CPU on a ASUS M3A78-EM motherboard (uname -a = Linux 2.6.31.6-162.fc12.x86_64 #1 SMP Fri Dec 4 00:06:26 EST 2009 x86_64 x86_64 x86_64 GNU/Linux ) Dovecot has been installed from the Fedora repositories, not recompiled from scratch. System has only one hard disk and is on one ext4 LVM partition. My configurations are http://emdx.org/Dovecot/dovecot.confA.txt for dovecot -a http://emdx.org/Dovecot/dovecot.confN.txt for dovecot -n The mail is properly delivered by Exim in the proper place. Using a client (Thunderbird 3), if I copy some messages in the INBOX, they stay there, but they are nowhere to be found in the /var/spool/mail/%u directory. User mail is in ~/Maildir. I tried to make a symlink pointing to /var/spool/mail/%u and, of course, it does not work. I also tried giving chmod 666 to all files in /var/spool/mail/%u (and chmod 777 for the directories), this makes no difference. Otherwise, Dovecot works flawlessly and without no problems whatsoever in ~/Maildir. I can transfer huge volumes of email from the future old server and everything is rock solid. I just can’t get the INBOX. I would rather not fiddle with Exim and have it deliver the mail into ~/Maildir Google has been stellarly inefficient in helping me find solutions.
[Dovecot] Mail.app + dovecot 1.2 + POP3
Hello all, I have an user with MacOS X 10.5 Mail.app 3.5, which is connecting using POP3 to a dovecot 1.2 server. He has a 512 kbps link, which he saturates downloading large files. While the bandwidth is saturated, Mail.app shows the POP3 account as offline (I haven't used that client, but it seems that it doesn't retry the connection if it fails at some moment). He argues that he has some other POP3 and IMAP4 accounts configured in the same app, and those accounts never go offline even if the bw usage is at 100% (those other accounts are not on my servers and I don't know which sw are they using). My question is, could dovecot be somehow involved in this offline issue? (something like the past IDLE issues with Outlook 2007?) Thanks in advanced.
Re: [Dovecot] Cannot read mdir inbox.
On Wed, 2009-12-09 at 17:04 -0500, Marc Dufour wrote: Dovecot is totally and merrily oblivious to maildir INBOX installed in the usual /var/spool/mail/%u .. User mail is in ~/Maildir. So you want INBOX to be in mbox format in /var/spool/mail/%u, and everything else in Maildir format in ~/Maildir? I would rather not fiddle with Exim and have it deliver the mail into ~/Maildir That would be the best long term solution, but .. : http://wiki.dovecot.org/Namespaces#Mixed_mbox_and_Maildir signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Cannot read mdir inbox.
Timo Sirainen wrote: On Wed, 2009-12-09 at 17:04 -0500, Marc Dufour wrote: Dovecot is totally and merrily oblivious to maildir INBOX installed in the usual /var/spool/mail/%u .. User mail is in ~/Maildir. So you want INBOX to be in mbox format in /var/spool/mail/%u, and everything else in Maildir format in ~/Maildir? Not at all. I want 100% pure, natural maildir. Exim already delivers fine in maildir.
Re: [Dovecot] Mail.app + dovecot 1.2 + POP3
On Wed, 2009-12-09 at 16:10 -0600, Rodolfo Gonzalez Gonzalez wrote: He argues that he has some other POP3 and IMAP4 accounts configured in the same app, and those accounts never go offline even if the bw usage is at 100% (those other accounts are not on my servers and I don't know which sw are they using). My question is, could dovecot be somehow involved in this offline issue? (something like the past IDLE issues with Outlook 2007?) So the problem is higher latency I suppose? Dovecot's logins fail after idling for 3 minutes. I don't think the latencies should be that high no matter what you do with your bandwidth. Of course it's possible that there's something else than Dovecot that kills high-latency connections too soon (firewall, whatever). signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Cannot read mdir inbox.
On Wed, 2009-12-09 at 17:13 -0500, Marc Dufour wrote: Timo Sirainen wrote: On Wed, 2009-12-09 at 17:04 -0500, Marc Dufour wrote: Dovecot is totally and merrily oblivious to maildir INBOX installed in the usual /var/spool/mail/%u .. User mail is in ~/Maildir. So you want INBOX to be in mbox format in /var/spool/mail/%u, and everything else in Maildir format in ~/Maildir? Not at all. I want 100% pure, natural maildir. Exim already delivers fine in maildir. So /var/spool/mail/%u/ is a maildir? If so, your settings should already work correctly. What exactly is the problem? Nothing shows up in INBOX? Does Dovecot log any errors? http://wiki.dovecot.org/Logging Also potentially helpful things: - mail_debug=yes and look at the logs - strace -p `pidof imap`, select INBOX and see what files it tries to access signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Patch: event port-based ioloop and notify
On Sat, 2009-11-14 at 21:09 +0100, Emanuele Pucciarelli wrote: I have prepared a small patch to support Solaris 10 and Opensolaris' event port mechanism for both the ioloop and the notify subsystems. It seems to work fine for me, but I haven't conducted any extensive testing. Does the configure check actually have to test that all the port_* functions work? If they exist in libc, aren't they guaranteed to work? If just their existence is enough, I'd just change the check to test to AC_CHECK_FUNC(port_associate, ..). Why do you call it fen / file event notification? It seems to be called just port in the man pages and everywhere else, so I'd call it that. Why do you silently handle EBADFs and ENOENTs? Are those actually happening in your system? Dovecot should never close fds before removing them from ioloop, other ioloops also log an error if that happens. For port_getn() error handling I'd probably do the same as all other ioloops: Ignore EINTR/ETIME and treat everything else as fatal. What's the idea behind BAD_PORTEV_USER? In general when an error that really shouldn't happen does happen I prefer to fatal/panic than trying to limp along. + io-path = i_new(char, strlen(path)+1); + strcpy(io-path, path); io-path = i_strdup(path); signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Mail.app + dovecot 1.2 + POP3
Timo Sirainen escribió: On Wed, 2009-12-09 at 16:10 -0600, Rodolfo Gonzalez Gonzalez wrote: He argues that he has some other POP3 and IMAP4 accounts configured in the same app, and those accounts never go offline even if the bw usage is at 100% (those other accounts are not on my servers and I don't know which sw are they using). My question is, could dovecot be somehow involved in this offline issue? (something like the past IDLE issues with Outlook 2007?) So the problem is higher latency I suppose? Dovecot's logins fail after idling for 3 minutes. I don't think the latencies should be that high no matter what you do with your bandwidth. Of course it's possible that there's something else than Dovecot that kills high-latency connections too soon (firewall, whatever). Thanks for the answer Timo. No, his latency is not so high, and moreover, I guess something is logged when this situation happens, right? Nothing appears in the logs... Thanks.
Re: [Dovecot] Mail.app + dovecot 1.2 + POP3
On Wed, 2009-12-09 at 17:00 -0600, Rodolfo Gonzalez Gonzalez wrote: Timo Sirainen escribió: On Wed, 2009-12-09 at 16:10 -0600, Rodolfo Gonzalez Gonzalez wrote: He argues that he has some other POP3 and IMAP4 accounts configured in the same app, and those accounts never go offline even if the bw usage is at 100% (those other accounts are not on my servers and I don't know which sw are they using). My question is, could dovecot be somehow involved in this offline issue? (something like the past IDLE issues with Outlook 2007?) So the problem is higher latency I suppose? Dovecot's logins fail after idling for 3 minutes. I don't think the latencies should be that high no matter what you do with your bandwidth. Of course it's possible that there's something else than Dovecot that kills high-latency connections too soon (firewall, whatever). Thanks for the answer Timo. No, his latency is not so high, and moreover, I guess something is logged when this situation happens, right? Nothing appears in the logs... If Dovecot doesn't log even a login attempt, then yeah, I don't see how this could have anything to do with Dovecot or probably even your side of the server/network. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Patch: event port-based ioloop and notify
Timo, thanks for the detailed review! I'm going to work on the patch and make it follow your comments. Does the configure check actually have to test that all the port_* functions work? If they exist in libc, aren't they guaranteed to work? If just their existence is enough, I'd just change the check to test to AC_CHECK_FUNC(port_associate, ..). I don't know of any configurations where they exist and don't work. I'll cut the tests, then. Why do you call it fen / file event notification? It seems to be called just port in the man pages and everywhere else, so I'd call it that. Yes, I mixed that up. The general port_* framework is the event ports framework, while the part that specifically watches for changes in files and directories is the newer file event notification API [1]. The presence of port_* is enough for the ioloop to work, but the FEN API, which introduces PORT_SOURCE_FILE in the headers, is needed for the ioloop-notify. The file event notification is only available since version 72 of Nevada, so all recent versions (since before 2008) of OpenSolaris have it, but I don't know which, if any, versions of Solaris 10 have it. I would be going to separate the two checks and take a less tortuous path to check for PORT_SOURCE_FILE (AC_CHECK_DECL, I'd say). Why do you silently handle EBADFs and ENOENTs? Are those actually happening in your system? Dovecot should never close fds before removing them from ioloop, other ioloops also log an error if that happens. I'll check that again and report back. I'm not sure if I saw an ENOENT. Does this apply to ioloop-notify as well? For port_getn() error handling I'd probably do the same as all other ioloops: Ignore EINTR/ETIME and treat everything else as fatal. What's the idea behind BAD_PORTEV_USER? Unfortunately, it's possible (at least in some versions, see [2]) that port_getn() returns EINTR before updating nget to anything useful. In this case, the code would see it set to 1 and try to process the event: it would probably crash immediately, as soon as it tries to dereference events[0].portev_user to update the refcount. It seems to be a rare race condition and I haven't witnessed it personally, but (claimed to be) entirely possible. In general when an error that really shouldn't happen does happen I prefer to fatal/panic than trying to limp along. Then I'll let EBADFD be fatal too, instead of trying to recreate the port and proceed, and I'll clean up the two switch statements. + io-path = i_new(char, strlen(path)+1); + strcpy(io-path, path); io-path = i_strdup(path); Thanks. It kind of shows that I haven't taken the time to read the library – sorry about that. I'll re-post as soon as I manage to do the clean-up. [1] http://arc.opensolaris.org/caselog/PSARC/2007/027/mail [2] http://www.mail-archive.com/networking-disc...@opensolaris.org/msg12330.html -- Emanuele
Re: [Dovecot] Patch: event port-based ioloop and notify
On Thu, 2009-12-10 at 00:28 +0100, Emanuele Pucciarelli wrote: Why do you silently handle EBADFs and ENOENTs? Are those actually happening in your system? Dovecot should never close fds before removing them from ioloop, other ioloops also log an error if that happens. I'll check that again and report back. I'm not sure if I saw an ENOENT. Does this apply to ioloop-notify as well? Yes. For port_getn() error handling I'd probably do the same as all other ioloops: Ignore EINTR/ETIME and treat everything else as fatal. What's the idea behind BAD_PORTEV_USER? Unfortunately, it's possible (at least in some versions, see [2]) that port_getn() returns EINTR before updating nget to anything useful. In this case, the code would see it set to 1 and try to process the event: it would probably crash immediately, as soon as it tries to dereference events[0].portev_user to update the refcount. It seems to be a rare race condition and I haven't witnessed it personally, but (claimed to be) entirely possible. Oh, so kind of an API design bug. But could BAD_PORTEV_USER be simply NULL? Seems safer than some random memory address that might even be valid. Oh and in notify code your loops use ret, not read_events. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Virtual mailboxes not always up to date?
Finally fixed: http://hg.dovecot.org/dovecot-1.2/rev/9cccb8617820 On Tue, 2009-11-10 at 15:21 +0800, Patrick Nagel wrote: So it seems that neither EXPUNGE nor re-SELECT seems to have any refreshing effect. Nikita Koshikov told me to Try to add :INDEX=MEMORY to location setting. After my tests above I tried that, and suddenly everything works as expected. It seems logical to have the index of a virtual folder in memory only, since it is generated dynamically anyway, and is outdated before it's even written to disk (at least without some configurable virtual search result max age parameter). So maybe the easiest solution is, to imply ':INDEX=MEMORY' when a namespace location is a virtual folder? That also makes it somewhat slower. Although if you're only searching flags, it doesn't matter much. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] SASL plain authentication failed; unable to lookup user record
JP dove...@dovecot.exjay.com I'm sorry I offended you, but I really do not understand how you found condescension in my reply. I could explain some things, but I have better things to do. Please help me ensure that I never offend you again by adding me to your ignore list or killfile. Thank you. -- Offlist mail to this address is discarded unless /dev/rob0 or not-spam is in Subject: header
Re: [Dovecot] expire_dict - Folder names with spaces
On Sat, 2009-11-14 at 19:03 +0100, mich...@euroinfissi.eu wrote: How to deal with IMAP foldernames that include spaces when setting up the expire tool for them? http://hg.dovecot.org/dovecot-1.2/rev/91c6b067f464 adds support for: expire = foo bar 5 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Bug report
On Wed, 2009-11-11 at 20:11 -0800, Bryan Seitz wrote: Nov 11 23:11:20 triton dovecot: IMAP(sam): Panic: file istream-raw-mbox.c: line 578 (istream_raw_mbox_get_body_size): assertion failed: (rstream-body_offset != (uoff_t)-1) Are you still seeing these? Wonder if these patches would at least make it log more: http://hg.dovecot.org/dovecot-1.2/rev/8d4621094e54 http://hg.dovecot.org/dovecot-1.2/rev/fe1f31b4e21e signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 2.0.alpha3: imap-login segfault in hex_to_binary
On Fri, 2009-11-13 at 22:05 -0600, Mike Abbott wrote: Looks to me like auth_client_get_cookie() returned NULL in master_send_request(). Fixed: http://hg.dovecot.org/dovecot-2.0/rev/32e77c570529 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Developer Documentation
Let me explain to you i want to split the email in header and body...my smtp server do this for me but, to read again in dovecot, i need to point the email to this two files. This division in two parts is more like a test... and if the dovecot can join again this two files in read time is good for me There is no much reason to do that ? yes... i know... but like i say, its like a test to another thinks There is a way to do this ? 2009/12/9 Timo Sirainen t...@iki.fi On Tue, 2009-12-08 at 21:42 -0200, Alex Baule wrote: I want to include lines from another file into every email when the user request to read this email. Why do you want this? Why not add the extra contents on the SMTP server side when the mail is being delivered?
Re: [Dovecot] Developer Documentation
On Wed, 2009-12-09 at 23:30 -0200, Alex Baule wrote: Let me explain to you i want to split the email in header and body...my smtp server do this for me but, to read again in dovecot, i need to point the email to this two files. This division in two parts is more like a test... and if the dovecot can join again this two files in read time is good for me So you're thinking maybe you get better performance that way, or something? I was first thinking you'd want to add some automatic signature that gets modified once in a while, that wouldn't have worked. But yeah, you could do this with Maildir in a similar way than zlib plugin works. Instead of using i_stream_create_zlib(), you'd open the other file with i_stream_create_fd() and then make i_stream_create_concat() use both of the streams. Should be pretty easy to implement based on the zlib plugin code. Also when messages get expunged, you'd also need to delete the other file yourself. You can do that the same way as quota plugin decreases quota when message gets deleted. See http://wiki.dovecot.org/Design for more information about istreams and some other Dovecot code docs. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Virtual mailboxes not always up to date?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Timo, On 2009-12-10 07:50, Timo Sirainen wrote: Finally fixed: http://hg.dovecot.org/dovecot-1.2/rev/9cccb8617820 Great news, thanks! :) - -- STAR Software (Shanghai) Co., Ltd.http://www.star-group.net/ Phone:+86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key E883A005 https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005 -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAksgZwQACgkQ7yMg/OiDoAUzcgCgjLpN3VnjPrMMC95XXjM2cnwU ka4An2fmouXb9BOTr8aLGKPwWg4jWOx7 =22OC -END PGP SIGNATURE-
Re: [Dovecot] Cannot read mdir inbox.
On 09/12/2009 17:11, Timo Sirainen wrote: That would be the best long term solution, but .. : http://wiki.dovecot.org/Namespaces#Mixed_mbox_and_Maildir Well, I tried that and it works, so this is what I have decided to use. Thanks very much for the pointer.
Re: [Dovecot] SASL plain authentication failed; unable to lookup user record
Hi On Wed, 09.12.2009 @ 11:21:56AM, JP wrote: when i attempt to use smtp auth from a mail client, postfix says SASL plain authentication failed unable to lookup user record You did not send your master.cf from postfix, am I right? AFAIK smtpd is running in a chroot. For this, your config seems to be correct. Have you already tried to set a chmod 777 on the socket? Another point is to check whether dovecot could even open the location - check the permissions of the topfolders (/var/, /var/spool, ...). Another try would be to check whether it work without a chroot? I dunno whether this helps that much... but often the mistakes are small. Regards raf signature.asc Description: Digital signature
Re: [Dovecot] Adding capacity by simply migrating to dovecot -- thank you
If you still want to reduce disk IO, you can also try (if you haven't already): - deliver: http://wiki.dovecot.org/LDA/Indexing - maildir_very_dirty_syncs=yes: http://wiki.dovecot.org/MailLocation/Maildir We did switch from maildrop (and courier authd and cyrus sasl) to just dovecot (+sieve +manage sieve, a great simplification to build and maintain) and will ponder very dirty syncs. . .
