As I mentioned in another thread I set up these 2 namespaces for a couple of users:
namespace { inbox = yes location = prefix = separator = / type = private } namespace { location = maildir:/home/vmail/oeffentlich:INDEXPVT=/home/vmail/public/index/%d/%u/index prefix = Oeffentlich/ separator = / subscriptions = yes type = public }
It is planned that they all will use Thunderbird (on MS Windows) to access their mailboxes.
Now when I create a folder in the public space and try to delete it via thunderbird I get something like:
"Renaming not supported across non-private namespaces"
As far as I found out by browsing the web this is related to Thunderbird trying to move (=rename) the mail from the public to the private namespace, correct?
Setting TB to immediately remove mails (tested that, this works) seems a bit scary to me: this removes a safety layer for the users because this would also apply to their personal maildirs.
Is there any more elegant way of solving this?
Do I have to set up some kind of ACLs?
Some kind of "public paperbin folder" ??
Pls help me to understand this better ;-)
Regards, Stefan
Am 05.11.2014 um 18:50 schrieb Stefan G. Weichinger:
As I mentioned in another thread I set up these 2 namespaces for a couple of users:
namespace { inbox = yes location = prefix = separator = / type = private } namespace { location = maildir:/home/vmail/oeffentlich:INDEXPVT=/home/vmail/public/index/%d/%u/index prefix = Oeffentlich/ separator = / subscriptions = yes type = public }
It is planned that they all will use Thunderbird (on MS Windows) to access their mailboxes.
Now when I create a folder in the public space and try to delete it via thunderbird I get something like:
"Renaming not supported across non-private namespaces"
As far as I found out by browsing the web this is related to Thunderbird trying to move (=rename) the mail from the public to the private namespace, correct?
Setting TB to immediately remove mails (tested that, this works) seems a bit scary to me: this removes a safety layer for the users because this would also apply to their personal maildirs.
Is there any more elegant way of solving this?
Do I have to set up some kind of ACLs?
Some kind of "public paperbin folder" ??
Pls help me to understand this better ;-)
Am I in the wrong place with my questions?
Am 08.11.2014 um 19:12 schrieb Stefan G. Weichinger:
Now when I create a folder in the public space and try to delete it via thunderbird I get something like:
"Renaming not supported across non-private namespaces"
As far as I found out by browsing the web this is related to Thunderbird trying to move (=rename) the mail from the public to the private namespace, correct?
Setting TB to immediately remove mails (tested that, this works) seems a bit scary to me: this removes a safety layer for the users because this would also apply to their personal maildirs.
Is there any more elegant way of solving this?
Do I have to set up some kind of ACLs?
Some kind of "public paperbin folder" ??
Pls help me to understand this better ;-)
Am I in the wrong place with my questions?
yes - this is a server list
you just have two options in a mail-client
- delete immediately
- move it to trash folder
move in case of thunderbird is always copy+delete
that's how it works
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 08.11.2014 um 19:15 schrieb Reindl Harald:
Am I in the wrong place with my questions?
yes - this is a server list
I asked for a possible config change on the server side as well ;-)
you just have two options in a mail-client
- delete immediately * move it to trash folder
move in case of thunderbird is always copy+delete
that's how it works
Yep, thanks.
Stefan
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUXl6CAAoJEClcuD1V0PzmY/UP/RTw9cj5Jsa9jQWDnbA0Dts4 QKLWcAmU8f5qN/ip+PFiWn7bVHjFPMkzXGvBoR2msiR6uNEEd6+gokeNJCObM8xG MBAcsinHqKma67spWT5IaOmmUuaiZTbhvta40I3CoQpaXYRxXVze0RKlILYZPkk3 3rh1ceALckvU37s4mLa0QehmOs6R0LMB6Ldr9hnqvf252Abfg8GMoFTtpDJSlyS8 3vUkoy4Us06N5ac422A77Tb0VFqE3V1lFs40t9C0CeFOX/l+kEj2mzG0mexr2ylT zioy68Wb8CqhKEw/GP5O55KPCoZ7yJ3gVUeAGCezMZ+lfZ2UDZXXsgimsZ1tMFOw qAESPtqYd5T19+qKDIcu5HVqu9Hmw9W1XIhYvzvmkyEf3aTSBC7mfefSTFH2yE/W qzz12ZjcR/s0jdtgEWN1AWWCTNbEMxl/UBOSVEfZEdg/DlkE6vInrntyjLwviCIY EGl1a//v7bRIruWqZmfm6bdT2vC5VUaKj6VFmiPuRjcHSyzK6grLZAEmzXetVSEa rwRSfl8TMJlsqAaNZaNEAzr57DBldL7T6EKAJZb0xlLLgOqgy/PG7zFPMZki2Xp2 a0yYh1uwqef5/5RBM3EDuXKQOJ2yG2hrtFP1tIXutgD7yfwjY85uNhn72YLqy9ho nat6nUK4H5WU9sTcte5V =i3GA -----END PGP SIGNATURE-----
Am 08.11.2014 um 19:18 schrieb Stefan G. Weichinger:
Am 08.11.2014 um 19:15 schrieb Reindl Harald:
Am I in the wrong place with my questions?
yes - this is a server list
I asked for a possible config change on the server side as well ;-)
not use different namespaces - but that likely is no solution
you just have two options in a mail-client
- delete immediately * move it to trash folder
move in case of thunderbird is always copy+delete
that's how it works
Yep, thanks
looks like TB tries a atomic rename (depending on the server capabilities) which could do a fallback to copy/rename in case of a message - doing that for a whole folder i dangerous - in case the folder may contain 5000 messages
mayboe you could configure TB trash to a local folder instead keep it on the server (as long you control all clients) - may also help against users deleting junk but never empty trash :-)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 08.11.2014 um 19:33 schrieb Reindl Harald:
looks like TB tries a atomic rename (depending on the server capabilities) which could do a fallback to copy/rename in case of a message - doing that for a whole folder i dangerous - in case the folder may contain 5000 messages
mayboe you could configure TB trash to a local folder instead keep it on the server (as long you control all clients) - may also help against users deleting junk but never empty trash :-)
worth a thought, yes ... I will suggest that to the customer next week. Thanks, Stefan
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBAgAGBQJUXmMhAAoJEClcuD1V0Pzm7SQP/2IOyWhA3+rdeWbUqPddE4zH mSOEu5xbsWrSg3M+n+4dqxfpXoxTwGOFXr2GJyP0yZAG33j2W+xt5wSFRwTNdYXz d5GQyCwYPtY+H5ssPsVLqr5rxpKKVAp6SkZBDy4Cqi0bf1zqOxbBXvXGpU5WGO1M FuCJduEW0xa2iQOoJfNlr8kGc6ZwbIK1FluFNCwjDsPLQJ2lLyVTCZMRamF6y6zg chy5lqRIdRuENife/Kd2Yj+P5W75P2mrCSUhwqAyvM1L6Y8aHIxc74DuojOh1UFG 9IS9aQxGJGudvz9IotFylodeIjvexWqIr+24mTWYqsL831YS6PwW2A9x4ZhXejHa yg2VigihvJygG7o3fD0IEHpBBHeHUCgCyGCIzGQhRh0vJ6OSSoBlzq9xPG7Bn+K0 VkkSDKfjBuZRHx4BrtSI/Z9N7HjOxnh1Tg6LYrpJpM2aPtMUpPXe36HDXsT2gbtX ot4NyKNlxjK2KoNmvVgJcsoRjfS3Sz6h8SKVoRX8ukwJ+U/wp1UKTkuT/TSWNEtd fOA3lqMc10r9Lf7dqYFzxZEiLnN9+Z17SGOgepcKu+6MphweLrYiYzzvkx/mA9l8 8p59f2Y3JfimHFrMkp0aYCzQNr1mlzqYrfNO89BgbDgJn4rDxa+nYrEH+uWhc2IT 6Xxr71jt3y67rpV5nwpI =etZg -----END PGP SIGNATURE-----
On 08. nov. 2014 19:15, Reindl Harald wrote:
move in case of thunderbird is always copy+delete
that's how it works
Really? Sure? Icedove gives me THREE choices, move, mark as deleted, or delete immediately. I thought the codebase was the same for thunderbird and icedove?
With the middle choice (Just mark as deleted) I get a red cross over deleted messages, and they stay around until I "compact" the mailbox. The "just mark as deleted" might depend on dovecot announcing that capability, I have not checked. It IS available with dovecot using Maildir storage, under all icedove versions since I can remember.
Check your mail-client and see. Under "account settings" -> "server settings".
participants (3)
-
Håkon Alstadheim
-
Reindl Harald
-
Stefan G. Weichinger