Re: Packages for CentOS 8
On 1 Jun 2020, at 17:02, Peter wrote: On 2/06/20 1:49 am, Aki Tuomi wrote: we are still waiting for CentOS 8 Repo for current Dovecot version from here https://repo.dovecot.org/. Do you have an idea when it will come? Who does it maintain? Is it the Dovecot team? Thanks, Tobias Yes, it's maintained by us. We are working on it and hopefully we are able to publish next release for CentOS8. There are unfortunately some package dependency issues which are not yet fixed in CentOS8, so let's hope those are fixed before we do our release. Aki: If you're talking about quota-devel it has been available now from CentOS in the Devel repo for a while. If you're talking about tcp_wrappers-devel, that is not available and I don't think it ever will be because CentOS 8 has obsoleted tcp wrappers. I have simply disabled tcp wrappers functionality in my GhettoForge build. I'm not aware of any other missing dependencies. Tobias: You are more than welcome to use the packages from GhettoForge which are now in the gf-plus repo. I would love to hear feedback if you have any issues with them. We will have a look at gf-plus, thank you! Tobias
Re: Packages for CentOS 8
Hi Peter, On 9 Apr 2020, at 12:53, Peter wrote: I've now successfully built Dovecot packages for CentOS 8 that do not have the quota support stripped out. I was able to do this because CentOS has now finally shipped the quota-devel package as well as the other -devel packages that were previously missing from CentOS 8. For those of you who are interested they are in the GhettoForge Testing repo for el8 at: http://mirror.ghettoforge.org/distributions/gf/el/8/testing/x86_64/ These are untested so let me know if anyone experiences any issues with them. we are still waiting for CentOS 8 Repo for current Dovecot version from here https://repo.dovecot.org/. Do you have an idea when it will come? Who does it maintain? Is it the Dovecot team? Thanks, Tobias
Re: shared folder name or public folder with mail address
On 15 Feb 2020, at 19:04, Armin Schindler wrote: The shared and public folders need of course the anyone post right to let fileinto work. Or you have a special „list user“ which has the appropriate permissions - depends all on the use case. Now it works. Thank you Tobias. Well done! :) -- collect@shift.agency
Re: shared folder name or public folder with mail address
On 15 Feb 2020, at 12:27, Armin Schindler wrote:
On 15.02.2020 12:16, Tobias Kirchhofer wrote:
...
the sieve part seems to be very tricky.
My test is now working with a public folder and I have a
"sieve_before" script in place which works for rules of the
private namespace.
But when the rule shall "fileinto" a public folder, the mail
isn't
filtered (moved) and syslog says
dovecot: lmtp(.): Error ... sieve...: Mailbox doesn't exist.
After some tests I found out it always looks in the private (or
shared)
namespace for that specfied folder.
Do I miss a config option to let dovecot sieve "fileinto" a
public
namespace folder?
I use dovecot version 2.2.13.
We „fileinto“ in this manner :
|fileinto „Namespace/folder“; |
This is what is not working for me.
Your procedure below is good and maybe I will use parts of it, thank
you. But this part is working for already. The incoming mail
is sent to dovecot (postfix virtual alias working) and the
match in sieve script is correct too.
The problem is that dovecot (sieve) refuses to
fileinto "Namespace/folder"
because it seems it wants to store the mail
in private namespace with "folder1/folder2" instead.
The first part of the fileinto path isn't used as
namespace name.
Is there a config option for this behaviour?
Maybe you are missing an include?
We have:
```
require "fileinto";
require "mailbox";
require "envelope";
require "subaddress";
require "variables";
require "regex";
require "editheader";
require "include";
```
In dovecot.conf* i found no directly related settings. Just the usual
sieve settings explained here
https://wiki.dovecot.org/Pigeonhole/Sieve/Configuration
Can you see the Public namespace and the folder in your MUA or via
telnet?
Are you sure the ACL are correct? Can be that the error message
„Mailbox doesn't exist“ is misleading and the permissions are not
correct.
Here you can see how to debug if not already
https://wiki.dovecot.org/Pigeonhole/Sieve/Configuration#Trace_Debugging
Armin
The procedure in our setup is like this:
1. Virtual alias for each public-Folder email address within
postfix:
Pattern:
fol...@domain.tld <mailto:fol...@domain.tld>
listadm+Namespace/fol...@domain.tld <mailto:fol...@domain.tld>
Example:
i...@domain.tld <mailto:i...@domain.tld>
listadm+Verteiler/i...@domain.tld <mailto:i...@domain.tld>
Verteiler is the namespace, info the mailbox. listadm is a pseudo
user
in this context which holds the ACL for fileinto the resulting
mailbox
with proper permissions.
2. Disassemble the virtual alias address with sieve:
Excerpt of the script. It is actually more code because we sort out
spam
for public folder. German comments, sorry.
|# Hat Subadresse? if envelope :matches :detail "to" "*" { #
Adressaufbau: listadm+Namespace/liste@ # ${liste} wird Namespace/box
set
"liste" "${1}"; } […] fileinto "${liste}"; |
I can send you the whole script if you need.
--
collect@shift.agency
Re: Dovecot 2.3 repo for CentOS 8.
On 14 Feb 2020, at 10:59, Peter wrote: On 14/02/20 10:10 pm, Tobias Kirchhofer wrote: would it be useful/advisable to use this repo for productive operation? An official repo is still not available for CentOS 8 https://repo.dovecot.org/ We would like to set up our new mail server on CentOS 8 and are waiting… :) What is your advice? As others have mentioned there are missing -devel packages in CentOS 8, which is because there are missing -devel packages in RHEL 8, most notably in this case is quota-devel. tcp wrappers is also missing but that's because they are deprecated in CentOS 8 so building without tcp wrapper support is not a big deal, but I would assume that a lot of people will want quota support, so I wouldn't want to build a dovecot package without it. Personally I'm trying to get the GhettoForge build system modified so it can get missing -devel packages by rebuilding the source rpms for them, this is a work in progress. There is also work on the CentOS side to build and offer up the missing -devel packages. At the end of the day nobody will be able to build decent dovecot packages until one of these things happens. For now you can use the stock dovecot 2.2.36 that comes with CentOS or you can wait. CentOS and Red Hat have not made this easy so it is going to take time. Okay, will try 2.2.36. Our protoype is on Debian 10 with the latest Dovecot. Don’t know yet if we rely on features from the latest version. Will see. Thank you. Also on a personal note, I think that pushing out any production server on CentOS 8 at this time is premature. CentOS 8 simply is not ready yet, imo. We have CentOS 8.1 VMs productive with either of nginx, PostgreSQL, MariaDB, Node.js. No problems so far. Cross your fingers! :-) Peter -- collect@shift.agency
Re: shared folder name or public folder with mail address
On 15 Feb 2020, at 10:43, Armin Schindler wrote:
On 14.02.2020 11:44, Tobias Kirchhofer wrote:
On 14 Feb 2020, at 11:06, Armin Schindler wrote:
...
The sorting in the according public folder happens in a global sieve
script before user scripts are fireing. It is combined with the
‚+‘
notation in postfix for sub addresses and an special ‚listadm‘
user
postfix:
|
listadm+Verteiler/info@$DOMAIN
|
The sieve script is then reading the generated address and delivers
it
into the according public folder. We learned a lot about sieve
scripting
with this task :-)
|sieve_before = /var/vmail/sieve/global/global-before.sieve […] |
More details would be to much here.
To be honest, we needed some time to get it done properly. It is a
combination of features and A LOT OF testing and analysing the
behaviour
of postfix/dovecot/public-folder/sieve/acl.
the sieve part seems to be very tricky.
My test is now working with a public folder and I have a
"sieve_before" script in place which works for rules of the
private namespace.
But when the rule shall "fileinto" a public folder, the mail isn't
filtered (moved) and syslog says
dovecot: lmtp(.): Error ... sieve...: Mailbox doesn't exist.
After some tests I found out it always looks in the private (or
shared)
namespace for that specfied folder.
Do I miss a config option to let dovecot sieve "fileinto" a public
namespace folder?
I use dovecot version 2.2.13.
We „fileinto“ in this manner :
```
fileinto „Namespace/folder“;
```
The procedure in our setup is like this:
1. Virtual alias for each public-Folder email address within postfix:
Pattern:
fol...@domain.tld listadm+Namespace/fol...@domain.tld
Example:
i...@domain.tld listadm+Verteiler/i...@domain.tld
Verteiler is the namespace, info the mailbox. listadm is a pseudo user
in this context which holds the ACL for fileinto the resulting mailbox
with proper permissions.
2. Disassemble the virtual alias address with sieve:
Excerpt of the script. It is actually more code because we sort out spam
for public folder. German comments, sorry.
```
# Hat Subadresse?
if envelope :matches :detail "to" "*"
{
# Adressaufbau: listadm+Namespace/liste@
# ${liste} wird Namespace/box
set "liste" "${1}";
}
[…]
fileinto "${liste}";
```
I can send you the whole script if you need.
Greetings!
Tobias
--
collect@shift.agency
Re: shared folder name or public folder with mail address
On 14 Feb 2020, at 15:02, Armin Schindler wrote: On 2/14/20 2:23 PM, Tobias Kirchhofer wrote: On 14 Feb 2020, at 14:05, Armin Schindler wrote: On 2/14/20 11:44 AM, Tobias Kirchhofer wrote: On 14 Feb 2020, at 11:06, Armin Schindler wrote: Hello! […] For our new setup (planned with CentOS 8, waiting for the official repo for the latest dovecot version…) we have a prototype on Debian base with the latest version of Dovecot. In opposite to our current solution we will implement global acls with user and groups from LDAP. This is very nice. Wow, thanks. This seem to be exactly what I need to go on. Our base system is a Univention UCS, so LDAP users and groups is what we already have working :-) With your elements I think we really could have the cyrus shared folders with dovecot by using a namespace of type=public but with prefix=shared/ (we might use type=shared with prefix=usershared/ later). There is not something like one way do to this. You could also make your life easier and choose to create a „Share user“ which is only there to share folders. This will then be Dovecot „Shared folders“ shared by this pseudo user to other users. You then could use Roundcube or such to maintain acl with this pseudo user. But we did not follow this path then for reasons i cannot remember anymore :) For each Public folder we have a defined namespace. „Newsletter“, „Client1“, „Client2“ etc. We have many, around 30 or so. ACL goes on this namespace (namespace/*). I guess ACL are first match. Each namespace has its own prefix. (eq. prefix = Newsletter/, prefix = Client1 etc.) User can subscribe namespace by namespace acl assumed. What is the benefit using own namespace for each public folder? If the config is equal for all folders, wouldn't one namespace with subfolders be the same? One public namespace would look like it is with cyrus in the client: one "shared/" folder to open/close. Yes, this was a misunderstanding - we have a lot of subfolders per namespace. The subfolders have ACLs. -- collect@shift.agency
Re: shared folder name or public folder with mail address
On 14 Feb 2020, at 14:05, Armin Schindler wrote: On 2/14/20 11:44 AM, Tobias Kirchhofer wrote: On 14 Feb 2020, at 11:06, Armin Schindler wrote: Hello! […] For our new setup (planned with CentOS 8, waiting for the official repo for the latest dovecot version…) we have a prototype on Debian base with the latest version of Dovecot. In opposite to our current solution we will implement global acls with user and groups from LDAP. This is very nice. Wow, thanks. This seem to be exactly what I need to go on. Our base system is a Univention UCS, so LDAP users and groups is what we already have working :-) With your elements I think we really could have the cyrus shared folders with dovecot by using a namespace of type=public but with prefix=shared/ (we might use type=shared with prefix=usershared/ later). There is not something like one way do to this. You could also make your life easier and choose to create a „Share user“ which is only there to share folders. This will then be Dovecot „Shared folders“ shared by this pseudo user to other users. You then could use Roundcube or such to maintain acl with this pseudo user. But we did not follow this path then for reasons i cannot remember anymore :) For each Public folder we have a defined namespace. „Newsletter“, „Client1“, „Client2“ etc. We have many, around 30 or so. ACL goes on this namespace (namespace/*). I guess ACL are first match. Each namespace has its own prefix. (eq. prefix = Newsletter/, prefix = Client1 etc.) User can subscribe namespace by namespace acl assumed. But as i sad - by writing this i get nervous, cause i now that you must immerse deeply with this topic. Otherwise you will not get happy :) Tobias Or is the idea of just *one* public folder with name "shared" and with subdirs for different "projects/departments/topics" not working as expected? ACL is something I didn't look at yet. Is it possible to set different permissions for the folders in the public prefix like /shared/dir1 , /shared/dir2 , etc. or even for sub-subfolders? Global ACLs aren't neccessary when using folder acls, right? Armin […] -- collect@shift.agency
Re: shared folder name or public folder with mail address
On 14 Feb 2020, at 11:06, Armin Schindler wrote:
Hello!
we are about to move from cyrus to dovecot and have one open issue
for that migration.
With cyrus we have "shared/" folders with a name that is self defined
like
shared/project-xyz
but the email address for direct delivery to that folder my be
different
(not project-...@domain.com).
With dovecot we try to have it similar (at least how the user sees it
in the client)
like it is now.
When configuring a namespace of type=shared, I see in the docs the the
prefix
can be configured with %%u , %%n or %%d. But is it possible to
configure
the name different to the email address? E.g. to hide the email
address of
that folder and show a nice name instead?
I also thought about using public namespace instead. Does this make
sense here?
With public (maybe configured with prefix=shared/) folder I can set
any name
as subdir in prefix, right?
So would this be more like what we have with cyrus shared folder?
If so, how could these public folders have an email address for direct
mail delivery into?
Can something like a global sieve rule do that? Or can a public folder
have an email address?
Thanks in advance.
Armin
Hi, we went through this some years ago. It is a bit tricky in the
details. Involved is postfix, public namespace, subscriptions, acl,
sieve.
We found a quite comprehensive solution so far. It is working similar to
Cyrus shared folder. Do not mix the names. Cyrus „shared“ folders
are „public“ folders in Dovecot. Dovecot „shared“ folders are
personally shared folders from one user to another.
For our new setup (planned with CentOS 8, waiting for the official repo
for the latest dovecot version…) we have a prototype on Debian base
with the latest version of Dovecot. In opposite to our current solution
we will implement global acls with user and groups from LDAP. This is
very nice.
Some elements:
Global ACL:
```
[..]
Newsletter group=administrator lrwstipekxa
Newsletter/* group=team lrwstipe
Newsletter/* user=n...@domain.tld lrwstipe
[…]
```
Public folder:
```
namespace {
type = public
prefix = Newsletter/
separator = /
location =
maildir:/var/vmail/public/$DOMAIN/newsletter:LAYOUT=fs:INDEXPVT=~/public/$DOMAIN/newsletter
subscriptions = no
hidden = no
list = children
}
```
Subscriptions (! This one was tricky)
```
namespace subscriptions {
subscriptions = yes
prefix =
separator = /
list = no
hidden = yes
}
namespace inbox {
inbox = yes
separator = /
prefix = INBOX/
subscriptions = no
[…]
```
„Dovecot“ Shared folder (optional):
```
namespace shared {
type = shared
separator = /
prefix = Shared/%%u/
location = maildir:%%h/:INDEXPVT=~/shared/%%u
list = children
subscriptions = no
}
```
The sorting in the according public folder happens in a global sieve
script before user scripts are fireing. It is combined with the ‚+‘
notation in postfix for sub addresses and an special ‚listadm‘ user
postfix:
```
listadm+Verteiler/info@$DOMAIN
```
The sieve script is then reading the generated address and delivers it
into the according public folder. We learned a lot about sieve scripting
with this task :-)
```
sieve_before = /var/vmail/sieve/global/global-before.sieve
[…]
```
More details would be to much here.
To be honest, we needed some time to get it done properly. It is a
combination of features and A LOT OF testing and analysing the behaviour
of postfix/dovecot/public-folder/sieve/acl. For now we have a Public
folder setup which is as nice like it is with Cyrus. With Cyrus this
issue is less complex to implement.
Maybe this helps a bit. Take exclusivly one to two weeks for this task
and read and test a lot! :-)
Tobias
--
collect@shift.agency
Re: Dovecot 2.3 repo for CentOS 8.
Hi Filip, On 12 Dec 2019, at 12:01, fil...@centrum.cz wrote: > Hello, > I have builded some dovecot packages for CentOS 8 in my personal > repository: > http://repo.joomhosting.eu/centos/8/x86_64/ > and SRPMS are in > http://repo.joomhosting.eu/centos/8/SRPMS/ > > I you want you can try it. > > With best regards, > Filip Bartmann would it be useful/advisable to use this repo for productive operation? An official repo is still not available for CentOS 8 https://repo.dovecot.org/ We would like to set up our new mail server on CentOS 8 and are waiting… :) What is your advice? Tobias > On Thu, 12 Dec 2019 12:31:45 +0200 > Reio Remma wrote: > >> On 09/12/2019 17:25, Aki Tuomi via dovecot wrote: On 09/12/2019 17:20 Reio Remma via dovecot wrote: Hello! Are there any plans for an official Dovecot repo for CentOS 8? Thanks, Reio >>> (sorry for duplicate, user error in earlier one...) >>> >>> Yes. There are plans for the repo, unfortunately there are still >>> technical problems due to how CentOS8 repositories are organized. >>> But soon. >>> >>> Aki >> >> I tried rebuilding the RPM for CentOS 8 but I see it's missing some >> notable required packages like tcp wrappers and quota-devel. Managed >> to rebuild by switching these off in the spec file >> (--without-libwrap), but that's probably not a good idea. :) >> >> Reio -- collect@shift.agency
Re: [ext] Dovecot Wiki: Please disable edit on double click
On 20 Mar 2019, at 11:59, Ralf Hildebrandt via dovecot wrote: * Michael Goth via dovecot : could you maybe disable the 'edit on doubleclick' feature on wiki2.dovecot.org? Everytime I try to select a word by double clicking on it, I end up in editing mode. It's just a minor thing, but maybe I'm not the only one who's annoyed by this ;) Amen to that. I never bothered to ask, but it annoys the shit out of me! Same same here :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de -- collect@shift.agency
Re: Error with virtual index "Broken mailbox_count header"
On 2 Jan 2019, at 9:48, Aki Tuomi wrote:
Can you try
INBOX
INBOX/*
-INBOX/Trash
-INBOX/Spam
all
This worked already, all E-Mails from Namespace INBOX and below. What we
want is „All E-Mails from all Namespaces“. We have several beside
INBOX/, like Admin/ News/ Clients/ a.s.o.
Do we have to name each Namespace explicitly?
Aki
On 02 January 2019 at 10:40 Tobias Kirchhofer
wrote:
On 2 Jan 2019, at 9:27, Aki Tuomi wrote:
Please provide doveconf -n
Sure:
https://crypto.shift.agency/?66a9e34e83032c3e#ovF5Yq5qTNa8ii7Qup4oy8h5HyEVLKl/RbhCFpQGkkY=
Aki
On 02 January 2019 at 10:26 Tobias Kirchhofer
wrote:
Hi, we experience trouble with one of our virtual mailboxes.
dovecot-virtual:
`
*
-INBOX/Trash
-INBOX/Spam
all
`
Error log:
```Error: virtual index
/var/vmail/mailboxes/kirchhofer.net/tobias/virtual/all: Broken
mailbox_count header```
This happens only with the filter form above. All other virtual
mailboxes works fine.
Jakobus Schürz experienced something similar:
https://www.dovecot.org/list/dovecot/2018-January/110656.html
We do not have the panic message.
Is this probably something on our side or is this Dovecot?
```
namespace virtual {
prefix = Virtual/
separator = /
location = virtual:~/virtual
}
--
collect@shift.agency
--
collect@shift.agency
--
collect@shift.agency
Re: Error with virtual index "Broken mailbox_count header"
On 2 Jan 2019, at 9:27, Aki Tuomi wrote:
Please provide doveconf -n
Sure:
https://crypto.shift.agency/?66a9e34e83032c3e#ovF5Yq5qTNa8ii7Qup4oy8h5HyEVLKl/RbhCFpQGkkY=
Aki
On 02 January 2019 at 10:26 Tobias Kirchhofer
wrote:
Hi, we experience trouble with one of our virtual mailboxes.
dovecot-virtual:
`
*
-INBOX/Trash
-INBOX/Spam
all
`
Error log:
```Error: virtual index
/var/vmail/mailboxes/kirchhofer.net/tobias/virtual/all: Broken
mailbox_count header```
This happens only with the filter form above. All other virtual
mailboxes works fine.
Jakobus Schürz experienced something similar:
https://www.dovecot.org/list/dovecot/2018-January/110656.html
We do not have the panic message.
Is this probably something on our side or is this Dovecot?
```
namespace virtual {
prefix = Virtual/
separator = /
location = virtual:~/virtual
}
--
collect@shift.agency
--
collect@shift.agency
Error with virtual index "Broken mailbox_count header"
Hi, we experience trouble with one of our virtual mailboxes.
dovecot-virtual:
`
*
-INBOX/Trash
-INBOX/Spam
all
`
Error log:
```Error: virtual index
/var/vmail/mailboxes/kirchhofer.net/tobias/virtual/all: Broken
mailbox_count header```
This happens only with the filter form above. All other virtual
mailboxes works fine.
Jakobus Schürz experienced something similar:
https://www.dovecot.org/list/dovecot/2018-January/110656.html
We do not have the panic message.
Is this probably something on our side or is this Dovecot?
```
namespace virtual {
prefix = Virtual/
separator = /
location = virtual:~/virtual
}
--
collect@shift.agency
dsync backup public namespace - how?
Hello,
We just celebrated the launch of our new mailserver setup (Dovecot and
Postfix). Really nice!
Now we want to change our quickfix backup with rsync to dsync.
For mailder backup of users this was an easy task:
dsync -v -f -u "${user}" backup "maildir:${destination}" (local file path
destination)
We use many public folder with ACL and now we are wondering how we can backup
these folder in a similar manner:
a)
dsync -u dove...@domain.com backup -n Namespacename
"maildir:/var/vmail-backup/backup/public"
or
b)
dsync -v -u dove...@domain.com -N backup "maildir:${destination}
But this is not working.
a) does nothing, no error
b) Error message: doveadm(dove...@domain.com): Fatal: -N parameter requires
syncing with remote host
Any ideas?
# dovecot --version
2.2.13
--
Tobias Kirchhofer
tob...@kirchhofer.net
signature.asc
Description: OpenPGP digital signature
Re: shared/public mailbox application
Sounds good - this could do the trick. Post the final and working concept :) On 29 Nov 2016, at 17:58, Michael Fox wrote: >> Basically we alias n...@domain.com to dove...@domain.com. doveadm@ has a >> sieve-Script which files into the public folder. You could also configure >> a postfix transport which does the job. > > Ah. OK. That may be more complexity than I need for my situation. So > please bear with me as I try to understand this. > > IF: > > Postfix is already configured to deliver mail destined for the virtual domain > "domain.com" to Dovecot > --and-- > I create the NAMESPACE and NAME setup as you described > --and-- > I create a Dovecot userdb entry for n...@domain.com (but no passdb entry) > --and-- > I configure ACLs so that all domain.com users can read NAME's mailbox but > only admin users can delete messages in NAME's mailbox > --and-- > I configure the virtual INBOX for POP users to include "RealMails" and "NAME" > > THEN, I'm thinking that: > > Because there is no passdb entry, user n...@domain.com cannot log in > --and-- > Because userdb defines NAME's home directory, incoming mail to > n...@domain.com would be delivered to the NAME mailbox, just like any other > user in domain.com, without the need for aliasing or sieve > --and-- > Because of the ACLs, IMAP admin users would be able to delete/manage NAME's > messages and everyone else would be able to read NAME's messages > --and-- > Because of the virtual INBOX, POP users would be able to read the NAME > messages. > > Does that make sense? Am I missing something? > > >> Its necessary to overlook the whole process chain to properly configure >> everything. > > Yes! Agreed! That's why I'm trying to think through the whole thing before > diving down a rabbit hole that leads to a dead end. > >> And a lot of try out :) > > For sure. (Just as soon as I understand what I'm trying to do.) ;-) > > Michael -- Tobias Kirchhofer tob...@kirchhofer.net signature.asc Description: OpenPGP digital signature
Re: shared/public mailbox application
Basically we alias n...@domain.com to dove...@domain.com. doveadm@ has a sieve-Script which files into the public folder. You could also configure a postfix transport which does the job. Its necessary to overlook the whole process chain to properly configure everything. And a lot of try out :) On 29 Nov 2016, at 6:34, Michael Fox wrote: > Thanks Tobias. Thanks for the detailed reply. > > > > I think I see what you’re doing. But I’m unclear on something (since I’m a > nube): > > > > Can anyone send mail to n...@domain.com <mailto:n...@domain.com> and have it > appear in the public mailbox? > > > > If not, would it be enough to create a userdb entry which defines a > pseudo-user NAME, including its home directory, such that imcoming mail > addressed to n...@domain.com <mailto:n...@domain.com> could be delivered > into that mailbox? > > > > Thanks, > > Michael > > > > > > > > From: Tobias Kirchhofer [mailto:tob...@kirchhofer.net] > Sent: Monday, November 28, 2016 7:19 AM > To: Michael Fox <n...@mefox.org> > Cc: Dovecot Mailing List <dovecot@dovecot.org> > Subject: Re: shared/public mailbox application > > > > Hi Michael, > > we migrated from Cyrus Shared Folders to Dovecot Public Folder. > > Our setup with Dovecot: > > * Public Namespace type=public > * prefix=NAMESPACE > * > location=maildir:/var/vmail/public/domain.com/folder:INDEXPVT=~/public/domain.com/NAME > * list=children to show NAMESPACE only if acl is given > * Restart Dovecot > * cd /var/vmail/public/domain.com/NAMESPACE > * mkdir .NAME > * We utilise one user <mailto:dove...@domain.com> dove...@domain.com to > control acl > * doveadm acl set -u <mailto:dove...@domain.com> dove...@domain.com > NAMESPACE/NAME user= <mailto:dove...@domain.com> dove...@domain.com all (this > creates also the Maildir) > * doveadm mailbox subscribe -u <mailto:dove...@domain.com> > dove...@domain.com NAMESPACE/NAME > * dm acl set -u <mailto:dove...@domain.com> dove...@domain.com > NAMESPACE/NAME user= <mailto:firstname.lastn...@domain.com> > firstname.lastn...@domain.com lookup read write write-seen write-deleted > insert post expunge > > User <mailto:firstname.lastn...@domain.com> firstname.lastn...@domain.com > can now subscribe to the public folder „NAMESPACE/NAME“. > > With this base you could create a more specific setup which more precisely > fits your need. > > There are also other strategies achieving Shared Folders the Cyrus way. :) > > Hope that helps. > > Tobias > > On 28 Nov 2016, at 15:38, Michael Fox wrote: > > No answer. Trying again. Surely someone with experience with public > mailboxes can offer some insight on whether the application below should be > a public or shared namespace ... > > Thanks > Michael > > -Original Message- > From: dovecot [mailto: <mailto:dovecot-boun...@dovecot.org> > dovecot-boun...@dovecot.org] On Behalf Of Michael Fox > Sent: Thursday, November 24, 2016 11:53 AM > To: Dovecot Mailing List <mailto:dovecot@dovecot.org> dovecot@dovecot.org > Subject: shared/public mailbox application > > I'm new to Dovecot and I need help configuring a shared or public mailbox - > I'm not sure which is appropriate. I've read the wiki and Peer's book and > neither appears to cover what I'd like to do. So I could use some specific > help on how to configure a solution for the following: > > I'd like to create two real mailboxes, let's call them AAA and BBB. Let's > call the domain "mydomain". By "real", I mean that users aaa@mydomain and > bbb@mydomain can log into their own mailbox. > > Anyone user can send mail to them, just like any other address: > aaa@mydomain or bbb@mydomain. > > I'd like all IMAP users in mydomain to be able to read the messages in those > mailboxes. > > I'd like all POP users in mydomain to also see those messages. (But I don't > think I need help with the virtual part). > > I'd like only a few designated IMAP users to be able to delete the messages > in those mailboxes, including dummy users AAA and BBB themselves. > > Ideally, I'd like them to appear in the client under a separate namespace > from shared mailboxes. Example: > > INBOX > > +--- the normal stuff. > > Shared > > +--- user1 > > +--- user2 > > Special > > +--- AAA > > +--- BBB > > My confusion: > > 1) I don't know if this requires a shared namespace or a public > namespace. It "feels" like it's "public", since all users would have > access. But Peer's b
Re: shared/public mailbox application
Hi Michael, we migrated from Cyrus Shared Folders to Dovecot Public Folder. Our setup with Dovecot: - Public Namespace type=public - prefix=NAMESPACE - location=maildir:/var/vmail/public/domain.com/folder:INDEXPVT=~/public/domain.com/NAME - list=children to show NAMESPACE only if acl is given - Restart Dovecot - cd /var/vmail/public/domain.com/NAMESPACE - mkdir .NAME - We utilise one user dove...@domain.com to control acl - doveadm acl set -u dove...@domain.com NAMESPACE/NAME user=dove...@domain.com all (this creates also the Maildir) - doveadm mailbox subscribe -u dove...@domain.com NAMESPACE/NAME - dm acl set -u dove...@domain.com NAMESPACE/NAME user=firstname.lastn...@domain.com lookup read write write-seen write-deleted insert post expunge User firstname.lastn...@domain.com can now subscribe to the public folder „NAMESPACE/NAME“. With this base you could create a more specific setup which more precisely fits your need. There are also other strategies achieving Shared Folders the Cyrus way. :) Hope that helps. Tobias On 28 Nov 2016, at 15:38, Michael Fox wrote: > No answer. Trying again. Surely someone with experience with public > mailboxes can offer some insight on whether the application below should be > a public or shared namespace ... > > Thanks > Michael > > > -Original Message- > From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Michael Fox > Sent: Thursday, November 24, 2016 11:53 AM > To: Dovecot Mailing List <dovecot@dovecot.org> > Subject: shared/public mailbox application > > I'm new to Dovecot and I need help configuring a shared or public mailbox - > I'm not sure which is appropriate. I've read the wiki and Peer's book and > neither appears to cover what I'd like to do. So I could use some specific > help on how to configure a solution for the following: > > > > I'd like to create two real mailboxes, let's call them AAA and BBB. Let's > call the domain "mydomain". By "real", I mean that users aaa@mydomain and > bbb@mydomain can log into their own mailbox. > > Anyone user can send mail to them, just like any other address: > aaa@mydomain or bbb@mydomain. > > I'd like all IMAP users in mydomain to be able to read the messages in those > mailboxes. > > I'd like all POP users in mydomain to also see those messages. (But I don't > think I need help with the virtual part). > > I'd like only a few designated IMAP users to be able to delete the messages > in those mailboxes, including dummy users AAA and BBB themselves. > > Ideally, I'd like them to appear in the client under a separate namespace > from shared mailboxes. Example: > > > > INBOX > > +--- the normal stuff. > > Shared > > +--- user1 > > +--- user2 > > Special > > +--- AAA > > +--- BBB > > > > My confusion: > > 1) I don't know if this requires a shared namespace or a public > namespace. It "feels" like it's "public", since all users would have > access. But Peer's book and the wiki describe manually creating folders for > public namespaces and controlling the contents with manual file > manipulation, which leads me to believe that they can't be used for regular > mail (although the book and the wiki never say one way or the other). I > don't want to manually control files. I want to send mail to the mailbox > and delete (see above) it with a client. > > 2) There are several examples in Peer's book and the wiki, but none > seem to match what I want. (This is the problem with documentation that is > predominantly example-based). I guess I need more explanation of the > mechanical differences between shared and public and why one would pick one > over the other. > > > > Can someone help? Please be as specific as you can. > > > > Thanks much, > > Michael -- Tobias Kirchhofer tob...@kirchhofer.net signature.asc Description: OpenPGP digital signature
