next »

[jelv1]

I can access the default mailbox now, but it is still showing as "(pending)" which makes me suspect that all is not well. Isn't that what we see when a component refresh hasn't completed?

[jelv1]

Problem 42137 Unable to create redirects containing a dot following next gen email rollout

How soon will this be fixed? I deleted a redirect with a full stop by mistake and need to recreate it.

Also, were mailbox names and redirects restricted to 16 characters before? Given that I would expect that prefixes in the format firstname.surname are quite common, 16 characters seems hellish short. A nephew of mine has a 17 character name (including a full stop) - and he only has a 5 character surname!

[bpullen]

Problem 42137 Unable to create redirects containing a dot following next gen email rollout

How soon will this be fixed? I deleted a redirect with a full stop by mistake and need to recreate it.

It's being worked on as we speak. Incidentally we've just picked up on another issue that's preventing customers from logging into mailboxes with dots in them

Also, were mailbox names and redirects restricted to 16 characters before? Given that I would expect that prefixes in the format firstname.surname are quite common, 16 characters seems hellish short. A nephew of mine has a 17 character name (including a full stop) - and he only has a 5 character surname!

Yes, I think this was the case before.

[paulcobb]

Problem 42137 Unable to create redirects containing a dot following next gen email rollout
It's being worked on as we speak. Incidentally we've just picked up on another issue that's preventing customers from logging into mailboxes with dots in them

Has 42137 issue been resolved Bob?

[jelv1]

I've just recreated the redirect containing a full stop that I had deleted by accident.

[bpullen]

Has 42137 issue been resolved Bob?

Yes, as supported by John's findings, it has been fixed. The login issue has been fixed too.

[JSchlackman]

Why can we no longer use upper case characters in a mailbox password? This was possible on the old system. If I try to do that now, I get the message "Invalid password, please read the instructions below". The instructions do indeed only list lower case as valid characters - but why?

For the record, my existing mailbox uses a mix of upper and lower case, and it still works - at least for now.

[bpullen]

Absolutely no idea why the form validation was built like this. I'll do some digging and see if anyone has any valid reasons as to why this shouldn't be allowed any more.

Edit: Digging done. No reason why there should be this limitation so we're looking to fix things as part of another problem our developers are working on (regarding the maximum limit for mailbox passwords).