ClearOS Bug Tracker

Main | My View | View Issues | Change Log | Roadmap | Repositories
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000933ClearOSapp-mail-extension - Mail Extensionpublic2013-01-11 20:192019-04-24 08:04
Reporteruser2 
Assigned To 
PrioritylowSeveritytweakReproducibilityalways
StatusclosedResolutionsuspended 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000933: Handle groups with spaces
DescriptionThough the GUI does not allow adding groups with spaces, there should be a way for the mail extension to handle setting the distribution list e-mail address for such groups. For example, a group name of "test group" needs to use something like "test_group@example.com" for the group distribution list. It's tricky since "test_group" might already exist. Perhaps there is a valid character for e-mail addresses, but not permitted for group names?

http://en.wikipedia.org/wiki/Email_address#Valid_email_addresses [^]
TagsNo tags attached.
Attached Files

- Relationships
related to 0000723closeduser2 app-groups allows group creation with spaces which is disallowed by app-users. 
related to 0002261closed Handle groups with spaces 

-  Notes
(0001392)
dloper (administrator)
2015-03-11 11:07
edited on: 2015-03-11 11:16

 This affects samba shares as well especially with flexshares where the default group of "domain users" is applied to a flexshare under active directory. To fix this in a flexshare, double-quotes can be added to the group name for example, the default behavior renders the valid users as:

valid users = @"%D\domain users", @domain users

When it should be:

valid users = @"%D\domain users", @"domain users"

Edit: added tracker 0002261 for Samba issue.
(0011561)
NickH (developer)
2019-04-24 08:04

 Migrated to https://gitlab.com/clearos/clearfoundation/app-mail-extension/issues/1 [^]

- Issue History
Date Modified Username Field Change
2013-01-11 20:19 user2 New Issue
2013-01-11 20:19 user2 Status new => assigned
2013-01-11 20:19 user2 Assigned To => user2
2013-01-11 20:19 user2 Issue generated from: 0000723
2013-01-11 20:19 user2 Relationship added related to 0000723
2015-03-11 11:07 dloper Note Added: 0001392
2015-03-11 11:14 user2 Issue cloned: 0002261
2015-03-11 11:14 user2 Relationship added related to 0002261
2015-03-11 11:16 user2 Note Edited: 0001392 View Revisions
2018-12-14 12:11 user2 Assigned To user2 => tracker
2019-04-24 08:04 NickH Note Added: 0011561
2019-04-24 08:04 NickH Status assigned => closed
2019-04-24 08:04 NickH Assigned To tracker =>
2019-04-24 08:04 NickH Resolution open => suspended