[Dovecot] Refilter Mailboxes via Sieve - Missing delivered-to header
Hello,
i already read http://wiki.dovecot.org/HowTo/RefilterMail but it won't
work here :(
I have many old mails in my folders and need to refilter many of them.
But there are many mails without a delivered-to-header.
What can i do?
Error:
Configuration error: envelope_recipient specified header missing
(delivered-to:1)
Would be okay if getmail would just skip the mail, but it cancels. Not
sure if there is any way around.
This is the config:
[retriever]
type = MultidropIMAPSSLRetriever
envelope_recipient = delivered-to:1
server = foo
port = 993
username = foo
password = foo
mailboxes = ("INBOX.REFILTER",)
move_on_delete = INBOX.trash
[destination]
type = MDA_external
path = /usr/lib/dovecot/deliver
arguments = ("-e", "-f", "%(sender)", "-d", "%(recipient)")
user = vmail
group = vmail
[options]
delete = true
recieved = false
delivered_to = false
verbose = 2
I'm using virtual users, so i must use Multidrop.
Thanks
Re: [Dovecot] mail to admin when quota exceeded
Replying to myself is bad I know but its holiday time :) at least for a few more days... On Wed, 2011-01-12 at 09:32 +1000, Noel Butler wrote: > > That said, if you use dovecot 2.0.x's LDA, you *can* do this now, and > the wiki IIRC, does tell you how - we still use 1.2.x so I don't have > the command immediately at hand but recall seeing it (it might even work > on 1.2.x, but never bothered trying it) > I actually found we added it in our quota warning script commented out for when we do more to 2.0.. : -o "plugin/quota=maildir:User quota:noenforcing" is what you add in your warning script pipped command to bypass it for 2.0, the fact we dont use it now means old age is setting in as we must have tried it and given its commented out, it wont work with 1.2.x <> signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Making shared folders "unmovable"
Well, I've tried ACLs before and had no success, which I remembered when
looking back through the config file to try it now. :) But, perhaps I'm
missing something obvious! Here's what I've done: I enabled the ACL
features in IMAP with "mail_plugins = acl imap_acl" under the "protocol
imap {" section, as instructed in the wiki. I also added "acl = vfile"
under the "plugin {" section. I HUPped Dovecot so as to re-read the
config, and put a "dovecot-acl" in Maildir/.TestFolder that contains 1 line:
anyone lrwstipea
So, in theory, that should do it right? No "x" and no "k" permissions
in that list for "anyone", yet I can still delete, move, and rename the
"TestFolder" folder (in which that dovecot-acl file resides, on disk in
the folder above) through my mail client. What am I missing? Clearly
something! :) (I haven't tried restarting Dovecot yet as there are some
people using the mailbox at the moment, fwiw.)
Dave
On 1/11/2011 4:11 PM, Willie Gillespie wrote:
Jose Celestino wrote:
You may be able to do that with ACLs.
Jose is right. Take away the x and k rights with ACLs.
Re: [Dovecot] mail to admin when quota exceeded
On Wed, 2011-01-12 at 01:06 +0200, Karolis Žvaigždinas wrote: > We're using Dovecot v1.2.15 LDA/IMAP/POP3+MySQL with quota plugin, > quota_rule per-user size, quota_exceed_message and quota_warning on > storage=90%%.with script. > Everything is working as expected. > But I've been asked to configure it the way, that when a user gets message, > which would make his maildir over quota limit, notification go not only to > sender, but also to postmas...@domain.com. > Browsed wiki, mailinglist archive - couldn't find anything on that. > Is there a way to implement such feature? I use a perl script querying DB and test active domains (since there is no domain quotas) every hour, you could adapt it to test users and send a message rather than what it does, if you dont have many users it should not be much of a problem. it warns the domain manager, and suspends inbound mail. nasty but a necessary evil. but I think you need to make your warning messages more compliance strict, we send a friendly relaxed warning at 75%, a more serious message at 90% telling them to clear out old stuff and purge unneeded now, not wait until they dont see any new mail and wonder why, if they dont clear out the mail, they have no one but themselves to blame. > And what about possibility to send a message to user, notifying him about > rejected email "from: x...@yyy.com" with "subj: blah blah" due to full > mailbox? Such messages are small and would not take too much space. Thus the > user would know what he misses, urging him to clean his mailbox. > Thats all nice and well, but what if you have these limits because of disk space, 1000 users getting 100 of these a day WILL add up. That said, if you use dovecot 2.0.x's LDA, you *can* do this now, and the wiki IIRC, does tell you how - we still use 1.2.x so I don't have the command immediately at hand but recall seeing it (it might even work on 1.2.x, but never bothered trying it) signature.asc Description: This is a digitally signed message part
[Dovecot] mail to admin when quota exceeded
We're using Dovecot v1.2.15 LDA/IMAP/POP3+MySQL with quota plugin, quota_rule per-user size, quota_exceed_message and quota_warning on storage=90%%.with script. Everything is working as expected. But I've been asked to configure it the way, that when a user gets message, which would make his maildir over quota limit, notification go not only to sender, but also to postmas...@domain.com. Browsed wiki, mailinglist archive - couldn't find anything on that. Is there a way to implement such feature? And what about possibility to send a message to user, notifying him about rejected email "from: x...@yyy.com" with "subj: blah blah" due to full mailbox? Such messages are small and would not take too much space. Thus the user would know what he misses, urging him to clean his mailbox. Thank you in advance. -- Karolis
Re: [Dovecot] Making shared folders "unmovable"
Jose Celestino wrote: On Ter, 2011-01-11 at 12:27 -0600, Dave wrote: I have set up an area of shared folders with Dovecot 1.2 that is accessed by several people (by way of one account, and everyone who logs in sees these same folders), and the only problem with this setup is that occasionally somebody moves one of the folders underneath another folder or somewhere else in the folder structure, and this sometimes disrupts some automatic procmail filters and the like. Is there a way to keep folders in a shared setup such as this "static" or "unmovable" so that the users can't disrupt the structure? Like, where the folder structure itself can't be changed, but new messages can still come in to the folders? You may be able to do that with ACLs. Jose is right. Take away the x and k rights with ACLs.
Re: [Dovecot] Dovecot fails after updating MySQL
Jerry schreef: I then turned on some of the logging function in Dovecot and restarted it. I then had Postfix roguery some messages. This is a snippet of the dovecot log. Sorry about the line wrap. I am not using my regular MUA at present. Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 dovecot: Error: child 85589 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85588 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85580 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 dovecot: Error: child 85596 (auth-worker) killed with signal 11 (core not dumped) I doubt that this will be of any value; however, it cannot hurt to submit it. just hit the ports tree mysql55-client 5.5.8_2 With the following comment. Remove any attempts to create a libmysqlclient not linked to a threading library. Restore previous libraries location. These two changes should fix most of the reported errors. I think you can try again. regards, Johan Hendriks
Re: [Dovecot] Denying authentication
On 11/01/2011 20:10, Romer Ventura wrote: -Original Message- From: dovecot-bounces+rventura=h-st@dovecot.org [mailto:dovecot-bounces+rventura=h-st@dovecot.org] On Behalf Of Simone Caruso Sent: Tuesday, January 11, 2011 12:18 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] Denying authentication What I would like to know is if there is any way that I could deny access for users trying to access email via cellphones or email clients outside the company. I can close everything since there are a few users that need to get emails from outside the company via cell phone of email clients. I was thinking if there was a way to lets say create a group in AD named: "remote-email" that will allow connection and authentication from any network, any user not in that group will only be able to authenticate if the source is 192.168.xx.xx/24. Is this possible? Read this: http://wiki1.dovecot.org/PasswordDatabase/ExtraFields/AllowNets -- Simone Caruso IT Consultant p.iva: 03045250838 Yeah, but again. There are certain users that will need to access their email from outside our local networks. This would work for half of what I would like to accomplish, the other half: "allow authentication for remote users as long as they belong to certain LDAP group" or something similar is what I am more interested on. You can try using two userdb with different LDAP queries for each ldap group(see MultipleDatabases wiki page), but i never tried something like this. -- Simone Caruso IT Consultant +39 349 65 90 805 p.iva: 03045250838
Re: [Dovecot] Connection queue full on my directors
On Tue, Jan 11, 2011 at 04:31:03PM +0200, Timo Sirainen wrote:
>
> Well, switching to high performance mode would work better for proxies:
> http://wiki2.dovecot.org/LoginProcess
>
That text does a good job at scaring me away from high perf mode.. I
wouldn't want any attackers stealing my user's passwords. Is it really
necessary to run this way, when the server otherwise doesn't seem to be
affected by the number of running processes ?
BTW: I'm seeing a bit more failed logins than I think there should be..
pop3-login: Disconnected (auth failed, 1 attempts):
user=, method=PLAIN, rip=xx.xx.xx.xxx, lip=xx.xxx.xx.xxx
imap-login: Aborted login (auth failed, 1 attempts):
user=, method=PLAIN, rip=xx.xxx.xxx.xx,
lip=xx.xxx.xx.xxx, TLS
Could these be explained with the fact that we earlier didn't offer STARTTLS,
because users might be talking with one of the CNAMEs that doesn't match the
certificate name, and with this new config we started offering STARTTLS ?
I'm a bit reluctant to do it, but if we do get too many complaints about failed
logins, will it be it possible to disable STARTTLS, while keeping SSL active
for the imaps/pops ports on the director ?
Current config and stats:
#
# 2.0.8: /usr/local/dovecot-2.0.8/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-194.32.1.el5 x86_64 Red Hat Enterprise Linux Server release
5.5 (Tikanga)
director_mail_servers = 192.168.42.7 192.168.42.8 192.168.42.9 192.168.42.10
192.168.42.11 192.168.42.28 192.168.42.29
director_servers = 192.168.42.15 192.168.42.17
disable_plaintext_auth = no
listen = *
passdb {
args = proxy=y nopassword=y
driver = static
}
service anvil {
client_limit = 2051
}
service auth {
client_limit = 4196
}
service director {
fifo_listener login/proxy-notify {
mode = 0666
}
inet_listener {
port = 5515
}
unix_listener director-userdb {
mode = 0600
}
unix_listener login/director {
mode = 0666
}
}
service imap-login {
executable = imap-login director
process_limit = 1024
}
service pop3-login {
executable = pop3-login director
process_limit = 1024
}
ssl_cert =
Re: [Dovecot] Fatal crash during a user search
On Dovecot 2.0.7 sorry
Quoting Rick Romero :
Well, it looks like it occurred during the search to me...
>
> Jan 10 17:05:37 sysvolone dovecot: [ID 583609 mail.crit]
> imap(u...@host.com): Panic: file istream-header-filter.c: line 520
> (i_stream_create_header_filter): assertion failed: (ret < 0)
> Jan 10 17:05:37 sysvolone dovecot: [ID 583609 mail.error]
> imap(u...@host.com): Error: Raw backtrace:
> /usr/local/lib/dovecot/libdovecot.so.0.0.0'default_fatal_finish+0x3c
> [0xfee7b050] ->
> /usr/local/lib/dovecot/libdovecot.so.0.0.0'i_internal_fatal_handler+0x2b
> [0xfee7bbe7] -> /usr/local/lib/dovecot/libdovecot.so.0.0.0'0x3b239
> [0xfee7b239] ->
>
/usr/local/lib/dovecot/libdovecot.so.0.0.0'i_stream_create_header_filter+0x12f
> [0xfee6598b] ->
>
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'index_mail_get_header_stream+0x17c
> [0xfef050cc] ->
>
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'mail_get_header_stream+0x13
> [0xfeee8b8b] ->
>
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'index_storage_search_next_nonblock+0x5bf
> [0xfef07807] ->
>
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'mailbox_search_next_nonblock+0x2a
> [0xfeeef4c6] -> /usr/local/libexec/dovecot/imap'cmd_search_more+0x78
> [0x806516c] -> /usr/local/libexec/dovecot/imap'imap_search_start+0x18e
> [0x8065612] -> /usr/local/libexec/dovecot/imap'c
> Jan 10 17:05:37 sysvolone dovecot: [ID 583609 mail.error] master: Error:
> service(imap): child 7746 killed with signal 6 (core not dumped - set
> service imap { drop_priv_before_exec=yes })
>
> I'm not sure if that gives you what you need - it looks like the entire
> dump didn't get saved.
>
> This is on OpenSolaris 5.11 snv_134
>
> Rick
[Dovecot] Fatal crash during a user search
Well, it looks like it occurred during the search to me...
Jan 10 17:05:37 sysvolone dovecot: [ID 583609 mail.crit]
imap(u...@host.com): Panic: file istream-header-filter.c: line 520
(i_stream_create_header_filter): assertion failed: (ret < 0)
Jan 10 17:05:37 sysvolone dovecot: [ID 583609 mail.error]
imap(u...@host.com): Error: Raw backtrace:
/usr/local/lib/dovecot/libdovecot.so.0.0.0'default_fatal_finish+0x3c
[0xfee7b050] ->
/usr/local/lib/dovecot/libdovecot.so.0.0.0'i_internal_fatal_handler+0x2b
[0xfee7bbe7] -> /usr/local/lib/dovecot/libdovecot.so.0.0.0'0x3b239
[0xfee7b239] ->
/usr/local/lib/dovecot/libdovecot.so.0.0.0'i_stream_create_header_filter+0x12f
[0xfee6598b] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'index_mail_get_header_stream+0x17c
[0xfef050cc] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'mail_get_header_stream+0x13
[0xfeee8b8b] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'index_storage_search_next_nonblock+0x5bf
[0xfef07807] ->
/usr/local/lib/dovecot/libdovecot-storage.so.0.0.0'mailbox_search_next_nonblock+0x2a
[0xfeeef4c6] -> /usr/local/libexec/dovecot/imap'cmd_search_more+0x78
[0x806516c] -> /usr/local/libexec/dovecot/imap'imap_search_start+0x18e
[0x8065612] -> /usr/local/libexec/dovecot/imap'c
Jan 10 17:05:37 sysvolone dovecot: [ID 583609 mail.error] master: Error:
service(imap): child 7746 killed with signal 6 (core not dumped - set
service imap { drop_priv_before_exec=yes })
I'm not sure if that gives you what you need - it looks like the entire
dump didn't get saved.
This is on OpenSolaris 5.11 snv_134
Rick
Re: [Dovecot] Denying authentication
-Original Message- From: dovecot-bounces+rventura=h-st@dovecot.org [mailto:dovecot-bounces+rventura=h-st@dovecot.org] On Behalf Of Simone Caruso Sent: Tuesday, January 11, 2011 12:18 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] Denying authentication > What I would like to know is if there is any way that > I could deny access for users trying to access email via cellphones or > email clients outside the company. I can close everything since there > are a few users that need to get emails from outside the company via > cell phone of email clients. > > > > I was thinking if there was a way to lets say create > a group in AD named: "remote-email" that will allow connection and > authentication from any network, any user not in that group will only > be able to authenticate if the source is 192.168.xx.xx/24. > > > > Is this possible? Read this: http://wiki1.dovecot.org/PasswordDatabase/ExtraFields/AllowNets -- Simone Caruso IT Consultant p.iva: 03045250838 Yeah, but again. There are certain users that will need to access their email from outside our local networks. This would work for half of what I would like to accomplish, the other half: "allow authentication for remote users as long as they belong to certain LDAP group" or something similar is what I am more interested on. Any thoughts? Thanks
Re: [Dovecot] Dovecot - AllowGroups option
Hi, Found It :) Here it is - very simple. Add the group you wanna use to /etc/group maigroup:x:1007:user1,user2,user3 Make a file listing the groups you wanna allow access from echo "maigroup" > /etc/dovecot/group.allow Add group authentication to dovecot pam setting in /etc/pam.d/dovecot Add this line on the top of the file auth required pam_listfile.so onerr=fail item=group sense=allow file=/etc/dovecot/group.allow I hope I can safe other people the trouble. /Neergaard Den 30/12/2010 kl. 11.09 skrev Timo Sirainen: > On Tue, 2010-12-28 at 00:15 +0100, Jacob Neergaard Pedersen wrote: >> I'm trying to control access to different services on an Debian server using >> /etc/group. So that a user I create for FTP usage doesn't fill up my server >> with IMAP folders or samba garbage. > > Assuming you use passdb pam, I think pam_listfile can do this: > http://www.kernel.org/pub/linux/libs/pam/Linux-PAM-html/sag-pam_listfile.html >
Re: [Dovecot] Making shared folders "unmovable"
On Ter, 2011-01-11 at 12:27 -0600, Dave wrote: > I have set up an area of shared folders with Dovecot 1.2 that is > accessed by several people (by way of one account, and everyone who logs > in sees these same folders), and the only problem with this setup is > that occasionally somebody moves one of the folders underneath another > folder or somewhere else in the folder structure, and this sometimes > disrupts some automatic procmail filters and the like. > > Is there a way to keep folders in a shared setup such as this "static" > or "unmovable" so that the users can't disrupt the structure? Like, > where the folder structure itself can't be changed, but new messages can > still come in to the folders? > You may be able to do that with ACLs. -- Jose Celestino | http://japc.uncovering.org/files/japc-pgpkey.asc "Assumption is the Mother of Screw-Up" -- Mr. John Elwood Hale
[Dovecot] Making shared folders "unmovable"
I have set up an area of shared folders with Dovecot 1.2 that is accessed by several people (by way of one account, and everyone who logs in sees these same folders), and the only problem with this setup is that occasionally somebody moves one of the folders underneath another folder or somewhere else in the folder structure, and this sometimes disrupts some automatic procmail filters and the like. Is there a way to keep folders in a shared setup such as this "static" or "unmovable" so that the users can't disrupt the structure? Like, where the folder structure itself can't be changed, but new messages can still come in to the folders? David
Re: [Dovecot] Denying authentication
What I would like to know is if there is any way that I could deny access for users trying to access email via cellphones or email clients outside the company. I can close everything since there are a few users that need to get emails from outside the company via cell phone of email clients. I was thinking if there was a way to lets say create a group in AD named: "remote-email" that will allow connection and authentication from any network, any user not in that group will only be able to authenticate if the source is 192.168.xx.xx/24. Is this possible? Read this: http://wiki1.dovecot.org/PasswordDatabase/ExtraFields/AllowNets -- Simone Caruso IT Consultant p.iva: 03045250838
[Dovecot] Denying authentication
Hello, I've been running dovecot for over 3 years now and it works with no problems. I have it setup so that it authenticates users against Active Directory via LDAP and so far no problems. What I would like to know is if there is any way that I could deny access for users trying to access email via cellphones or email clients outside the company. I can close everything since there are a few users that need to get emails from outside the company via cell phone of email clients. I was thinking if there was a way to lets say create a group in AD named: "remote-email" that will allow connection and authentication from any network, any user not in that group will only be able to authenticate if the source is 192.168.xx.xx/24. Is this possible? Maybe not with Dovecot, but maybe someone else has any ideas..? Thanks Romer Ventura
Re: [Dovecot] Dovecot fails after updating MySQL
I then turned on some of the logging function in Dovecot and restarted it. I then had Postfix roguery some messages. This is a snippet of the dovecot log. Sorry about the line wrap. I am not using my regular MUA at present. Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Loading modules from directory: /usr/local/lib/dovecot/lda Jan 11 10:33:19 deliver(r...@seibercom.net): Info: Module loaded: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so Jan 11 10:33:19 auth(default): Info: master in: USER1 r...@seibercom.net service=deliver Jan 11 10:33:19 dovecot: Error: child 85589 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85588 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 dovecot: Error: child 85580 (auth-worker) killed with signal 11 (core not dumped) Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 deliver(r...@seibercom.net): Error: userdb lookup(r...@seibercom.net) failed: Internal failure Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 auth(default): Error: worker-server(r...@seibercom.net): Aborted: Worker process died unexpectedly Jan 11 10:33:19 auth(default): Info: master out: FAIL 1 Jan 11 10:33:19 dovecot: Error: child 85596 (auth-worker) killed with signal 11 (core not dumped) I doubt that this will be of any value; however, it cannot hurt to submit it. -- Jerry
Re: [Dovecot] Dovecot fails after updating MySQL
On Tue, Jan 11, 2011 at 8:44 AM, Maxim Kostikov wrote: > Well, I believe that this is not Dovecot fault so all questions and > complains must be addressed to MySQL developers. I would question if that is factually correct. I did have a problem with Postfix; however, after rebuilding Postfix it started working correctly. For some unknown reason, that is not the case with Dovecot. Therefore, until I have seen proof confirming that it is a "MySQL 5.5.8+" problem, I will continue to investigate why only Dovecot seems to be exhibiting this behavior. I do intend to check on the MySQL forum though for a possible solution. By the way, I have KDE apps that are working fine with this newer version of MySQL also. -- Jerry
Re: [Dovecot] Dovecot fails after updating MySQL
Thank you! So it will be better to use 5.5.7 waiting for bugfix. 2011/1/11 Jerry > On Tue, Jan 11, 2011 at 8:47 AM, Maxim Kostikov > wrote: > > Tell us please, did you tried to rebuild Dovecot with 5.5.8 or with > 5.5.8_1 > > version of MySQL client? > > I hope that in 5.5.8_1 this bug must fixed already. > > The latter (5.5.8_1). > > -- > Jerry > -- Best regards, Maxim V. Kostikov ICQ #115377
Re: [Dovecot] Dovecot fails after updating MySQL
On Tue, Jan 11, 2011 at 8:47 AM, Maxim Kostikov wrote: > Tell us please, did you tried to rebuild Dovecot with 5.5.8 or with 5.5.8_1 > version of MySQL client? > I hope that in 5.5.8_1 this bug must fixed already. The latter (5.5.8_1). -- Jerry
[Dovecot] Seeing other people subscribed non-shared mailboxes
Hello Timo,
With dovecot-2.0.8/Maildir, in a simple shared mailboxes setting I noticed the
following :
- user "doveimap" has 2 mailboxes : "Common" and "Private"
- he shares only the "Common" mailbox to user "dovepop" doing :
x setacl "Common" dovepop lrwstipekxacd
x OK Setacl complete.
- he subscribed to both
x lsub "" *
* LSUB () "." "Trash"
* LSUB () "." "Common"
* LSUB () "." "Private"
x OK Lsub completed.
I'm not realy sure if the fact that "dovepop" can see doveimap's subscribed
"Private" mailbox in the "#Shared" namespace is legitimate or not :
x login dovepop x
x OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT
SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN
NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT
SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL RIGHTS=texk] Logged in
x list "" *
* LIST (\HasNoChildren) "." "Trash"
* LIST (\HasNoChildren) "." "INBOX"
* LIST (\Noselect \HasChildren) "." "#shared.doveimap"
* LIST (\HasNoChildren) "." "#shared.doveimap.Common"
x OK List completed.
x lsub "" *
* LSUB () "." "Trash"
* LSUB (\Noselect) "." "#shared.doveimap"
* LSUB (\Noselect) "." "#shared.doveimap.Trash"
* LSUB () "." "#shared.doveimap.Common"
* LSUB (\Noselect) "." "#shared.doveimap.Private"
x OK Lsub completed.
x logout
Is this the way it's supposed to work ?
My setup is :
namespace {
type = shared
separator = "."
prefix = "#shared.%%u."
location =
maildir:/courriel/boites/%%u:INDEX=/var/dovecot-2/indexes/%1u/%u/shared/%%u:CONTROL=/courriel/meta/%%u
# Use the default namespace for saving subscriptions.
# subscriptions = no
# hidden = no
# list = no
list = children
}
# pwd
/courriel/boites/doveimap
# cat dovecot-acl-list
1294755382 Common
# cat .Common/dovecot-acl
user=dovepop akxeilprwts
# cat .Private/dovecot-acl
cat: .Private/dovecot-acl: No such file or directory
Also, I'm not sure I correctly understand what "Use the default namespace for
saving subscriptions." option is. Is it just the location of the subscription
file for mailboxes subscribed in the shared namespace ? Where would it be if
set to "yes" ?
Thanks.
--
Thomas Hummel | Institut Pasteur
| Pôle informatique - systèmes et réseau
Re: [Dovecot] Max number of mail processes
On 11.1.2011, at 0.37, Patrick Nudo wrote: > Dovecot version 1.1.11. > Error: Maximum number of mail processes exceeded (see max_mail_processes > setting). > > I can't seem to get rid of these errors. I get batches of these errors > about 4 or 5 times a day. I have a cron-job checking for the existence of > this error and then I reboot dovecot when I see this error, but what is > causing this error ? What I am reading on the Internet about this > particular issue has not helped to resolve the issue. I would really like > to know how many mail processes it thinks that it is using at any one instant > in time. Is this possible ? Maybe then I can track the reason for the > error. It thinks there are max_mail_processes number of processes running at that time. Which you can find out with: dovecot -a | grep max_mail_processes
Re: [Dovecot] enforce STARTTLS on port 110 with POP3?
On 11.1.2011, at 6.48, Tom Talpey wrote: >>> The problem is that we have no way to enforce STARTTLS on 110, user can >>> connect to DoveCot on port 110, sending user credential without STARTTLS >>> (thus insecure). >> >> default_plaintext_auth = yes >> > You meant "disable_plaintext_auth", right? Yeah.
Re: [Dovecot] Dovecot fails after updating MySQL
See it here from my previous post http://dovecot.org/pipermail/dovecot/2011-January/056217.html 2011/1/11 Timo Sirainen > On 11.1.2011, at 15.01, Jerry wrote: > > > On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov > wrote: > >> The problem is in new buggy MySQL client. I wrote to this list before > about > >> it. Roll back to previous version 5.5.7 for a while (server may stills > >> 5.5.8). > > > > I will probably have no choice. I was wondering if Timo had any ideas > > on this however. > > I might if someone can produce a gdb backtrace of the crash. -- Best regards, Maxim V. Kostikov ICQ #115377
Re: [Dovecot] Connection queue full on my directors
On 11.1.2011, at 12.03, Jan-Frode Myklebust wrote: > $ ps -ef|grep dovecot/pop3-login|wc -l > 192 > $ ps -ef|grep dovecot/imap-login|wc -l > 472 > > so looks like I'm quite close to hitting this limit for my imap logins. Well, switching to high performance mode would work better for proxies: http://wiki2.dovecot.org/LoginProcess
Re: [Dovecot] Multiple Authentication Databases
On 11.1.2011, at 15.28, Jonathan Tripathy wrote: > I wish to run Dovecot on my "Front End" outbound mail relay, and use > Dovecot purely for authentication purposes. However, each mysql database > for each domain will be on a separate server. Is there a way for dovecot > to authenticate against different databases depending on domain name? Not directly. You could create a checkpassword script to do it though.
Re: [Dovecot] Dovecot fails after updating MySQL
On 11.1.2011, at 15.01, Jerry wrote: > On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov > wrote: >> The problem is in new buggy MySQL client. I wrote to this list before about >> it. Roll back to previous version 5.5.7 for a while (server may stills >> 5.5.8). > > I will probably have no choice. I was wondering if Timo had any ideas > on this however. I might if someone can produce a gdb backtrace of the crash.
Re: [Dovecot] Multiple Authentication Databases
I see. I guess you could install an mysql to do this. Like trigerrs to others databases. Sorry, don't know much of this. []'sf.rique On Tue, Jan 11, 2011 at 11:42 AM, Jonathan Tripathy wrote: > Yes, but the problem there is that each database is controlled by > different untrusted individuals. If someone were to create a > username/password on a database that is higher in the list, they could > authenticate as that user, which is undesirable. > > > > On 11/01/11 13:37, Henrique Fernandes wrote: > > Well, at least it work, it will fail until get the right databases. > > []'sf.rique > > > On Tue, Jan 11, 2011 at 11:32 AM, Jonathan Tripathy wrote: > >> I had a look there, but that doesn't have anything on a domain-by-domain >> basis >> >> >> On 11/01/11 13:31, Henrique Fernandes wrote: >> >> http://wiki2.dovecot.org/Authentication/MultipleDatabases >> >> Is that are you looking for ? >> >> []'sf.rique >> >> >> On Tue, Jan 11, 2011 at 11:28 AM, Jonathan Tripathy >> wrote: >> >>> Hi Everyone, >>> >>> I wish to run Dovecot on my "Front End" outbound mail relay, and use >>> Dovecot purely for authentication purposes. However, each mysql database >>> for each domain will be on a separate server. Is there a way for dovecot >>> to authenticate against different databases depending on domain name? >>> >>> Thanks >>> >>> >> >
Re: [Dovecot] Dovecot fails after updating MySQL
Tell us please, did you tried to rebuild Dovecot with 5.5.8 or with 5.5.8_1 version of MySQL client? I hope that in 5.5.8_1 this bug must fixed already. 2011/1/11 Jerry > On Tue, Jan 11, 2011 at 2:44 AM, Odhiambo Washington > wrote: > > On Tue, Jan 11, 2011 at 3:54 AM, Bradley Giesbrecht < > > bradley.giesbre...@gmail.com> wrote: > > > >> > >> On Jan 10, 2011, at 4:19 PM, Jerry wrote: > >> > >> I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system. > >>> Now Dovecot refuses to run. Prior to this, dovecot had been running for > >>> several > >>> years without a problem. > >>> > >>> > > Please recompile Dovecot again so that it re-links with the MySQL > library. > > This is a known problem on FreeBSD with the upgrade from MySQL 5.5.7 -> > > 5.5.8. I believe the port maintainer has also incorporated a fix into the > > FreeBSD ports. > > I all ready did that twice. I completely removed Dovecot before > reinstalling it the second time. The prolem still exists. In addition, > I am using th version of MySQL that the "port maintainer" supposed > fixed. I guess I will have no choice but to return to the older MySQL > version. I would be interrested todiscoverif this problem is isolated > strictly to FreeBSD + MySQL 5.5.8 however. > > -- > Jerry > -- Best regards, Maxim V. Kostikov ICQ #115377
Re: [Dovecot] Dovecot fails after updating MySQL
Well, I believe that this is not Dovecot fault so all questions and complains must be addressed to MySQL developers. 2011/1/11 Jerry > On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov > wrote: > > The problem is in new buggy MySQL client. I wrote to this list before > about > > it. Roll back to previous version 5.5.7 for a while (server may stills > > 5.5.8). > > I will probably have no choice. I was wondering if Timo had any ideas > on this however. > > -- > Jerry > -- Best regards, Maxim V. Kostikov ICQ #115377
Re: [Dovecot] Multiple Authentication Databases
Yes, but the problem there is that each database is controlled by different untrusted individuals. If someone were to create a username/password on a database that is higher in the list, they could authenticate as that user, which is undesirable. On 11/01/11 13:37, Henrique Fernandes wrote: Well, at least it work, it will fail until get the right databases. []'sf.rique On Tue, Jan 11, 2011 at 11:32 AM, Jonathan Tripathy mailto:jon...@abpni.co.uk>> wrote: I had a look there, but that doesn't have anything on a domain-by-domain basis On 11/01/11 13:31, Henrique Fernandes wrote: http://wiki2.dovecot.org/Authentication/MultipleDatabases Is that are you looking for ? []'sf.rique On Tue, Jan 11, 2011 at 11:28 AM, Jonathan Tripathy mailto:jon...@abpni.co.uk>> wrote: Hi Everyone, I wish to run Dovecot on my "Front End" outbound mail relay, and use Dovecot purely for authentication purposes. However, each mysql database for each domain will be on a separate server. Is there a way for dovecot to authenticate against different databases depending on domain name? Thanks
Re: [Dovecot] Multiple Authentication Databases
Well, at least it work, it will fail until get the right databases. []'sf.rique On Tue, Jan 11, 2011 at 11:32 AM, Jonathan Tripathy wrote: > I had a look there, but that doesn't have anything on a domain-by-domain > basis > > > On 11/01/11 13:31, Henrique Fernandes wrote: > > http://wiki2.dovecot.org/Authentication/MultipleDatabases > > Is that are you looking for ? > > []'sf.rique > > > On Tue, Jan 11, 2011 at 11:28 AM, Jonathan Tripathy wrote: > >> Hi Everyone, >> >> I wish to run Dovecot on my "Front End" outbound mail relay, and use >> Dovecot purely for authentication purposes. However, each mysql database >> for each domain will be on a separate server. Is there a way for dovecot >> to authenticate against different databases depending on domain name? >> >> Thanks >> >> >
Re: [Dovecot] Multiple Authentication Databases
I had a look there, but that doesn't have anything on a domain-by-domain basis On 11/01/11 13:31, Henrique Fernandes wrote: http://wiki2.dovecot.org/Authentication/MultipleDatabases Is that are you looking for ? []'sf.rique On Tue, Jan 11, 2011 at 11:28 AM, Jonathan Tripathy mailto:jon...@abpni.co.uk>> wrote: Hi Everyone, I wish to run Dovecot on my "Front End" outbound mail relay, and use Dovecot purely for authentication purposes. However, each mysql database for each domain will be on a separate server. Is there a way for dovecot to authenticate against different databases depending on domain name? Thanks
Re: [Dovecot] Multiple Authentication Databases
http://wiki2.dovecot.org/Authentication/MultipleDatabases Is that are you looking for ? []'sf.rique On Tue, Jan 11, 2011 at 11:28 AM, Jonathan Tripathy wrote: > Hi Everyone, > > I wish to run Dovecot on my "Front End" outbound mail relay, and use > Dovecot purely for authentication purposes. However, each mysql database > for each domain will be on a separate server. Is there a way for dovecot > to authenticate against different databases depending on domain name? > > Thanks > >
[Dovecot] Multiple Authentication Databases
Hi Everyone, I wish to run Dovecot on my "Front End" outbound mail relay, and use Dovecot purely for authentication purposes. However, each mysql database for each domain will be on a separate server. Is there a way for dovecot to authenticate against different databases depending on domain name? Thanks
[Dovecot] Multiple Authentication Databases
Hi Everyone, I wish to run Dovecot on my "Front End" outbound mail relay, and use Dovecot purely for authentication purposes. However, each mysql database for each domain will be on a separate server. Is there a way for dovecot to authenticate against different databases depending on domain name? Thanks
Re: [Dovecot] Dovecot fails after updating MySQL
On Tue, Jan 11, 2011 at 5:28 AM, Maxim Kostikov wrote: > The problem is in new buggy MySQL client. I wrote to this list before about > it. Roll back to previous version 5.5.7 for a while (server may stills > 5.5.8). I will probably have no choice. I was wondering if Timo had any ideas on this however. -- Jerry
Re: [Dovecot] Dovecot fails after updating MySQL
On Mon, Jan 10, 2011 at 7:54 PM, Bradley Giesbrecht wrote: > > What version of mysql were you at before? MySQL 5.7.x > Do your mysql logs reveal anything? No > Have you turned on mysql query logging? No > Can you run the /usr/local/etc/dovecot-sql.conf queries in a mysql client > successfully? I can manually run MySQL with the queries and they work OK. I will check further into this though. -- Jerry
Re: [Dovecot] Dovecot fails after updating MySQL
On Tue, Jan 11, 2011 at 2:44 AM, Odhiambo Washington wrote: > On Tue, Jan 11, 2011 at 3:54 AM, Bradley Giesbrecht < > bradley.giesbre...@gmail.com> wrote: > >> >> On Jan 10, 2011, at 4:19 PM, Jerry wrote: >> >> I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system. >>> Now Dovecot refuses to run. Prior to this, dovecot had been running for >>> several >>> years without a problem. >>> >>> > Please recompile Dovecot again so that it re-links with the MySQL library. > This is a known problem on FreeBSD with the upgrade from MySQL 5.5.7 -> > 5.5.8. I believe the port maintainer has also incorporated a fix into the > FreeBSD ports. I all ready did that twice. I completely removed Dovecot before reinstalling it the second time. The prolem still exists. In addition, I am using th version of MySQL that the "port maintainer" supposed fixed. I guess I will have no choice but to return to the older MySQL version. I would be interrested todiscoverif this problem is isolated strictly to FreeBSD + MySQL 5.5.8 however. -- Jerry
Re: [Dovecot] Dovecot fails after updating MySQL
The problem is in new buggy MySQL client. I wrote to this list before about it. Roll back to previous version 5.5.7 for a while (server may stills 5.5.8). --- Maxim 11.01.2011 2:19 пользователь "Jerry" написал: > > I just updated MySQL to Server version: 5.5.8 on my FreeBSD-8.2 system. > Now Dovecot refuses to run. Prior to this, dovecot had been running for several > years without a problem. > > This is the output of "dovecot -n" > > # 1.2.16: /usr/local/etc/dovecot.conf > # OS: FreeBSD 8.2-PRERELEASE amd64 ufs > log_path: /var/log/dovecot.log > login_dir: /var/run/dovecot/login > login_executable: /usr/local/libexec/dovecot/imap-login > verbose_proctitle: yes > first_valid_uid: 1000 > first_valid_gid: 1000 > mail_privileged_group: mail > mail_location: maildir:/var/mail/vhost/seibercom.net/gerard > mail_plugins: expire > imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep > lda: > postmaster_address: postmas...@seibercom.net > mail_plugins: sieve > sieve_global_path: /usr/local/etc/dovecot/sieve/gerard.sieve > sendmail_path: /usr/sbin/sendmail > auth default: > mechanisms: plain login digest-md5 cram-md5 > username_format: %Lu > verbose: yes > debug: yes > debug_passwords: yes > passdb: >driver: sql >args: /usr/local/etc/dovecot-sql.conf > userdb: >driver: sql >args: /usr/local/etc/dovecot-sql.conf > socket: >type: listen >client: > path: /var/run/dovecot/auth-client > mode: 432 >master: > path: /var/run/dovecot/auth-master > mode: 384 > user: vmail > group: vmail > plugin: > expire: Trash 2 Spam/* 2 > expire_dict: proxy::expire > dict: > expire: mysql:/usr/local/etc/dovecot-dict-expire.conf > > The /var/run/dovecot directory looks like this: > > drwxr-xr-x 3 root wheel 512B 2011-01-10 18:49:44 EST ./ > drwxr-xr-x 15 root wheel 1.0K 2011-01-10 18:49:37 EST ../ > srw-rw 1 root wheel 0B 2011-01-10 18:49:37 EST auth-client= > srw--- 1 vmail vmail 0B 2011-01-10 18:49:37 EST auth-master= > srw--- 1 root wheel 0B 2011-01-10 18:49:37 EST auth-worker.34781= > srwxrwxrwx 1 root wheel 0B 2011-01-10 18:49:37 EST dict-server= > lrwx-- 1 root wheel 27B 2011-01-10 18:49:37 EST > dovecot.conf@ -> /usr/local/etc/dovecot.conf > drwxr-x--- 2 root dovecot 512B 2011-01-10 18:49:37 EST login/ > -rw--- 1 root wheel 6B 2011-01-10 18:49:37 EST master.pid > > This is the log file output, updated every second (snippet) > > Jan 10 18:42:11 dovecot: Info: Dovecot v1.2.16 starting up > Jan 10 18:42:11 dovecot: Error: child 34517 (auth-worker) killed with > signal 11 (core not dumped) > Jan 10 18:42:11 dovecot: Error: child 34521 (auth-worker) killed with > signal 11 (core not dumped) > > I have tried deleting and rebuilding dovecot without success. I am at a > lose to figure out what the problem is. > > -- > Jerry ✌ > dovecot.u...@seibercom.net > > Disclaimer: off-list followups get on-list replies or get ignored. > Please do not ignore the Reply-To header. > __ > I would rather say that a desire to drive fast > sports cars is what sets man apart from the animals.
[Dovecot] Connection queue full on my directors
I finally upgraded to v1.2.16 on my backend servers, with ldap instead of
previously mysql, and put a couple of dovecot v2.0.8 directors in front
of them (used haproxy previously). It seemed to work OK initially, but
after a few hours we got bit by "Connection queue full" problems on the
directors.
So I now set default_process_limit=512 and also:
service anvil {
client_limit=1027
}
since dovecot said that was now required. Things seems to be working,
but I'm afraid default_process_limit=512 is too low:
$ ps -ef|grep dovecot/pop3-login|wc -l
192
$ ps -ef|grep dovecot/imap-login|wc -l
472
so looks like I'm quite close to hitting this limit for my imap logins.
We will eventually put up some webmail servers (using imapproxy to keep
connections alive), that will be connecting over these directors. Then
we will expect to have a lot more active imap sessions over these
directors. Should we just keep increasing default_process_limit, or per
service process_limit, and follow dovecots warnings about client_limits for
auth/anvil.. or will we be getting into other problems like running out
of file descriptors? Are there any max'es we should expect to run into ?
Current director config:
###
$ ../../sbin/dovecot -n
# 2.0.8: /usr/local/dovecot-2.0.8/etc/dovecot/dovecot.conf
# OS: Linux 2.6.18-194.32.1.el5 x86_64 Red Hat Enterprise Linux Server release
5.5 (Tikanga)
default_process_limit = 256
director_mail_servers = 192.168.42.7 192.168.42.8 192.168.42.9 192.168.42.10
192.168.42.11 192.168.42.28 192.168.42.29
director_servers = 192.168.42.15 192.168.42.17
disable_plaintext_auth = no
listen = *
passdb {
args = proxy=y nopassword=y
driver = static
}
service director {
fifo_listener login/proxy-notify {
mode = 0666
}
inet_listener {
port = 5515
}
unix_listener director-userdb {
mode = 0600
}
unix_listener login/director {
mode = 0666
}
}
service imap-login {
executable = imap-login director
}
service pop3-login {
executable = pop3-login director
}
ssl_cert =
