Steve Atkins wrote:
Of those, the only thing that's actually associated with the inbound mailbox is
the incoming mail server.
As you suggest, key it to "feedback(_at_)feedback(_dot_)<incoming server name>".
But a critical bit of UI design is that it should be clear to the user whether
something will happen, or not. So for this to be workable the MUA needs to be
able to configure itself to show or hide the TiS button (or grey it out, or
whatever UI idiom you like).
The charm of using an MX record to configure this is that the MUA can do an MX
lookup to know whether to show or hide the button. That's pretty clean, and if
I were coding an MUA I'd be happy to do it that way, but it's not necessarily a
_trivial_ thing to add to a codebase, especially via plugin, so it's worth
considering.
From the perspective of code base, checking for an A record for
"feedback.<incoming server name>" would be simpler. The MTA doesn't
need to use DNS to deliver, and you really don't want the MUA to be
establishing direct connections anyway. Fixed route to whereever in the
MTA.
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg