mirror of
https://github.com/pelican-dev/panel.git
synced 2026-07-16 04:03:50 +03:00
Panel mail settings has username as a mandatory field #149
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Gr4Ss on GitHub (Aug 29, 2024).
Originally assigned to: @Boy132 on GitHub.
Current Behavior
When setting up an SMTP Servers via the panel interface, the 'Username' is a mandatory field.
Filling in a username in this case will allow the config to be saved but causes errors when trying to send a (test) mail.
Expected Behavior
Username to be optional in case the mail server requires no authentication
By editing the .env file directly, it is possible to leave the username/password blank and get a working mail config for mail servers that require no username/password.
Steps to Reproduce
Panel Version
1.0.0-beta8
Wings Version
n/a
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
No response
Is there an existing issue for this?
@rmartinoscar commented on GitHub (Aug 29, 2024):
Hey setting up mails without any user/password or certificate screams bad practice !
You shouldn't ever do that so i doubt The Pelican Team will ever make those fields optional.
@Gr4Ss commented on GitHub (Aug 29, 2024):
There are legit reasons where you might want to use unauthenticated SMTP, e.g. when using postfix on localhost to forward the mails. Or OPNSense's postfix plugin doesn't even support user authentication currently...
It isn't like a mail server without authentication immediately means there is a mail server sitting open to the internet.