When fixing MGNLMAIL-93, we recognized that we are having some issues when user chooses to send a 'page' in email.

• First of all, 401 and 403 error codes produced when user choose to send a 'page' email if the page is protected despite putting username and password into mail template configuration.
• Secondly HTML Tidy empty the content returned by HTTPClient which failed the content processing in MgnlPageEmail.cleanupHtmlCode(...) function.

To support our minor version release, we decided to fix the ProtocolException and SendConfirmationEMailProcessor first in MGNLMAIL-93, also providing a link to the page within email content, then creating this ticket to follow up with the full feature described below:

The Page option means that we send the content of a page to the user. The internal process reads the page content, pastes the content in the body of the email, and sends the mail to the user.
The page itself does not need to available to the visitor. It's enough that the Magnolia internal process can access the page and get its content. You should be executing the process in a context that provides access to pages.