Well...poodle noodle. First, Ron is a prince among men heading to knighthood for setting up this almost perfect test. Not knowing how the alias concept works, I used the other credentials, login in perfectly, three times in fact. Name of my inbox, a frankly stunning amount of options. so as a test, I chose inbox, was presented with the understandable information that my inbox is empty..quite wonderful so far tough. so, next test would be to try sending an email. all the fields worked, there are associated editors with all three of the browsers I use here at shellworld, with my getting the correct status line fields, along with my editor for spell checking the body...dancing with joy, or I was until I reached the send button. This, for reasons that make no sense whatsoever, has been scripted, as in Javascripted to be disabled from the keyboard. Lynx, which many, speaking personally, think of as a text only browser, actually has a keystroke to manage this..it has an html5 plug in too, but I digress. so, I engaged the keystroke on the submit button, getting a 510 server error. When I raised the JavaScript friendly lever, moving next to the links as an a chain browser, I learned why. here the coding on that send button just says button, as in not intended to work with the entre key. final JavaScript friendly more graphical browser, elinks, which can be built that way shows the button coded as harmless. from a web contact access guideline standpoint, that hints at someone using JavaScript 0, which is an absolute shame because from my simple test absolutely everything else works. Way to reach their support team? This could be quite an amazing tool, perhaps there is a configuration that fixes this issue? With appreciation, Kare