Please remember to reply to the mailing list, not the original sender:
http://gnudip2.sourceforge.net/#mailinglist
+++++++++
In the web interface, the way that the user's MX configuration
is displayed is non-intuitive:
1. When an MX is set and the user returns to the web
config, that MX is not shown. Only by querying
the nameserver directly do you see that there is
an MX record in place.
2. The semantics of the "secondary MX" button are unclear.
When I first tried to use it, I expected that by
entering a FQDN in the MX box and clicking on the
secondary button, that the entered FQDN would be
listed as the secondary MX. Instead, I went from this:
host 300 IN MX 100 mx-main.example.com.
To this:
host 300 IN MX 200 mx-main.example.com.
host 300 IN MX 100 mx-back.example.com.
As you can see, the priorities in the MX records are
reversed.
I would content that a better interface would be to have two entry
boxes, one for the primary MX and one for the secondary MX.
Furthermore, when the form is displayed, any current MX records
should be displayed in those fields just as the username and
email address are currently displayed.
--
Devin Reade <[EMAIL PROTECTED]>
--
GnuDIP Mailing List
http://gnudip2.sourceforge.net/#mailinglist
