[Dovecot] More than one inbox possible ?
I wanted to know if more than one INBOX - entry is possible. My situation: Three users with [EMAIL PROTECTED] One Mail-Adress [EMAIL PROTECTED], where all three users can get the mails. But i dont want to copy the mails from office to the user (like mailinglist), because if one reads a new mail it should be marked as read at all users. Same with answered and deleted. Thanks in advance, Christian
[Dovecot] Quota per domain
Hi People I have a two question I use dovecot 1.0.10 I have quota maildir 1- I want to use the last version of quota 1.1 in my dovecot , i have to patch then, so which file i have to apply ? http://dovecot.org/patches/1.0/ this one quota-rewrite-1.0.9.diff ??? When i using the original version with out quota new 1.1 , in my mailbox is created a file called maildirsize with the quota , but when a apply the patch the quota this stop work for me. 2- if is posible define a quota per domain? [EMAIL PROTECTED] = 100M [EMAIL PROTECTED] = 0 --- no limit quota or @domain1.com = 100M @domain2.com = 0 --- no limit quota Once again , sorry for my english Thanks
Re: [Dovecot] deliver can't connect to auth server at */usr/local*/var/run/dovecot/auth-master
Message: 8
Date: Tue, 15 Jan 2008 15:19:11 +0100
From: Andreas Ntaflos <[EMAIL PROTECTED]>
Subject: Re: [Dovecot] deliver can't connect to auth server at
*/usr/local*/var/run/dovecot/auth-master
To: dovecot@dovecot.org
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="utf-8"
On Tuesday 15 January 2008 03:56:28 Jerry Yeager wrote:
while fiddling around with the configuration so Dovecot's LDA
"deliver" can be
used by multiple users by means of Getmail (you can read about that
in [1]) I
always end up running into the error message posted in the subject
line:
( stuff snipped out )
One last thing, as a security idea, try something like
master {
path = /usr/local/var/run/dovecot/auth-master
mode = 0600
user = dovecot_user
group = dovecot_group
}
and set your postfix line that calls deliver to match:
dovecot unix - n n - - pipe flags=DRhu
user=dovecot_user:dovecot_group argv=/usr/local/libexec/dovecot/
deliver -f ${sender} -d ${recipient}
Thanks for this suggestion! But that would imply that I have a
virtual user
setup, wouldn't it? Because I don't, all my users are regular Unix
users with
shell accounts. That's why my Postfix main.cf contains just
home_mailbox = Maildir/
mailbox_command = /usr/local/libexec/dovecot/deliver
which is also what the LDA/Postfix wiki page says on
wiki.dovecot.org. No
Dovecot entry in master.cf at all.
Actually I was responding to what you had listed in your message i.e.
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 432
user: postfix
group: postfix
master:
path: /var/run/dovecot/auth-master
mode: 432
user: root
group: dovecot
--
which is a setup type you would use in a virtual style of user (either
a "super user" or a group of non-system listed users with different
uids / gids) setup .
I had not encountered your other postings until later.
Jerry
And, as also mentioned elsewhere in this thread, until yesterday I
didn't even
have the master { ... } section uncommented, and no auth-master
socket seems
to have been configured. But then again I only delivered through
Postfix and
didn't need to have deliver called by a regular user.
Andreas
--
Andreas "daff" Ntaflos
Vienna, Austria
GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4
-- next part --
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
Url :
http://dovecot.org/pipermail/dovecot/attachments/20080115/33439c1a/attachment.bin
--
___
dovecot mailing list
dovecot@dovecot.org
http://dovecot.org/cgi-bin/mailman/listinfo/dovecot
End of dovecot Digest, Vol 57, Issue 46
***
smime.p7s
Description: S/MIME cryptographic signature
Re: [Dovecot] Keep pop messages, is it possible?
Thanks for the answer Bill! I see this a behavior as a good feature, seems like gmail just mark the message as read when you download if via pop and the pop server consider this information at the time to serve clients, it looks a pretty clean solution for me. I do agree that this is probably not compliant with pop3 protocol, but, sometimes you can break a RFC to serve a good service and sometimes a RFC is rewrited to agree with a good new feature (have a look in SIP evolution). I will try to do a plugin for that when I have time! Thanks! That's almost always correct: normal client-based POP3 server retention is entirely dependent on clients that keep track of what messages they have or have not downloaded, and some POP3 servers also maintain a Status header so that multiple clients can look at the same message and know whether another client has already read it. GMail goes a bit further, in a somewhat useful fashion. Their POP3 server acts mostly like an auto-deleting server: once a message has been retrieved by POP3, it will not be seen on later POP3 sessions, even though it is retained in the GMail Inbox. Mail deleted by a POP3 or IMAP client is removed from the Inbox, but remains in the "All Mail" dump as well as in whatever labelled collection it is in. Frankly, that behavior is positively weird and arguably dysfunctional from a POP3 perspective, but then POP3 really isn't designed with a server-based persistent mailstore in mind. It is my understanding that there is widespread principled aversion to the Status header (which is understandable) so that's likely not to happen for Dovecot. The GMail message hiding for POP3 seems to me like a recipe for disaster for anyone not willing to provide essentially unlimited permanent storage for mail, since it effectively hides mail from POP3 users without deleting it.
Re: [Dovecot] Keep pop messages, is it possible?
At 8:23 PM -0800 1/14/08, Jeff Grossman wrote: Fábio M. Catunda wrote: Hi! I would like to find a way to not delete messages when they are downloaded via pop3, is that possible with dovecot? Gmail do this, I dont know how they mark messages that have been downloaded to avoid clients to download it again, but it looks like a good resource! Thanks for the help! That is a feature of the client. Most clients have a setting which says "Keep Messages On Server". That's almost always correct: normal client-based POP3 server retention is entirely dependent on clients that keep track of what messages they have or have not downloaded, and some POP3 servers also maintain a Status header so that multiple clients can look at the same message and know whether another client has already read it. GMail goes a bit further, in a somewhat useful fashion. Their POP3 server acts mostly like an auto-deleting server: once a message has been retrieved by POP3, it will not be seen on later POP3 sessions, even though it is retained in the GMail Inbox. Mail deleted by a POP3 or IMAP client is removed from the Inbox, but remains in the "All Mail" dump as well as in whatever labelled collection it is in. Frankly, that behavior is positively weird and arguably dysfunctional from a POP3 perspective, but then POP3 really isn't designed with a server-based persistent mailstore in mind. It is my understanding that there is widespread principled aversion to the Status header (which is understandable) so that's likely not to happen for Dovecot. The GMail message hiding for POP3 seems to me like a recipe for disaster for anyone not willing to provide essentially unlimited permanent storage for mail, since it effectively hides mail from POP3 users without deleting it. -- Bill Cole [EMAIL PROTECTED]
Re: [Dovecot] deliver can't connect to auth server at */usr/local*/var/run/dovecot/auth-master
Andreas Ntaflos wrote:
On Tuesday 15 January 2008 05:24:58 Timo Sirainen wrote:
On Tue, 2008-01-15 at 00:21 +0100, Andreas Ntaflos wrote:
Notice how it says "/usr/local/var/run/dovecot"! How and why does dovecot
..
master:
path: /var/run/dovecot/auth-master
If you're not using the default built-in path, set:
protocol lda {
auth_socket_path = /var/run/dovecot/auth-master
}
Thanks for your reply, too!
So does this mean that auth_socket_path is by default set
to /usr/local/var/run/dovecot/auth-master? And I have to set that parameter
explicitly to /var/run/dovecot/auth-master?
I am a little confused. Why are there two places to set the path to the
authentication master socket?
- you need to tell the server where to listen
- you need to tell deliver where to find the socket
the --prefix is probably what added the /usr/local to the default
/var/run/
Do I need to set both? Until yesterday, when I
started experimenting, I hadn't even uncommented the "master { ... }" section
under "socket listen { ... }", I just used the client so Postfix could do
SMTP authentication lookups, as you can see from dovecot -n.
Andreas
P.S.: As you could probably tell some messages from this list bounced from my
mailserver when I tried to get the configuration right (which I didn't :)). I
apologise for that.
Re: [Dovecot] deliver can't connect to auth server a t */usr/local*/var/run/dovecot/auth-master
On Tuesday 15 January 2008 03:00:50 Charles Marcus wrote: > On 1/14/2008 Andreas Ntaflos wrote: > > Notice how it says "/usr/local/var/run/dovecot"! How and why does > > dovecot > > ^^ > > think that anything of any importance can be found under > > /usr/local/var/... ? > > I'm confused as to why *you're* confused... > > Look at the output again... > > ALL of your binaries paths are set to: > > /usr/local/var/... Thanks for your reply! But I think you misread that, not a single parameter is set to /usr/local/var. The installation prefix (configure --prefix) is set to /usr/local but the local state directory, which is supposed to be /var is really set to /var (this is also the default when running configure). The configuration also specified that Dovecot run out of /var/run/dovecot (base_dir). So naturally I had no idea where Dovecot would take that /usr/local prefix to the /var directory, and I really still don't. Andreas -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4 signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] deliver can't connect to auth server at */usr/local*/var/run/dovecot/auth-master
On Tuesday 15 January 2008 03:56:28 Jerry Yeager wrote:
> > while fiddling around with the configuration so Dovecot's LDA
> > "deliver" can be
> > used by multiple users by means of Getmail (you can read about that
> > in [1]) I
> > always end up running into the error message posted in the subject
> > line:
> >
> > Jan 15 00:00:02 HOSTNAME deliver(USERID): Can't connect to auth server
> > at /usr/local/var/run/dovecot/auth-master: Permission denied
> >
> > Notice how it says "/usr/local/var/run/dovecot"! How and why does
> > dovecot
> >^^
> > think that anything of any importance can be found under /usr/local/
> > var/... ?
> > Please see dovecot -n at the end of this message, but as far as I
> > can tell I
> >
> >master:
> > path: /var/run/dovecot/auth-master
> > mode: 432
> > user: root
> > group: dovecot
>
> For the quick answer to your immediate problem / question, try:
>
> cd /path/to/dovecot's/deliver (probably
> /usr/local/libexec/dovecot/ )
>
> chmod u+s deliver
>
> (enable the setuid bit for the deliver app). Your Getmail app may not
> be truly running as root and thus does not really have permission to
> do what you want.
>
> you may need to do the same for the group as well
Thank you as well for the reply! :)
Chmod'ing deliver really was a step forward in the right direction, although,
as I mentioned elsewhere in this thread, I did not quite get the
configuration right so a few messages from this and other mailing lists
bounced because deliver wasn't called correctly. Still trying to figure that
out.
> Unix permissions are weird sometimes, like a $100 television tube that
> protects a 50 cent fuse by blowing first.
Really great analogy :) I never had a problem with understanding Unix
permissions, but things seem to get complicated when you try to make
different parts of a mail system running smoothly together.
> It does look like (from your use of /usr/local/*) you built
> dovecot to run out of /usr/local.
No, I really didn't (as far as I can tell). The installation prefix
is /usr/local, yes, but Dovecot runs out of /var/run/dovecot. But apparently
the auth_socket_path for protocol lda defaults to /usr/local/var/run/dovecot,
a parameter I'm still not sure what I need it for.
> One last thing, as a security idea, try something like
>
> master {
> path = /usr/local/var/run/dovecot/auth-master
> mode = 0600
> user = dovecot_user
> group = dovecot_group
> }
>
> and set your postfix line that calls deliver to match:
>
> dovecot unix - n n - - pipe flags=DRhu
> user=dovecot_user:dovecot_group argv=/usr/local/libexec/dovecot/
> deliver -f ${sender} -d ${recipient}
Thanks for this suggestion! But that would imply that I have a virtual user
setup, wouldn't it? Because I don't, all my users are regular Unix users with
shell accounts. That's why my Postfix main.cf contains just
home_mailbox = Maildir/
mailbox_command = /usr/local/libexec/dovecot/deliver
which is also what the LDA/Postfix wiki page says on wiki.dovecot.org. No
Dovecot entry in master.cf at all.
And, as also mentioned elsewhere in this thread, until yesterday I didn't even
have the master { ... } section uncommented, and no auth-master socket seems
to have been configured. But then again I only delivered through Postfix and
didn't need to have deliver called by a regular user.
Andreas
--
Andreas "daff" Ntaflos
Vienna, Austria
GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4
signature.asc
Description: This is a digitally signed message part.
Re: [Dovecot] deliver can't connect to auth server at * /usr/local*/var/run/dovecot/auth-master
On Tuesday 15 January 2008 05:24:58 Timo Sirainen wrote:
> On Tue, 2008-01-15 at 00:21 +0100, Andreas Ntaflos wrote:
> > Notice how it says "/usr/local/var/run/dovecot"! How and why does dovecot
>
> ..
>
> > master:
> > path: /var/run/dovecot/auth-master
>
> If you're not using the default built-in path, set:
>
> protocol lda {
> auth_socket_path = /var/run/dovecot/auth-master
> }
Thanks for your reply, too!
So does this mean that auth_socket_path is by default set
to /usr/local/var/run/dovecot/auth-master? And I have to set that parameter
explicitly to /var/run/dovecot/auth-master?
I am a little confused. Why are there two places to set the path to the
authentication master socket? Do I need to set both? Until yesterday, when I
started experimenting, I hadn't even uncommented the "master { ... }" section
under "socket listen { ... }", I just used the client so Postfix could do
SMTP authentication lookups, as you can see from dovecot -n.
Andreas
P.S.: As you could probably tell some messages from this list bounced from my
mailserver when I tried to get the configuration right (which I didn't :)). I
apologise for that.
--
Andreas "daff" Ntaflos
Vienna, Austria
GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4
signature.asc
Description: This is a digitally signed message part.
Re: [Dovecot] Dovecot With cygwin
I googled around web and found http://www.dovecot.org/list/dovecot/2004-December/005665.html by Johannes Berg that has a patch for dovecot + cygwin. but that does not work. Does anybody successfully compiled and running dovecot on windows XP + cygwin 5.1. Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs
[Dovecot] Out of memory [repost as a new thread]
Hi, this happens since a few days on a Gentoo hardened system using a grsecurity enabled kernel running Dovecot 1.0.10, only to 2 of 10 users though: --8<-- kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537325568 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537321472 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537456640 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537321472 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 dovecot: IMAP(info): block_alloc(): Out of memory dovecot: child 15708 (imap) returned error 83 (Out of memory) --8<-- grsecurity only logs the attempted resource overstep. I already increased mail_process_size to 512M and deleted the index.cache* files inside the users maildir -- didn't help :/ Any idea why this is happening or how I could find out? TIA :) -- Regards, Wolfram Schlich <[EMAIL PROTECTED]> Gentoo Linux * http://dev.gentoo.org/~wschlich/
Re: [Dovecot] Using deliver from Getmail?
Andreas Ntaflos wrote: On Monday 14 January 2008 22:15:48 mouss wrote: Andreas Ntaflos wrote: On Monday 14 January 2008 18:47:27 Evaggelos Balaskas wrote: This is part of my getmailrc [destination] type = MDA_external path = /usr/local/libexec/dovecot/deliver user = ebal group = mail arguments = ( '-d', 'ebal' ) i use getmail + dovecot + sieve + spamassassin [filter getmail] at all of my accounts. I can't seem to be too far off with my configuration, but it's just not working yet. Your user "ebal" is part of the group "mail", I gather? I don't think this matters. he runs deliver as the user who owns the mailbox (see -d argument). Does that mean that one, and only one, user may be running deliver manually (or from Getmail) to get his mail? This would make it quite impossible for a server with multiple real system users to use Getmail and deliver mail via Dovecot's LDA, wouldn't it? it does not mean that. some people use a single uid:gid for their mailstore. thus a single user is used to deliver all mail. Others use different uid:gid for mailboxes. If this is your case, then some work is needed. one possibility is suid. check the wiki. Or am I not seeing the obvious solution to this problem?
Re: [Dovecot] Out of memory
Argh, I broke threading by forgetting to remove the In-Reply-To: header which was set automatically by mutt because I was using list-reply in order to circumvent having to type the dovecot mailing list address in by hand. Sorry :) -- Regards, Wolfram Schlich <[EMAIL PROTECTED]> Gentoo Linux * http://dev.gentoo.org/~wschlich/
[Dovecot] Out of memory
Hi, this happens since a few days on a Gentoo hardened system using a grsecurity enabled kernel running Dovecot 1.0.10, only to 2 of 10 users though: --8<-- kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537325568 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537321472 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537456640 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 kernel: grsec: From 192.168.0.1: denied resource overstep by \ requesting 537321472 for RLIMIT_AS against limit 536870912 \ for /usr/libexec/dovecot/imap[imap:15708] uid/euid:30010/30010 \ gid/egid:30006/30006, parent /usr/sbin/dovecot[dovecot:15574] \ uid/euid:0/0 gid/egid:0/0 dovecot: IMAP(info): block_alloc(): Out of memory dovecot: child 15708 (imap) returned error 83 (Out of memory) --8<-- grsecurity only logs the attempted resource overstep. I already increased mail_process_size to 512M and deleted the index.cache* files inside the users maildir -- didn't help :/ Any idea why this is happening or how I could find out? TIA :) -- Regards, Wolfram Schlich <[EMAIL PROTECTED]> Gentoo Linux * http://dev.gentoo.org/~wschlich/
[Dovecot] Dovecot With cygwin
Hi This is jesse. I am running exim as my mail server on cygwin. But i need imap/pop3 for accessing mail. I found that dovecot works on cygwin with some code change. So can i know how to compile dovecot on cygwin. This is important ANYBODY Be a better friend, newshound, and know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
Re: [Dovecot] Using deliver from Getmail?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have all my users (and the user running getmail) to mail group, so the folder is writable my mail group and also dovecot belongs to mail group. So i add the group = mail to getmailrc and everything works Andreas Ntaflos wrote: > On Monday 14 January 2008 19:10:10 Andreas Ntaflos wrote: >> On Monday 14 January 2008 18:47:27 Evaggelos Balaskas wrote: >>> This is part of my getmailrc >>> >>> [destination] >>> type = MDA_external >>> path = /usr/local/libexec/dovecot/deliver >>> user = ebal >>> group = mail >>> arguments = ( '-d', 'ebal' ) >>> >>> i use getmail + dovecot + sieve + spamassassin [filter getmail] >>> at all of my accounts. > > Follow-up: How did you configure Dovecot's authentication facilities and > which > permissions are set for the deliver binary? > > I think that is the problem I am having. I do not want to mess too much with > the default permissions but since you have it running fine maybe you could > share some insight? > > Thanks in advance! > > Andreas Evaggelos Balaskas - http://ebalaskas.gr Unix System Engineer Informatics Engineer Technological Education -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHjHHYWIK+Pe9twhoRAjRyAJ0cxPbwhCiSBc3z+Hrl5KtPbRShPwCfQ87Z bk4nIqAYh6PLgFTeGqgQ5xI= =WlQV -END PGP SIGNATURE-
