emailaddress2set4default

dragonxi

Consider for email address
(1) to be unique
(2) to be non space
(3) to have default easy to search "dummy" etc
(4) to be mandatory to key in if not (3)
Why ?
(4) several email addresses with empty name
possible to create and propability to have them increases when wait times for email users increase
(5) no way to search these orphans, only to view if any scrolling email address lists
(6) no way to mark and delete
(7) only way to delete is to edit each one and then delete
Notes:
(8) no way to use search to pick a suitable email user from the latest database - instead you have to be happy with the list the server provides and which may not contain the email user although its pwd has been created and it has been created according to server message !
(9) however, what is important is that it IS POSSIBLE to create several email users and email addresses - takes some time to learn for example how many request to put into queue at a time and how long to wait getting something from queue and how to find created email and domain objects which are not sorted.

sean

Thanks for the feedback, we'll look into adding search/filter to the long select lists.

The blank email addresses are a known bug, we'll have that corrected in a future update.

Not sure why you were not able to mark and delete those items, even on a small screen the checkboxes should be visible for selection.

dragonxi

we could mark those oprhan dummy email addresses to be deleted by using the checkbox.

however, the server did not let us to delete them
whereas after we had changed their name to
delete@domain we could delete them all.

And just to let you know, instead of putting two mail user requests i.e one for .app and one for .dev for domains such as aceit, and then trying to create email address to each of them, we soon found out better to create email user for .app and then email address to .app and after that email user to .dev and then email address to .dev
i.e. when server had two requests it seemed to put often only one request to queue and in cases it put two requests it seemed to try to get only the first one
i.e
with two object requests only the first one was being served in reasonable time whereas the second one only after very long time
sometimes only after you logged out and logged in after many hours.

That said, having a lot of coffee & tea our guys created the email users and email addresses to proceed.

Thanks for all Opalstack guys for your support!