Re: [Dovecot] Problems with Apple Mail: Enter Password for Account "..."
* Frank Röhm 2013.05.22 16:44:
> In the logfiles of Dovecot I don't find anything about this.
Mail.App is known to utilize many concurrent connections. Look again, most
likely it maxes out the limit:
protocol imap {
mail_max_userip_connections = 10
}
Regards
Thomas
signature.asc
Description: Digital signature
[Dovecot] Error: Initial status notification not received
Hi , We are getting a below error on our Dovecot POP/IMAP server on every alternate days. Please help us in knowing with the errors are related to May 23 02:40:05 blade7 dovecot: master: Error: service(pop3-login): Initial status notification not received in 30 seconds, k illing the process May 23 02:40:05 blade7 dovecot: master: Error: service(log): child 8697 killed with signal 9 May 23 02:42:04 blade7 dovecot: master: Error: service(pop3-login): Initial status notification not received in 30 seconds, k illing the process May 23 02:42:04 blade7 dovecot: master: Error: service(ssl-params): Initial status notification not received in 30 seconds, k illing the process May 23 02:42:04 blade7 dovecot: master: Error: service(log): Initial status notification not received in 30 seconds, killing the process May 23 02:42:04 blade7 dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killin g the process May 23 02:42:04 blade7 dovecot: master: Error: service(imap-login): Initial status notification not received in 30 seconds, k illing the process Regards, Kavish Karkera
Re: [Dovecot] problem with proxy setup
Hi all,
i could solve my problem.
the solution is to set the unneeded fields to "NULL" - it's described in
WIKI, but i overlooked this important statement.
Sorry for my blindness
On 22.05.2013 18:37, Claus wrote:
Hi all,
i have some troubles in the implementation of my proxyconfiguration.
i have two kind of users, the first will be proxied to a dovecot
backend with masteruser-login, the other one will be proxied to
another non-dovecot imapserver with nopassword.
Everything looks to work if i use passwd-file like this:
user1:{PLAIN}pass1:::proxy=y host=192.168.1.1
destuser=user1*masteruser pass=masterpass
user2nopassword proxy=y host=192.168.2.2
In an second step i try the same behavior with sql (postgresql), but
there are my problems.
In my thinking, the sql query should return the right fields (in
passwd-file) like proxy, host, ..
but whats the trick, to get only the correct fields i need for the
different funktions?
first proxy, host, destuser, pass and on the other side nopassword,
proxy and host.
Maybe i have mistakes in reasoning, but in sql i get in one query
always the same fields.
I hope someone can give me some hints an tricks.
thanks, Claus
Re: [Dovecot] Dovecot 2.2.2 compiling error
On 23.5.2013, at 9.05, Mart Pirita wrote: > Timo Sirainen kirjutas: >> On 22.5.2013, at 20.31, Mart Pirita wrote: >> >>> I cant build 2.2.2, but I can build fine version 2.1.16 with same options: >>> >>> RedHat based customized distro, 2.6.28.10 kernel >> What gcc version? >> > gcc -v > gcc version 3.3.6 Hmh. Does the attached patch help? diff Description: Binary data
Re: [Dovecot] auth with passwd file , doublepoint in paasword
Am 23.05.2013 01:47, schrieb Ben Morrow: > At 10PM +0200 on 22/05/13 you (Robert Schetterer) wrote: >> Hi, does anyone know >> if a doublepoint : is in the password how it gets escaped >> >> when using >> >> http://wiki2.dovecot.org/AuthDatabase/PasswdFile > > I don't think it can be; that is, I don't think any of the fields can > contain a colon if you're using passwd-file. > > Surely a password would usually be crypted, and so cannot contain a > colon? > > Ben > thats only for one time migration in a script, no big deal, i can change it manually, but a solution may welcome anyway Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
[Dovecot] How the does "new" autocreate method works?
Hi,
I'm trying to migrate from the deprecated autocreate plugin to the
mailbox { auto }setting without success.
What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the
folders other than the inbox itself.
# doveconf -n
# 2.2.2: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 9.1-STABLE amd64
auth_cache_negative_ttl = 0
auth_cache_size = 100 M
default_process_limit = 1000
default_vsz_limit = 1 G
disable_plaintext_auth = no
import_environment = LD_PRELOAD
info_log_path = syslog
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lmtp_save_to_detail_mailbox = yes
log_path = /var/log/dovecot-errors.log
mail_gid = 999
mail_location = maildir:~/Maildir
mail_plugins = " quota"
mail_temp_dir = /data/tmp
mail_uid = 999
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope
encoded-character vacation subaddress comparator-i;ascii-numeric
relational regex imap4flags copy include variables body enotify
environment mailbox date ihave
namespace inbox {
inbox = yes
location =
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Spam {
auto = subscribe
special_use = \Junk
}
mailbox Trash {
auto = subscribe
special_use = \Trash
}
prefix =
}
passdb {
args = /usr/local/etc/dovecot/master-users
driver = passwd-file
master = yes
pass = yes
}
passdb {
args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
plugin {
mail_log_events = delete mailbox_delete
mail_log_fields = uid box msgid size flags vsize from subject
quota = maildir:User quota
quota_warning = storage=95%% quota-warning 95 %h
quota_warning2 = storage=80%% quota-warning 80 %h
recipient_delimiter = +
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = pop3 imap lmtp
service auth {
unix_listener auth-userdb {
mode = 0600
user = qmailldap
}
}
service lmtp {
inet_listener lmtp {
port = 24
}
user = qmailldap
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
service quota-warning {
executable = script /usr/local/quota-warning/quota-warning.sh
unix_listener quota-warning {
user = qmailldap
}
user = qmailldap
}
ssl = no
userdb {
driver = prefetch
}
userdb {
args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext
driver = ldap
}
userdb {
args = /usr/local/etc/dovecot/dovecot-ldap-catchall.conf.ext
driver = ldap
}
verbose_proctitle = yes
protocol lmtp {
mail_plugins = " quota mail_log notify sieve"
}
protocol imap {
mail_plugins = " quota imap_quota mail_log notify"
}
Thanks,
Re: [Dovecot] How the does "new" autocreate method works?
On 23.5.2013, at 14.26, Attila Nagy wrote:
> I'm trying to migrate from the deprecated autocreate plugin to the mailbox {
> auto }setting without success.
> What do I forget, or misunderstand?
>
> I deliver mails via LMTP and log in on IMAP, neither of them create the
> folders other than the inbox itself.
The new method is creating the folders lazily to disk. They will be visible in
IMAP session, but they won't be actually created to disk until the folder is
opened.
Your config looks correct to me.
Re: [Dovecot] How the does "new" autocreate method works?
On 05/23/13 14:01, Timo Sirainen wrote:
On 23.5.2013, at 14.26, Attila Nagy wrote:
I'm trying to migrate from the deprecated autocreate plugin to the mailbox {
auto }setting without success.
What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the folders
other than the inbox itself.
The new method is creating the folders lazily to disk. They will be visible in
IMAP session, but they won't be actually created to disk until the folder is
opened.
Your config looks correct to me.
Exactly what I see, but I thought this was an error. Could you please
clarify this somewhere appropriate?
BTW, this is a problem for us, because we have a custom software
accessing the maildir, which won't see these until created.
Would it be possible to set the laziness of this process and provide the
possibility to create the folders on disk?
Thanks!
Re: [Dovecot] How the does "new" autocreate method works?
On 23.5.2013, at 15.06, Attila Nagy wrote:
> On 05/23/13 14:01, Timo Sirainen wrote:
>> On 23.5.2013, at 14.26, Attila Nagy wrote:
>>
>>> I'm trying to migrate from the deprecated autocreate plugin to the mailbox
>>> { auto }setting without success.
>>> What do I forget, or misunderstand?
>>>
>>> I deliver mails via LMTP and log in on IMAP, neither of them create the
>>> folders other than the inbox itself.
>> The new method is creating the folders lazily to disk. They will be visible
>> in IMAP session, but they won't be actually created to disk until the folder
>> is opened.
>>
>> Your config looks correct to me.
>>
> Exactly what I see, but I thought this was an error. Could you please clarify
> this somewhere appropriate?
> BTW, this is a problem for us, because we have a custom software accessing
> the maildir, which won't see these until created.
> Would it be possible to set the laziness of this process and provide the
> possibility to create the folders on disk?
This changed, because the previous behavior was unnecessarily accessing the
disk all the time at each login. I wasn't really planning on adding the old
behavior back anymore. Maybe you could create the folders when the user is
created?
Re: [Dovecot] How the does "new" autocreate method works?
On 05/23/13 14:08, Timo Sirainen wrote:
On 23.5.2013, at 15.06, Attila Nagy wrote:
On 05/23/13 14:01, Timo Sirainen wrote:
On 23.5.2013, at 14.26, Attila Nagy wrote:
I'm trying to migrate from the deprecated autocreate plugin to the mailbox {
auto }setting without success.
What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the folders
other than the inbox itself.
The new method is creating the folders lazily to disk. They will be visible in
IMAP session, but they won't be actually created to disk until the folder is
opened.
Your config looks correct to me.
Exactly what I see, but I thought this was an error. Could you please clarify
this somewhere appropriate?
BTW, this is a problem for us, because we have a custom software accessing the
maildir, which won't see these until created.
Would it be possible to set the laziness of this process and provide the
possibility to create the folders on disk?
This changed, because the previous behavior was unnecessarily accessing the
disk all the time at each login. I wasn't really planning on adding the old
behavior back anymore. Maybe you could create the folders when the user is
created?
Very good point, will do.
Thanks.
Re: [Dovecot] Dovecot 2.2.2 compiling error
Timo Sirainen kirjutas: gcc -v gcc version 3.3.6 Hmh. Does the attached patch help? Yes, it does, thanks! -- Mart
[Dovecot] Passwordless auth?
Hey all, I'm in the process of writing some scripts which I want to be able to take actions on my local mailbox. (For example, to move a subset of messages to the trash over time, if unread for a week. To act on messages in my learn-spam folder and then delete them). What occured to me as being a Neat Idea is if Dovecot could honor ident (rfc1413) lookups, from trusted hosts (i.e. 127.0.0.1). In this way I get all the benefits of dovecot's indexing being updated and nice locking, but I don't have to leave my password laying around in a plaintext file. (Yes, this assumes I'm running a shell on the mail server. I'm not concerned about the same level of security when you could simply cat my mail spool). I'd definitely consider something like an SSH key with a forced command (I do see questions in the FAQ about making dovecot work over a socket connection), but that forgoes using standard imap clients. I could also create a dovecot-only user with my UID and no other login privileges, but I'd like this to "just work" for anyone. I don't know anything about if dovecot supports X509 auth, but this would require the client libraries to support such a thing, which not all do. I'd love to hear about any other ways people have thought about to do this. Any ideas? -Dan Mahoney -- Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---
Re: [Dovecot] Passwordless auth?
On Thu, May 23, 2013 at 04:10:01PM -0700, Dan Mahoney, System Admin wrote: > I'd love to hear about any other ways people have thought about > to do this. Any ideas? Are you familiar with the mutt(1) MUA? I use it with a: set tunnel="MAILDIR=~/Mail/ /usr/libexec/dovecot/imap" So it speaks IMAP, but to its own /usr/libexec/dovecot/imap process, not through a network socket. Maybe you could adapt this idea in some way. -- http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
Re: [Dovecot] Passwordless auth?
At 4PM -0700 on 23/05/13 you (Dan Mahoney, System Admin) wrote: > > I'm in the process of writing some scripts which I want to be able to take > actions on my local mailbox. (For example, to move a subset of messages > to the trash over time, if unread for a week. To act on messages in my > learn-spam folder and then delete them). http://wiki2.dovecot.org/PreAuth You can also use doveadm for quite a lot of this sort of administration; this may be easier if you're scripting in shell rather than something more sophisticated. > I'd definitely consider something like an SSH key with a forced > command (I do see questions in the FAQ about making dovecot work over a > socket connection), but that forgoes using standard imap clients. Well, I'm not sure what you consider 'standard' here, but there are both Perl and Python IMAP libraries which will connect to a command rather than a socket. If you're using a client which insists on connecting to an (INET) socket, it's a little harder; while you can obviously connect preauthed imap to a listening socket with netcat, that's not remotely secure. > I could also create a dovecot-only user with my UID and no other login > privileges, but I'd like this to "just work" for anyone. I believe with the latest 2.2 you can also do this with Kerberos principals, if you're running Kerberos; I haven't looked into this yet, but I mean to (for much the same reason). Ben
Re: [Dovecot] Passwordless auth?
On Fri, 24 May 2013, Ben Morrow wrote: At 4PM -0700 on 23/05/13 you (Dan Mahoney, System Admin) wrote: I'm in the process of writing some scripts which I want to be able to take actions on my local mailbox. (For example, to move a subset of messages to the trash over time, if unread for a week. To act on messages in my learn-spam folder and then delete them). http://wiki2.dovecot.org/PreAuth Aah! I came across this in the Q&A, and assumed such a thing wasn't possible: -=- Can Dovecot authenticate and work via UNIX sockets? Dovecot authentication already works via UNIX sockets, but it only speaks its internal protocol. You could always create a "socket" passdb/userdb. Probably should be made compatible with "checkpassword" protocol. Patches welcome :) -=- Which could probably use some expansion/repointing. The "preauth" name kind of just implies in my mind "things you check before pam" -- I would have not looked there if not pointed. You can also use doveadm for quite a lot of this sort of administration; this may be easier if you're scripting in shell rather than something more sophisticated. I'm pretty much resigned to trying to parse the whole mailbox anyway, because I want functions like "when I move a message to the "threadkill" folder, move any message with the referenced messageid's in said message to folder X". All this is in pursuit of making that little red number in my mail.app window meaningful -- and it seems the only real control plane mobile clients give you is the ability to move a message to a folder :) I'd definitely consider something like an SSH key with a forced command (I do see questions in the FAQ about making dovecot work over a socket connection), but that forgoes using standard imap clients. Well, I'm not sure what you consider 'standard' here, but there are both Perl and Python IMAP libraries which will connect to a command rather than a socket. If you're using a client which insists on connecting to an (INET) socket, it's a little harder; while you can obviously connect preauthed imap to a listening socket with netcat, that's not remotely secure. I'm constructing a client, really. In perl, it looks like Mail::Box::Manager is the thing I want, in conjunction with the above. I could also create a dovecot-only user with my UID and no other login privileges, but I'd like this to "just work" for anyone. I believe with the latest 2.2 you can also do this with Kerberos principals, if you're running Kerberos; I haven't looked into this yet, but I mean to (for much the same reason). we are at the day job, but I'm not doing so personally. -Dan -- Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org ---
[Dovecot] . (dot) in maildir folder names
Hi. Uhm... yeah as the topic implies I want to have . (dots) in my folder names... Unfortunately dovecot's maildirmake hasn't a -f switch as the one from courier/maildrop, but that one in turn is buggy[0] and doesn't encode any characters at all. In principle, maildir++ should allow[1] having (encoded) dots in folder names,... but I don't quite understand how the encoding actually works, cause UTF-7 seems to be already the encoded (without padding and such)... but . is . in UTF-7 as well. Does dovecot support this? At least my mail clients (well I only tried Evolution so far which sucks in so many areas)... couldn't create it... but I guess it's rather a stupid client issue. Anyone knows how it would be encoded? Interestingly, and this might be actually an inssue in doveocot when I create maildirs with non-ASCII chars without encoding these, e.g. maildir/.München/ (instead of the correctly encoded (.M&APw-nchen) Dovecot seems to "export" these to the clients,... at least Evolution shows it in the list of subscribable folders (even correctly as "München")... but it doesn't allow me to actually subscribe to it. Cheers & thx, Chris. [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709555 [1] http://www.courier-mta.org/maildir.html#id351803 smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] . (dot) in maildir folder names
Maybe the whole thing IS actually also a dovecot issue... When trying to create a folder with a dot with thunderbird (which doesn't simply forbid this)... it actually transmits the folder name to dovecote (e.g. "kernel.org")... but dovecot then literally takes this over and creates .kernel.org, i.e. no encoding and thus org becomes a subfolder. Cheers, Chris. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] Passwordless auth?
> You can also use doveadm for quite a lot of this sort of administration; > this may be easier if you're scripting in shell rather than something > more sophisticated. +1
Re: [Dovecot] . (dot) in maildir folder names
On 2013-05-23 18:41, Christoph Anton Mitterer wrote: Uhm... yeah as the topic implies I want to have . (dots) in my folder names... Unfortunately dovecot's maildirmake hasn't a -f switch as the one from courier/maildrop, but that one in turn is buggy[0] and doesn't encode any characters at all. Does adding LAYOUT=fs to mail_location, which makes Dovecot use a dir hierarchy instead of dot-prefixing, make this possible? P.S., You don't need to use a maildirmake script with Dovecot--it will automatically create the Maildir on the first mail delivery (assuming you're using the deliver agent). -- Please reply on list.
Re: [Dovecot] . (dot) in maildir folder names
Am 24.05.2013 03:41, schrieb Christoph Anton Mitterer: > Hi. > > Uhm... yeah as the topic implies I want to have . (dots) in my folder > names... > Unfortunately dovecot's maildirmake hasn't a -f switch as the one from > courier/maildrop, but that one in turn is buggy[0] and doesn't encode > any characters at all. > > In principle, maildir++ should allow[1] having (encoded) dots in folder > names,... but I don't quite understand how the encoding actually works, > cause UTF-7 seems to be already the encoded (without padding and > such)... but . is . in UTF-7 as well. > > Does dovecot support this? > At least my mail clients (well I only tried Evolution so far which sucks > in so many areas)... couldn't create it... but I guess it's rather a > stupid client issue. > Anyone knows how it would be encoded? > > > Interestingly, and this might be actually an inssue in doveocot when I > create maildirs with non-ASCII chars without encoding these, e.g. > maildir/.München/ (instead of the correctly encoded (.M&APw-nchen) > Dovecot seems to "export" these to the clients,... at least Evolution > shows it in the list of subscribable folders (even correctly as > "München")... but it doesn't allow me to actually subscribe to it. > > > Cheers & thx, > Chris. > > > > > [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709555 > [1] http://www.courier-mta.org/maildir.html#id351803 > look http://wiki2.dovecot.org/Plugins/Listescape Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
