"From address for email from Webmin" doesn't accept root mail and "Return to previous page" does not actually return to the right page

Submitted by yngens on Sun, 10/28/2018 - 15:31

To replicate the issue:

  • Create and then delete a test virtual server.
  • Go to Webmin > Webmin Configuration > Sending Email.
  • Change the From address for email from Webmin option from Default to Addressand try to put just root and click on Save button.
  • You will see the error message: Failed to save mail sending options : Missing or incorrectly formatted from address. So my first request is to please allow this field accept the root or local user value.
  • Click on Return to previous page button and you will see that instead of returning to previous page it will offer you to delete the test virtual server deleted in the first step. I am not sure if this is Webmin or Authentic Theme issue, but I believe there is interference of some kind of cache here.
Status: 
Closed (fixed)

Comments

Submitted by andreychek on Sun, 10/28/2018 - 15:32

Assigned: Unassigned »

Submitted by yngens on Sun, 10/28/2018 - 15:34

Body: View changes

Correcting badly formatted message. Virtualmin.com needs a good WYSIWYG panel.

Submitted by yngens on Sun, 10/28/2018 - 16:12

Setting webmin_from=root in the /etc/webmin/mailboxes/config works fine though, so they only UI form does is not accepting the root user as sender.

Submitted by JamieCameron on Tue, 10/30/2018 - 00:48

In the UI you need to enter it like root@domain.com

Submitted by yngens on Tue, 10/30/2018 - 04:40

I know that Jamie, however the hostname can change over time and it will be real mess if we have to also need to remember to change to default Webmin mail. I believe the page has to accept local mails like root, so users could set it once and forget. Why don't you change the script in such a way that if there is no @ sign it considers it as local mail address?

Submitted by JamieCameron on Wed, 10/31/2018 - 00:21

Ok, I'll allow addresses without a domain in the next Webmin release.

Submitted by IssueBot on Thu, 02/28/2019 - 09:07

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.