Item12240: Email Test tab doesn't work in configure

Email Test tab didn't work, but the validate button under WebMaster email did. I'm not sure if it is intentional for this feature to be moved to the new validation framework or not.

IMHO the validate button should still be located under an independent tab, because it's validating many things (admin email address, server info, etc).

-- KipLubliner - 13 Nov 2012

Yup... Confirmed. Seems to have broken in a recent checkin.

-- GeorgeClark - 13 Nov 2012

Thanks for the report. The feature will indeed move, though I didn't intend to break it yet. The new version already does more testing than the old, though I have a couple of things to move to make it complete.

-- TimotheLitt - 13 Nov 2012

The old test tab has now been removed. The e-mail testing architecture has changed. Mail auto-configure is used for inital setup (and provides a detailed log). Where the old test guessed based on config parameters and topics, the new approach is to probe the server and figure out what it wants. The UI is in flux, so this isn't obvious. George Clark and I are working on that...

In the common case, it's much simpler: enter email address, name, (usually server address) & click auto-configure. You should then click test, but it's a formality. Done. With one more click, you get a (custom) self-signed S/MIME certificate activated.

If you want more control, you do more work.

The {!WebMasterEmail} test button is intended to test that email address (though with debug on, you can get a lot of debug data displayed - enough that post-configuration, it will replace the old test). If everything is working, you just get "accepted for delivery". If not, you get diagnostics.

The same button will appear with other e-mail addresses in Foswiki & the extensions. It's associated with a generic EMAILADDRESS checker; EMAILADDRESS fields (a .spec file datatype) get (or their private checkers inherit) it.

So the primary purpose for that button is to validate that the associated e-mail address is valid. Secondary is to test. (But it's a good test...)

I'm going to close this task - the work I mentioned is on-going under other items, and I think this update should address your concern.

Feel free to re-open if it does not.

Thanks again for trying things out and taking the time to file the report.

-- TimotheLitt - 08 Dec 2012

Commenting is disabled while not logged in