Re: [Dovecot] Moving
On Sat, 2 Jan 2010 22:24:27 -0500 Timo Sirainen t...@iki.fi articulated: No, my visa was originally set to be max. 1 year so I have to go back. It was pretty fun and Rackspace is a great company, but Blacksburg is a bit too small town and I want to go elsewhere. (Now could be a good time to try to get me to come somewhere I've always wanted to go. :) Where exactly would that be? I worked for years in New York City, and except for the occasional terror bombing, it was a great place to work. Everything I could want was there. Then again, coming from a small town I did sort of miss just lounging in a chair on my back lawn. To each his own. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Those of you who think you know everything are very annoying to those of us who do.
Re: [Dovecot] What auth ?
Hi again Timo,
Yep. Looks like you're right.
After my post yesterday I changed something and now nothing works.
Looks like I'll have to dig a little deeper on the docs.
Thank you again,
s.
--- On Sat, 2/1/10, Timo Sirainen t...@iki.fi wrote:
From: Timo Sirainen t...@iki.fi
Subject: Re: [Dovecot] What auth ?
To: Spyros Tsiolis sts...@yahoo.co.uk
Cc: Dovecot Mailing List dovecot@dovecot.org
Date: Saturday, 2 January, 2010, 22:10
On 2.1.2010, at 13.47, Spyros Tsiolis
wrote:
Jan 02 19:14:05 auth(default): Info:
passwd-file(postmaster,127.0.0.1): lookup: user=postmaster
file=/etc/dovecot/passwd
Jan 02 19:14:05 auth(default): Info:
passwd-file(postmaster,127.0.0.1): unknown user
postmaster doesn't exist in /etc/dovecot/passwd file.
Jan 02 19:15:26 imap-login: Info: Authenticate PLAIN
failed: Unsupported authentication mechanism.: method=PLAIN,
rip=127.0.
..
AFAIK, I disabled plain auth and enabled digest-md5.
I guess you mean you set auth { mechanisms = digest-md5 }?
Yeah, that'll cause plaintext auth attempts to fail and
probably isn't what you wanted. http://wiki.dovecot.org/Authentication may be
helpful.
Re: [Dovecot] Moving
On 3.1.2010, at 6.26, Jerry wrote: (Now could be a good time to try to get me to come somewhere I've always wanted to go. :) Where exactly would that be? I worked for years in New York City, and except for the occasional terror bombing, it was a great place to work. Everything I could want was there. Then again, coming from a small town I did sort of miss just lounging in a chair on my back lawn. New York City and New Zealand would be interesting, but I don't know of any interesting companies in them. Especially ones that would be interested in paying for Dovecot development.
Re: [Dovecot] Moving
On Mon, 04 Jan 2010 00:43:07 Timo Sirainen wrote: On 3.1.2010, at 6.26, Jerry wrote: (Now could be a good time to try to get me to come somewhere I've always wanted to go. :) Where exactly would that be? I worked for years in New York City, and except for the occasional terror bombing, it was a great place to work. Everything I could want was there. Then again, coming from a small town I did sort of miss just lounging in a chair on my back lawn. New York City and New Zealand would be interesting, but I don't know of any interesting companies in them. Especially ones that would be interested in paying for Dovecot development. tut tut. It may be 12.47am on Monday morning here in New Zealand but we have ears and eyes lol :-)
Re: [Dovecot] Moving
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Sirainen said the following on 03/01/10 12:43: New York City and New Zealand would be interesting, but I don't know of any interesting companies in them. Especially ones that would be interested in paying for Dovecot development. You can check http://jobs.joelonsoftware.com/ Joel Spolsky is a software developer in NY area. Ciao, luigi - -- / +--[Luigi Rosa]-- \ The Force will be with you. Always. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAktAiQ4ACgkQ3kWu7Tfl6ZRnRACdGKk46S0U1dRPsdRP2gBqTPXT 578AmwSsjw5fPEgK8Xwx2yXpB+9r6wYH =c2xj -END PGP SIGNATURE-
Re: [Dovecot] Moving
On Sun, 3 Jan 2010 06:43:07 -0500 Timo Sirainen t...@iki.fi articulated: On 3.1.2010, at 6.26, Jerry wrote: (Now could be a good time to try to get me to come somewhere I've always wanted to go. :) Where exactly would that be? I worked for years in New York City, and except for the occasional terror bombing, it was a great place to work. Everything I could want was there. Then again, coming from a small town I did sort of miss just lounging in a chair on my back lawn. New York City and New Zealand would be interesting, but I don't know of any interesting companies in them. Especially ones that would be interested in paying for Dovecot development. Perhaps you could apply for some sort of collegiate or government grant. You would be surprised at the crap (nothing personal) that they allocate grant money for. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | Ninety percent of the politicians give the other ten percent a bad reputation. Henry Kissinger
Re: [Dovecot] Kernel warnings
* Noel Butler, 2010-01-02 12:15 On Sat, 2010-01-02 at 09:45 +0100, Thomas Zajic wrote: Dovecot versions involved were/are 1.2.x, I'm currently at 1.2.9. My system is running Slackware 13.0, but this also happened with 12.2. We run Slackware (yes currently 13.0, and with custom kernels since donkies years ago)... I have never seen this on any of the servers. Yeah, same here, going back to Slackware 3.4 or something ... oh well. Thanks anyway, Thomas
Re: [Dovecot] Kernel warnings
* Timo Sirainen, 2010-01-02 17:48 On 2.1.2010, at 3.45, Thomas Zajic wrote: [c1095367] ? inotify_free_group_priv+0x12/0x21 [c1093c81] ? fsnotify_final_destroy_group+0x16/0x1e .. There are no processes other than dovecot's imap that are ever causing these warnings. Does this indicate a problem in the kernel or rather in dovecot? Yes. Hehe ... okay, so which one is it? :-) I don't even know what exactly to make of this warning - obviously, there may be a potential memory leak related to inotify and dovecot's imap process, but is it 1. a bug in the kernel that is triggered by something that dovecot's inotify code does, or 2. a bug in dovecot's imap that the kernel notices and warns about as of 2.6.31 (but didn't notice and/or warn about in 2.6.30 and earlier)? The reason why only imap process creates these is because it's probably the only process using inotify. You could of course compile Dovecot without inotify support, but that's just a workaround.. Hmmm ... I don't mind the warning as such, as it doesn't have any actual bad side effects as far as I can tell, I'm just curious as to what causes it. Is there anything related I should/could tune in /proc/sys/fs/inotify? [r...@airframe]:~# grep -r . /proc/sys/fs/inotify /proc/sys/fs/inotify/max_user_instances:128 /proc/sys/fs/inotify/max_user_watches:65536 /proc/sys/fs/inotify/max_queued_events:16384 [r...@airframe]:~# Bye, Thomas
[Dovecot] Problems getting the antispam-plugin to work
Hi List,
i'm running the current debian lenny dovecot-version
(dpkg says it's 1.0.15-2.3+lenny1) and i'm trying to get the
antispam-plugin ('1.2+20090702-1~bpo50+3') to work.
Unfortunately dovecot always says antispam plugin not configured
moving spam into the spam-folder.
My config:
protocol imap {
mail_plugins = antispam
}
plugin {
antispam_signature = X-DSPAM-Signature
antispam_signature_missing = error
antispam_trash = Trash
antispam_spam = Spam
antispam_dspam_binary = /usr/bin/dspam
antispam_dspam_args = --deliver=;--user;%u
}
Thanks in advance
Malte Schirmacher
[Dovecot] imap default separator ignored?
Hi folks, I have configured the imap folder separator to '/' (see below). AFAIU the separator character does not affect the internal folder representation managed by Dovecot, but just the communication between client and imap server. Question is: What is supposed to happen if I try to create a folder named a.b in this configuration? Since '.' is not a separator character anymore, and since the client doesn't know anything about the internals of Dovecot, I do not see why Dovecot complains about an invalid character? Shouldn't it hide its internal Maildir structure? Regards Harri == # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.2 x86_64 Debian squeeze/sid log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s managesieve 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_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve 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_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve namespace: type: private separator: / location: maildir:~/Maildir inbox: yes list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd signature.asc Description: OpenPGP digital signature
Re: [Dovecot] imap default separator ignored?
On January 3, 2010 6:16:18 PM +0100 Harald Dunkel harald.dun...@t-online.de wrote: What is supposed to happen if I try to create a folder named a.b in this configuration? Since '.' is not a separator character anymore, and since the client doesn't know anything about the internals of Dovecot, I do not see why Dovecot complains about an invalid character? Shouldn't it hide its internal Maildir structure? You'd think so, but . is used by the Maildir++ format in the filesystem so as long as you're using Maildir++ it is illegal. You can't have a folder named a.b because when this looks like a/b in Maildir++. So, . is always illegal, and whatever your separator character is, is also illegal. You can use the folder structure (ie, maildir instead of maildir++) and then . should be legal but I personally haven't tried this. I think you just append :LAYOUT=fs to the location spec to use it. -frank
Re: [Dovecot] Problems getting the antispam-plugin to work
On 01/03/2010 04:29 PM Malte Schirmacher wrote:
Hi List,
i'm running the current debian lenny dovecot-version
(dpkg says it's 1.0.15-2.3+lenny1) and i'm trying to get the
antispam-plugin ('1.2+20090702-1~bpo50+3') to work.
Unfortunately dovecot always says antispam plugin not configured
moving spam into the spam-folder.
My config:
protocol imap {
mail_plugins = antispam
}
plugin {
antispam_signature = X-DSPAM-Signature
antispam_signature_missing = error
antispam_trash = Trash
antispam_spam = Spam
antispam_dspam_binary = /usr/bin/dspam
antispam_dspam_args = --deliver=;--user;%u
}
Result from irc://chat.freenode.net/dovecot:
The plugin in the Debian dovecot-antispam package is compiled with the
configuration option 'BACKEND=mailtrain'. In this case the plugin has to
be configured with the antispam_mail_* settings.
Regards,
Pascal
--
The trapper recommends today: decade.1000...@localdomain.org
Re: [Dovecot] Problems getting the antispam-plugin to work
Pascal Volk wrote: Result from irc://chat.freenode.net/dovecot: Oops, sorry for forgeting to write this myself.
Re: [Dovecot] imap default separator ignored?
On 3.1.2010, at 12.16, Harald Dunkel wrote: What is supposed to happen if I try to create a folder named a.b in this configuration? Since '.' is not a separator character anymore, and since the client doesn't know anything about the internals of Dovecot, I do not see why Dovecot complains about an invalid character? Shouldn't it hide its internal Maildir structure? See listescape plugin.
Re: [Dovecot] Kernel warnings
On 3.1.2010, at 9.12, Thomas Zajic wrote: Hehe ... okay, so which one is it? :-) I don't even know what exactly to make of this warning - obviously, there may be a potential memory leak related to inotify and dovecot's imap process, but is it 1. a bug in the kernel that is triggered by something that dovecot's inotify code does, or Yes. 2. a bug in dovecot's imap that the kernel notices and warns about as of 2.6.31 (but didn't notice and/or warn about in 2.6.30 and earlier)? Userspace can't (shouldn't) cause kernel errors/warnings. Even if Dovecot did something wrong, I think it would still be a kernel bug if it logged a warning about it. And this doesn't seem to be a widespread problem, so I don't think Dovecot does anything wrong. Is there anything related I should/could tune in /proc/sys/fs/inotify? Probably not. I'd ask about this in your distro or kernel mailing list.
Re: [Dovecot] pop3+leave messages on server
Timo Sirainen wrote, On 2009. 12. 29. 21:08: dovecot -n output could be helpful. Also did you look at logs? Maybe Yes, I looked logs, I didn't found an error. This is dovecot -n: # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28-15-server x86_64 Ubuntu 9.04 xfs protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /data/apps/dovecot/mail.exampledomain.hu.pem ssl_key_file: /data/apps/dovecot/mail.exampledomain.hu.pem disable_plaintext_auth: no 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_executable(managesieve): /usr/lib/dovecot/managesieve-login login_user: _dovecot verbose_proctitle: yes first_valid_uid: 1 mail_privileged_group: dovecot mail_uid: dovecot mail_gid: dovecot mail_location(default): maildir:/data/mail/%d/%n/Maildir/ mail_location(imap): maildir:/data/mail/%d/%n/Maildir/ mail_location(pop3): maildir:/data/mail/%d/%n/Maildir/ mail_location(managesieve): maildir:/data/mail/%d/%n maildir_stat_dirs: yes maildir_copy_preserve_filename: yes maildir_very_dirty_syncs: yes mbox_write_locks: fcntl dotlock mbox_dirty_syncs: no mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota deleted_to_trash mail_plugins(imap): quota imap_quota deleted_to_trash mail_plugins(pop3): mail_plugins(managesieve): 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_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_enable_last(managesieve): no pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_reuse_xuidl(managesieve): no pop3_save_uidl(default): no pop3_save_uidl(imap): no pop3_save_uidl(pop3): yes pop3_save_uidl(managesieve): no pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): lda: postmaster_address: r...@mail.exampledomain.hu hostname: mail0.exampledomain.hu mail_plugins: quota sieve deliver_log_format: msgid=%m: From=%f %$ auth default: mechanisms: plain login default_realm: exampledomain.hu user: dovecot passdb: driver: sql args: /data/apps/dovecot/dovecot-mysql.conf userdb: driver: sql args: /data/apps/dovecot/dovecot-mysql.conf socket: type: listen client: path: /data/postfix/private/dovecot-auth-client mode: 438 user: dovecot group: dovecot master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: dovecot plugin: sieve: /data/mail/%d/%n/.sieve.dovecot sieve_dir: /data/mail/%d/%n quota: dict:User quota::proxy::quota quota_rule: *:storage=10GB dict: quota: mysql:/data/apps/dovecot/dict-sql.conf I didn't want to send it, because I don't know, which part is useful in this case. there are errors. http://wiki.dovecot.org/Logging Actually I've juest enabled all debugging related options, except password. I'm afraid, there will be too much messages. Anyway, the possible reasons: 1) Dovecot changed the UIDLs because something weird happened. In that case it logged an error. No error. 2) Did you use the courier migration script so that the UIDLs got converted to Dovecot? If not, maybe Outlook got confused because the UIDLs changed, and fixing it would require recreating the Outlook account or something.. No, there was no conversation. I was thinking about recreating the account, but it's not possible right now. It will be actual in 1-2 weeks. Anyway, even if it help, there is an error, which does not happen all the time, still I think it's server related. 3) Outlook just doesn't like the new UIDLs and messes up itself. I think Courier usually uses maildir filenames as UIDLs, you could have kept doing that with pop3_uidl_format=%f. But changing it now would cause users to redownload everything again.. With v1.2.5+ you could use pop3_save_uidl=yes to make it possible to change UIDLs on the fly. Are you sure, it can be enabled on the fly and if I use it, the mail won't be donwload again after changing the uidl format? Thank you, tamas
Re: [Dovecot] pop3+leave messages on server
Justin Krejci wrote, On 2009. 12. 29. 16:27: Not to pick nits but pop3+leave on server does not mean you have all message from the dawn of time stored on the server. Outlook and presumably other MUAs have remove from server after X time and remove from server when message is deleted options when leaving pop3 messages on the server is enabled. I agree with the general principal though that if you wish to keep messages on server as general practice you should use IMAP. IMO pop3+leave is really only ideal while traveling using other clients/computers or maybe if IMAP is not offered at all. This is not an ideal situation, we are agreed. tamas
Re: [Dovecot] pop3+leave messages on server
Charles Marcus wrote, On 2009. 12. 29. 13:18: The fact that he has had 'no problems' in many years is purely the luck of the draw. One minor bug in either the IMAP/POP server or the mail client during an upgrade or other maintenance, and boom - he will *really* be surprised when *all* of his messages from the last few *years* are downloaded again, not just the last few hours worth. No, he makes the messages deleted from time to time. tamas
Re: [Dovecot] architecture to handle 1000 messages per second?
Hi all, Thanks for the suggestions. It sounds like the consensus is that I should avoid polling with POP or IMAP and deal with incoming messages directly. Bob
Re: [Dovecot] Kernel warnings
* Timo Sirainen, 2010-01-03 22:54 On 3.1.2010, at 9.12, Thomas Zajic wrote: 1. a bug in the kernel that is triggered by something that dovecot's inotify code does, or Yes. Is there anything related I should/could tune in /proc/sys/fs/inotify? Probably not. I'd ask about this in your distro or kernel mailing list. Okay, will do. Thanks! Bye, Thomas
