[Dovecot] cluster with dsync mirror
I have an idea for running a pair of redundant dovecot mail servers that may be odd but it might work. I'm interested in any thoughts on the topic. Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other dedicated NFS server in a simple environment with a limited number of users. Everything else about the systems could be identical. Both could receive mail using Postfix with dovecot LDA. Thank you. Bryan
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On Aug 15, 2010, at 4:01 PM, Marc Perkel wrote: > Seems to me that it wouldn't take a lot of code to at lease find if they have > adduser or useradd. Or in the case of OS X, dscl... Documenting this is good, but perhaps the configure script could check if the user exists, and instruct the user to create this manually before going any further?
Re: [Dovecot] Master User Features I'd like to see
On 8/15/2010 5:07 PM, Bradley Giesbrecht wrote:
On Aug 15, 2010, at 4:56 PM, Marc Perkel wrote:
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the
master passdb and when doing so the variable %u is the master user.
I assume that %n and %d also represent the name and domain part of
the master user.
Yes.
What I need is to also be able to have variables for the loginuser
passed to the master user query. Something like %lu, %ln, and %ld
perhaps. That way with MySQL tricks I might be able to see if the
master user is master for that particular login user. That way I
can give domain owners or owners of multiple domains the ability to
manage the email accounts within their scope of permission.
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Further testing shows %{login_domain} returns an empty string.
What was your test? Mysql query log?
Did you add them as '%{login_user}' or '%login_user'?
ChangeLog has:
* src/auth/auth-request.c:
auth: Added %{login_user}, %{login_username} and %{login_domain}
variables that are set for master logins.
[5ae4a5c14f5b]
// Brad
The query is:
password_query = SELECT user_name, domain_name, password FROM users
WHERE user_name = '%n' AND domain_name = '%d' AND owns_domain='1' AND
'%d'='%{login_domain}'
Re: [Dovecot] Master User Features I'd like to see
On Aug 15, 2010, at 4:56 PM, Marc Perkel wrote:
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the
master passdb and when doing so the variable %u is the master
user. I assume that %n and %d also represent the name and domain
part of the master user.
Yes.
What I need is to also be able to have variables for the loginuser
passed to the master user query. Something like %lu, %ln, and %ld
perhaps. That way with MySQL tricks I might be able to see if the
master user is master for that particular login user. That way I
can give domain owners or owners of multiple domains the ability
to manage the email accounts within their scope of permission.
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Further testing shows %{login_domain} returns an empty string.
What was your test? Mysql query log?
Did you add them as '%{login_user}' or '%login_user'?
ChangeLog has:
* src/auth/auth-request.c:
auth: Added %{login_user}, %{login_username} and %{login_domain}
variables that are set for master logins.
[5ae4a5c14f5b]
// Brad
Re: [Dovecot] Master User Features I'd like to see
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the master passdb
and when doing so the variable %u is the master user. I assume that %n and %d
also represent the name and domain part of the master user.
Yes.
What I need is to also be able to have variables for the loginuser passed to
the master user query. Something like %lu, %ln, and %ld perhaps. That way with
MySQL tricks I might be able to see if the master user is master for that
particular login user. That way I can give domain owners or owners of multiple
domains the ability to manage the email accounts within their scope of
permission.
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Further testing shows %{login_domain} returns an empty string.
Re: [Dovecot] Master User Features I'd like to see
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the master passdb
and when doing so the variable %u is the master user. I assume that %n and %d
also represent the name and domain part of the master user.
Yes.
What I need is to also be able to have variables for the loginuser passed to
the master user query. Something like %lu, %ln, and %ld perhaps. That way with
MySQL tricks I might be able to see if the master user is master for that
particular login user. That way I can give domain owners or owners of multiple
domains the ability to manage the email accounts within their scope of
permission.
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Hi Timo,
I don't think it's working. I tried this query:
password_query = SELECT user_name, domain_name, password FROM users
WHERE user_name = '%n' AND domain_name = '%d' AND owns_domain='1' AND
'%d'='%{login_domain}'
It didn't work. However this did:
password_query = SELECT user_name, domain_name, password FROM users
WHERE user_name = '%n' AND domain_name = '%d' AND owns_domain='1'
But that doesn't test the '%d'='%{login_domain}' part.
Am I missing something.
I should have been testing 2.0 earlier.
Re: [Dovecot] dovecot 2.0 convert script
On 8/15/2010 3:34 PM, Noel Butler wrote: On Sun, 2010-08-15 at 14:06 -0700, Marc Perkel wrote: Since my old config had this: protocols = imap imaps pop3 pop3s ssl_cert_file = /usr/share/ssl/certs/imapd.pem ssl_key_file = /usr/share/ssl/certs/imapd.pem then the convert script should have added ssl = yes Just trying to document all the little issues as I find them. which rc? rc6
Re: [Dovecot] Master User Features I'd like to see
On 8/15/2010 3:06 PM, Timo Sirainen wrote:
On 15.8.2010, at 22.46, Marc Perkel wrote:
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
..
I'm assuming that the masteruser and masterpass is passed to the master passdb
and when doing so the variable %u is the master user. I assume that %n and %d
also represent the name and domain part of the master user.
Yes.
What I need is to also be able to have variables for the loginuser passed to
the master user query. Something like %lu, %ln, and %ld perhaps. That way with
MySQL tricks I might be able to see if the master user is master for that
particular login user. That way I can give domain owners or owners of multiple
domains the ability to manage the email accounts within their scope of
permission.
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Yeah - let us know where. I'm having a hard time finding the normal
variables documented. I'll see if I can use this and get something working.
Re: [Dovecot] dovecot 2.0 convert script
On Sun, 2010-08-15 at 14:06 -0700, Marc Perkel wrote: > Since my old config had this: > > protocols = imap imaps pop3 pop3s > > ssl_cert_file = /usr/share/ssl/certs/imapd.pem > ssl_key_file = /usr/share/ssl/certs/imapd.pem > > then the convert script should have added > > ssl = yes > > Just trying to document all the little issues as I find them. > which rc?
Re: [Dovecot] Address book for 2.0?
On 2010-08-15 18:07:07 -0400, Jerrale G wrote: > 2.0 could include a directory service, like MS Exchange, where > people's address books within IMAP clients could be stored on the > server and retrievable by the clients. Its a headache for users to > roam from pc to pc and not have someone's address stored locally on > another. you could allow people to store their contacts in ldap. and a quick google search for "imap contacts" brought up this http://lifehacker.com/239054/geek-to-live--sync-your-address-book-via-imap darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] dovecot 2.0 convert script
On 15.8.2010, at 22.06, Marc Perkel wrote: > protocols = imap imaps pop3 pop3s > > ssl_cert_file = /usr/share/ssl/certs/imapd.pem > ssl_key_file = /usr/share/ssl/certs/imapd.pem > > then the convert script should have added > > ssl = yes That's the default. Or was it set to "no" in your conversion?
[Dovecot] Address book for 2.0?
2.0 could include a directory service, like MS Exchange, where people's address books within IMAP clients could be stored on the server and retrievable by the clients. Its a headache for users to roam from pc to pc and not have someone's address stored locally on another. Jerrale G SC Senior Admin
Re: [Dovecot] Master User Features I'd like to see
On 15.8.2010, at 22.46, Marc Perkel wrote:
> passdb {
> driver = sql
> args = /etc/dovecot/dovecot-sql-master.conf.ext
> master = yes
> pass = yes
> }
..
> I'm assuming that the masteruser and masterpass is passed to the master
> passdb and when doing so the variable %u is the master user. I assume that
> %n and %d also represent the name and domain part of the master user.
Yes.
> What I need is to also be able to have variables for the loginuser passed to
> the master user query. Something like %lu, %ln, and %ld perhaps. That way
> with MySQL tricks I might be able to see if the master user is master for
> that particular login user. That way I can give domain owners or owners of
> multiple domains the ability to manage the email accounts within their scope
> of permission.
These are available in v2.0:
%{login_user}
%{login_username}
%{login_domain}
I guess they should be added to wiki..
Re: [Dovecot] Master User Features I'd like to see
On 8/15/2010 5:46 PM, Marc Perkel wrote:
Here's what I'd like. Limited master users, where someone can be a
master users for some domains but not others. I think I could do what
I want with the right kinds of variable passing that doesn't yet
exist. Let me see if I can explain clearly.
From the example in the wiki:
auth_master_user_separator = *
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
userdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
Login looks like this:
# telnet localhost 143
* OK Dovecot ready.
1 login loginuser*masteruser masterpass
1 OK Logged in.
I'm assuming that the masteruser and masterpass is passed to the
master passdb and when doing so the variable %u is the master user. I
assume that %n and %d also represent the name and domain part of the
master user.
What I need is to also be able to have variables for the loginuser
passed to the master user query. Something like %lu, %ln, and %ld
perhaps. That way with MySQL tricks I might be able to see if the
master user is master for that particular login user. That way I can
give domain owners or owners of multiple domains the ability to manage
the email accounts within their scope of permission.
YES, lets make an administrative tool for dovecot supporting multiple
domains administrated by various user. Oh, wait! There's vpopmail :-S
Jerrale G.
SC Senior Admin
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 5:49 PM, Marc Perkel wrote: On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named "dovenull" to work. Please create user "dovenull" and try again. I agree its not as simple as people would think but, if dovecot would log everything relevant, dovecot could use its own logs to know what environment it is within. Jerrale G. SC Senior Admin
[Dovecot] dovecot: Killed with signal 15 (by pid=14267
I don't know if dovecot 2.0 will have this already or not but, when dovecot is stopped or started, it would be nice to have the PID reported in the log for various uses. Jerrale Gayle SC Senior Admin
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 2:32 PM, Marcus Rueckert wrote: On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix Perhaps a better error message that says something like: Dovecot needs a user named "dovenull" to work. Please create user "dovenull" and try again.
[Dovecot] Master User Features I'd like to see
Here's what I'd like. Limited master users, where someone can be a
master users for some domains but not others. I think I could do what I
want with the right kinds of variable passing that doesn't yet exist.
Let me see if I can explain clearly.
From the example in the wiki:
auth_master_user_separator = *
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql-master.conf.ext
master = yes
pass = yes
}
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
userdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf.ext
}
Login looks like this:
# telnet localhost 143
* OK Dovecot ready.
1 login loginuser*masteruser masterpass
1 OK Logged in.
I'm assuming that the masteruser and masterpass is passed to the master
passdb and when doing so the variable %u is the master user. I assume
that %n and %d also represent the name and domain part of the master user.
What I need is to also be able to have variables for the loginuser
passed to the master user query. Something like %lu, %ln, and %ld
perhaps. That way with MySQL tricks I might be able to see if the master
user is master for that particular login user. That way I can give
domain owners or owners of multiple domains the ability to manage the
email accounts within their scope of permission.
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-15 14:01:25 -0700, Marc Perkel wrote: > Seems to me that it wouldn't take a lot of code to at lease find if > they have adduser or useradd. that is 2 out of many solutions. and depending of the admin he might create the user in an ldap tree or a nis server. also packager dont really like users created from the buildsystem. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
[Dovecot] dovecot 2.0 convert script
Since my old config had this: protocols = imap imaps pop3 pop3s ssl_cert_file = /usr/share/ssl/certs/imapd.pem ssl_key_file = /usr/share/ssl/certs/imapd.pem then the convert script should have added ssl = yes Just trying to document all the little issues as I find them.
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 9:58 AM, Marcus Rueckert wrote: On 2010-08-15 09:44:49 -0700, Marc Perkel wrote: might want to automatically add dovenull to the install script if possible. Perhaps a better error message than the one above that indicates the solution is to create the dovenull user. I dont think you can know all the different tools distros use to create users. (adduser vs useradd e.g.) so documenting this is the better approach. darix Seems to me that it wouldn't take a lot of code to at lease find if they have adduser or useradd.
Re: [Dovecot] Forcing users to change passwords
On 08/15/2010 12:58 PM, Marc Perkel wrote: Suppose I have users with a default password like "change-my-password" and I want to detect users who haven't changed their password and alert (nag) them about changing it. How would I do that? Write a script that checks your user/password database for that password, and sends an email to those users. If your passwords are hashed, you can create a new user with "change-my-password" as its password and check the DB to see what that hashes to.
[Dovecot] Forcing users to change passwords
Suppose I have users with a default password like "change-my-password" and I want to detect users who haven't changed their password and alert (nag) them about changing it. How would I do that?
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 2010-08-15 09:44:49 -0700, Marc Perkel wrote: > might want to automatically add dovenull to the install script if > possible. Perhaps a better error message than the one above that > indicates the solution is to create the dovenull user. I dont think you can know all the different tools distros use to create users. (adduser vs useradd e.g.) so documenting this is the better approach. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 8/15/2010 9:10 AM, Timo Sirainen wrote: On 15.8.2010, at 17.03, Marc Perkel wrote: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary. I added now to http://wiki2.dovecot.org/Upgrading/2.0 : - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. might want to automatically add dovenull to the install script if possible. Perhaps a better error message than the one above that indicates the solution is to create the dovenull user. Everything seems to be working. Is there a "what's new" feature list anywhere? Anything cool I might want to try?
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 15/08/2010 17:14, Dennis Clarke wrote: On 15.8.2010, at 17.03, Marc Perkel wrote: Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary. I added now to http://wiki2.dovecot.org/Upgrading/2.0 : - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting. Dovecot 2.x seems to be very close to release grade. Could you provide a guess as to when it will be released so that I can plan downtime for the upgrade on my production servers? See Timo's comment of Friday 13/08/2010 19:29: http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc6.tar.gz.sig I expect this to be the last release candidate. Unless release critical bugs are reported, I'll update the version number to v2.0.0 on Monday morning without any other changes. Since rc5 there have been mainly some small fixes and some error message improvements. The only (somewhat) important fixes are: - dict quota didn't always decrease quota when messages were expunged - Shared INBOX wasn't always listed with FS layout "I'll update the version number to v2.0.0 on Monday morning" Bill
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
> On 15.8.2010, at 17.03, Marc Perkel wrote: > >> Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: >> dovenull >> >> Just some real time feedback. I don't know what dovenull user is or why >> it is necessary. > > I added now to http://wiki2.dovecot.org/Upgrading/2.0 : > > - Dovecot uses two internal users now by default: dovenull and dovecot. > You need to create the dovenull user or change default_login_user > setting. > Dovecot 2.x seems to be very close to release grade. Could you provide a guess as to when it will be released so that I can plan downtime for the upgrade on my production servers? -- Dennis Clarke dcla...@opensolaris.ca <- Email related to the open source Solaris dcla...@blastwave.org <- Email related to open source for Solaris
Re: [Dovecot] Upgrade to 2.0 - Not so smooth
On 15.8.2010, at 17.03, Marc Perkel wrote: > Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull > > Just some real time feedback. I don't know what dovenull user is or why it is > necessary. I added now to http://wiki2.dovecot.org/Upgrading/2.0 : - Dovecot uses two internal users now by default: dovenull and dovecot. You need to create the dovenull user or change default_login_user setting.
[Dovecot] Upgrade to 2.0 - Not so smooth
Starting Dovecot Imap: Fatal: service(pop3-login) User doesn't exist: dovenull Just some real time feedback. I don't know what dovenull user is or why it is necessary.
Re: [Dovecot] \" character in folder name results in strange LIST
On 08/15/2010 02:24 PM, Timo Sirainen wrote: > On 15.8.2010, at 7.54, Samuel Kvasnica wrote: > >> 12 subscribe "Trash/aaa/" >> 12 NO Invalid mailbox name: Trash/aaa/ <=== non-existing child folder, >> ERROR >> 13 unsubscribe "aaa/" >> 13 NO Invalid mailbox name: aaa/ <=== non-existing child folder, ERROR > Set: > > imap_client_workarounds = tb-extra-mailbox-sep > just swapped shortly back to non-fs maildir layout for a test - that one works normally. So there must be a bug in layout=fs implementation, it is listing the parent directory as child !
Re: [Dovecot] \" character in folder name results in strange LIST
On 08/15/2010 02:24 PM, Timo Sirainen wrote: > On 15.8.2010, at 7.54, Samuel Kvasnica wrote: > >> 12 subscribe "Trash/aaa/" >> 12 NO Invalid mailbox name: Trash/aaa/ <=== non-existing child folder, >> ERROR >> 13 unsubscribe "aaa/" >> 13 NO Invalid mailbox name: aaa/ <=== non-existing child folder, ERROR > Set: > > imap_client_workarounds = tb-extra-mailbox-sep > no, that does not help at all (and I'm using maildir, not mbox). The problem is the LIST command for "aaa/*" lists not only the children of "aaa" but also the parent folder "aaa" itself which confuses the client which is trying to move/resubcribe all children as well. This got broken either with v2.0 or with my change to LAYOUT=fs.
Re: [Dovecot] \" character in folder name results in strange LIST
On 15.8.2010, at 7.54, Samuel Kvasnica wrote: > 12 subscribe "Trash/aaa/" > 12 NO Invalid mailbox name: Trash/aaa/ <=== non-existing child folder, > ERROR > 13 unsubscribe "aaa/" > 13 NO Invalid mailbox name: aaa/ <=== non-existing child folder, ERROR Set: imap_client_workarounds = tb-extra-mailbox-sep
Re: [Dovecot] turn Usernames in Lowercase
Hi again, I solved the issue. Thanks any way and excuse the noise. http://wiki.dovecot.org/Variables Regards Hi, I'm just curious how to force usernames to be modified to lowercase letters if one mixes uper and lower case letters to one salad? Cause my SpamAssassin gets confuesd and treats different spellings of Usernames as different Users - which is uncool. I've heard about something you can add in your dovecot.config to enforce lowercase letters only. Thanks
[Dovecot] turn Usernames in Lowercase
Hi, I'm just curious how to force usernames to be modified to lowercase letters if one mixes uper and lower case letters to one salad? Cause my SpamAssassin gets confuesd and treats different spellings of Usernames as different Users - which is uncool. I've heard about something you can add in your dovecot.config to enforce lowercase letters only. Thanks
