Dear All, I try to use the Public mailboxes. They work fine ! But i have to generate a more complex “Folder-Structure” within the Public Folders. I want to have a Subfolder per Domain and then different MailsAliases to be lead to the subfolders. Is that possible with the way Nethserver is working together with dovecot.
Thanks for this Articles, i read through it but dont find the soulution.
Maybe i was not detailed or understandable what i want to do is that incomming Mails are delivered to sub sub folders of the Public folder not only to the sub folder like in this grafic
its like a Proces / Kanban aproach with folders instead of using tikets and so on … they are working very efficent with this aproach for 15 Jears now and dont want to loose it …
Yes, but its not a one to one … lets say there are different brands that will be managed by a several Teams. A Office Team, a Billing team, a Support team, an some lets call them managers
al brands have there info@ billing@ support@ mailadresses … they all should be connected to a different public folder. but they should be structured in folders on the purpose of the mail
info@A → Public → general → A -->Inbox
info@B → Public → general → B -->Inbox
info@C → Public → general → C -->Inbox
support@A → Public → support–> A -->Inbox
support@B → Public → support → B -->Inbox
support@C → Public → support → C -->Inbox
…
so the Office will only see Public → General &Public -->Billing but not Support …
thats doable with creating public mailboxes and groups then set the right acls
theres a few ways to do this but the easiest IMHO is this
step 1. make groups in (users and groups) lets call them billinga, supporta and publica (since you mentioned abc simply make three sets of the three groups changing a to b and c)
step2. add all people in site “a” to have access to email publica to group publica same with site b and c.
step 3.then add all who should have access to billing to billinga,b,c etc and same with support
step 4. then in email go to mailboxes and then public mailboxes create info@a.domain.tld and set acl to groups publica do this for b and c as well
then create billing@a.domain.tld set acl to groups billinga do this for b and c as well
then create support@a.domain.tld set acl to groups supporta do this for b and c as well
i found that topic, but only for having the inboxes on root level of public … like
public->SupportA
public->SupportB
public->SupportC
what i need ist
Public–>what ever folder–>what ever nextfolder->inbox(Support@dmoainA.com)
so i want to lead the inboxes to sub-sub-folders not to the sub folder
i understand but i think the easiest way to acheive this is by setting the ussers in three setts of three groups then set the groups individualy as acl ie billing@sitea can be accessed by users in group billinga and info@sitea can be accessed by users in group publica then for people in billinga group add them to public as well and add users in supporta to publica so users in billinga can see billing@sitea and info@sitea and users in supporta can see support@sitea and info@sitea
i understand the workaround but i realy ned the freedom to set what ever mailadress to what ever needed Public subfolder because of real complex structure in Public folders … i just tried to explain it as simpe as i can
think about a mailadress per Project …
Public → Projects → Department → ProjectA …
e.g. if you have about 100 projcts that leads to 100 entrys in the root level of public … that isn’t managebal … so you need subfolders
ok so would work like this you follow what i mentioned but when you go to public mailboxes (i was thinking interms of email not mailboxes for some reason)
when you create group publica it assigns publica@domaina.com but the email can be ignored same with billing and support now what you do is
create the groups publica billinga supporta and assign users appropriately
you set public mailbox billinga and another for supporta and a third for publica acls to info billing and support
now this would be alot of manual setting if as i beleive your setting up multiple sets this could be scripted (i feel like i should get a t-shirt saying something like nah ill just make bash do it )
the way i would envision that is you have a script to automate the group creation have user group assigned (if it’s a long list) by data from a list (cvs maybe) then have the script setup mailbox and assign acl and then add the address to point to the mailbox i mean if this is something you will be creating and maybe adding people to on a regular bassis it could be set to automaite and you could just feed it a cvs to import users have the same data set pulled again to assign groups and ofcourse the other domains ie domainb.com and c depending howfar you want to go you could have the script automate the adding of domains if you realy wanted
can i ask why (if you dont mind),
is it so mass email can be sent to one email address and be received by everyone regardless of domain if thats the reason then you could have a catchall email that sends to everyone.
but (and i mean no offense and I’m sure there would be reasons I’m just not seeing any other reason that would require this) if you want to have say office a seing email for info and billing but not support and hence would be setup by acl would be redundant
The usage at the end is they use Public Folders like an Kanbanboard. the Backlog is the incomming folder thenn they have different subfolders like swimlanes, to some swimlanes it is allowed to write direktly and you dont need to use the Backlog folder.
what tey are dooing is Electronics, Cables, Devellopment,Shipping and Sales … they have diferent Brands and a Matrix organisation behind. from the Backlog a Groupleader is dropping mails to the swimlanes, so he has the right (ACL) to see all of them some user se only theire swim lane some can see a subset of swimlanes …
I know it is a kind of sufisticated use of public folders and sometimes it would be better to have a tiketsystem behind (we tryed it several times, doesent work vor them ) the public folder structure works vor them since years …
)