If we get more customer reports saying that this is a major problem then we will, of course.

However, we only have two complaints at the moment which unfortunately isn't sufficient to warrant development time to put a notice on. Whilst this is only a small change, it would still need to go through a full peer review and testing process which will take many man-hours, regardless of the size of the change.

In reply to a post by bentrimble:

If we get more customer reports saying that this is a major problem then we will, of course.

However, we only have two complaints at the moment which unfortunately isn't sufficient to warrant development time to put a notice on. Whilst this is only a small change, it would still need to go through a full peer review and testing process which will take many man-hours, regardless of the size of the change.

Ah! so only two of us are affected. Point taken

Well, I believe that it's a service wide issue but so few people want to replace an alias with a redirect by the method you've found fault with means that it's classed as low priority

In reply to a post by bentrimble:

Well, I believe that it's a service wide issue but so few people want to replace an alias with a redirect by the method you've found fault with means that it's classed as low priority

Hi Ben

Errrr! my case was not replacing an alias with a redirect but actually creating a redirect in the first place was failing and the create alias > delete alias > create redirect. Was the workaround you found was the way to create the redirect.

Sorry if I misunderstood what you had discovered about the bug but what you say above did not make immediate sense to me based on the origin of the problem for me.

I rather think it was me that introduced that red herring here which was one reason I knew of where creating a redirect would fail.

Have you finally managed to create the redirect? I don't think you ever answered the question I asked in the same post:

In reply to a post by jelv:

Could you confirm that in the Re-direct name box you only entered the mailbox name (excluding the @username.plus.com).

I had a few PM's with jelv to identify the specific issue he was seeing (replacing an alias with a redirect definitely is a tad funky), but I'm having no problems at all creating test redirects on your account - you can see test and test2. Can you have another go for me please - create a couple of redirects and leave them on file so I can go back and have a look what has happened?

Hi jelv & Ben

Firstly I did try on the mailbox to just use the mailbox name as Jelv suggested but that failed as well!

I will try again to redirect the mailbox by using both just the mailboxname and [email protected] in the first entry and see what happens??? But for the record each time I have tried there was no evidence that I had created them i.e. no list for you to see Ben. That was the reason for the original opening of this thread!

Yes, I could see you had created test & test2 as "the system" sent me emails telling me of the changes but I got no such emails when trying to create them.

Will advise shortly that I have done this

You need to just use mailboxname not [email protected] in the left field, I think that's what you're doing wrong.

In reply to a post by bentrimble:

You need to just use mailboxname not [email protected] in the left field, I think that's what you're doing wrong.

Hi Ben

Right I used just the mailbox name in the first field and the destination mailbox full address in the second field Note - this is an external email address i.e. not PlusNet

For the record this is what I tried before as per jelv's suggestion.

All that happens when I click to add that redirect the page refreshes with the "add a redirect" with no sign that the redirect has been created!!!

Why don't you either send him the exact details you are putting in each field, or better still send him a screen shot before you click OK or whatever it is on the screen?