Endurance POP3 -vs- EudoraPro3: Now Incompatible

[RayRoy]

My site had a flawless Automatic Migration on June 9th. Thank You.!.
-however-
About one week later, all my POP3 Email Accounts stopped being able
to receive any emails... Previously they were PowWeb Perfect...

Reported the issue to Endurance TechSupport but they have been unable
to comprehend the simple issue involved here, nor have they escalated
it to anyone who can comprehend it.

It's a simple issue:

EudoraPro v3 is a 16-bit email client, used by folks who perfer not to use
Win~XP whatsoever. It's a very flexible and safe emailer. It thrives when
used inside IBM's OS/2 Warp4 Operating System.

There are other 16-bit Email clients as well, used by many: Pegasus v3 and
Arachne v1 DOS Browser/Emailer for example.

None of those can accept an email Account Username which contains "@" symbol.

ie:
Account Username: Webmaster@MyDomain.Net --- cannot be properly parsed.
Account Username: Webmaster --- can be properly parsed.

Endurance now requires POP3 Usernames to be the Complete Email Address...

Hence:
POP3 Email Address: Webmaster@MyDomain.Net
-becomes-
POP3 Account Username: Webmaster@MyDomain.Net

This is a common issue with many Mail-Hosting services. Most of them are aware
of the inability of 16-bit email softwares to allow "@" symbols in Usernames.
So they accomodate us easily, by setting a simple option in their servers which
has alternates in lieu of "@". They allow + : % and @ symbols interchangeably.

ie: They allow us to login using any of these alternativers:

Examples:
POP3 Account Username: Webmaster+MyDomain.Net
POP3 Account Username: Webmaster:MyDomain.Net
POP3 Account Username: Webmaster%MyDomain.Net

And EudoraPro v3 loves it. Pegasus loves it. Arachne loves it. And I love it.

Can anyone reading this, from Endurance Staff, please escalate this and fix it?

Thank you.

[RayRoy]

Elsewhere in this Forum, was Posted the end-all-panacea for "setting up" our
new migrated OPS Panel's email accounts: It was in Forum Thread:

http://forum.powweb.com/showthread.php?t=67252

Which suggested we use this new PowWeb Email Tutorial Link:

http://www.powweb.com/info/tutorial.bml?id=17&step=4&displaystyle=full&mode=steps

However, I have found there are several incorrect items in that Tutorial:

(Using Win~XP MSIE 6.0 Browser, BTW)...

Among them:

(1) "Simple-vs-Advanced Mode" buttons do not appear in the new OPS Panel.

(2) "Example Images" shown, do not look anything like what we see in new OPS Panel.

(3a) "!" Icons (to view access information for a specific mailbox) do NOT exist.
(3b) Data expected in example image does not appear anywhere in OPS Panel:
http://www.powweb.com/images/tutorial/tut_email_sim_04.gif

(4a) All Client-Specific (eg: Eudora 6) POP3 Setups are incorrect, which state:
[quote]
"If you have previously configured e-mail programs to your mailbox using only the name of the mailbox ("mailbox_name" with no "@domain.com"), continue to use that mailbox name."
[unquote]

(4b) If a person uses only the ("mailbox_name" with no "@domain.com") it will
give you a False-POP3-Login-mailcheck: ie: Shows "No Mail" when infact, there
*is* mail awaiting pickup and can be seen/retreived *ONLY* if a person uses
the *FULL* username login setup as: ("mailbox_name@domain.com")

(5a) Many earlier 16-bit email clients (eg: EudoraPro v3 and Pegasus v3) cannot
accept a setup Username containing an "@" symbol. Hence, users with those 16-bit
client softwares will be misled into the trap of False POP3 Checks of item (4b).

(5b) Most other Host-Providers are aware of this and CORRECTLY option their POP3
servers to allow Username logins using + : % or @ symbols instead:

Examples:
("mailbox_name@domain.com") --- will not work in 16-bit email clients
("mailbox_name+domain.com") --- Works OKAY in 16-bit email clients
("mailbox_name:domain.com") --- Works OKAY in 16-bit email clients
("mailbox_name%domain.com") --- Works OKAY in 16-bit email clients

(6a) SMTP (send) Authentication is incorrectly optioned at Endurance's server.
The four standard SMTP AUTH protocols are:
(1) CRAM-MD5
(2) DIGEST-MD5
(3) LOGIN
(4) PLAIN

(6b) Endurance server offers only TWO of the FOUR standard SMTP-Auth protocols:
ie:
(3) LOGIN
(4) PLAIN

(6c) Therefore, many email clients cannot login, if they expect SMTP to offer:
(1) CRAM-MD5
(2) DIGEST-MD5

(6e) The Endurance SMTP server will respond with error message:
"Server: 504 CRAM-MD5 authentication mechanism not supported"
-or-
"Server: 504 DIGEST-MD5 authentication mechanism not supported"

Summary:

Endurance needs to:
(a) Fix the Email Tutorial to show the actual OPS Panel layouts.
(b) Fix the False POP3 Login-mailcheck issue.
(c) Enable their POP3 Server to accept alternate +:%@ symbols as other Hosts do.
(d) Enable their SMTP Server to offer all *FOUR* standard SMTP AUTH Protocols.

If Endurance cares, and, would do these things, they would see 99% of the user's
email problems resolved quickly.

Again: I am requesting that an Endurance Staff Person escalate these issues to
their POP3 & SMTP Server Engineers to fix it. And, advise their TechSupport of
proper-response to our many Tickets, instead of their mis-informed responses.

Thank you.