Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow multiple SMTP servers #2271

Closed
GitHubUser4234 opened this issue Nov 23, 2016 · 8 comments
Closed

Allow multiple SMTP servers #2271

GitHubUser4234 opened this issue Nov 23, 2016 · 8 comments

Comments

@GitHubUser4234
Copy link
Contributor

Maybe I'm all wrong, but it seems like multiple SMTP servers aren't supported even though the documentation says so?

  • Have tried with the current master to set multiple hosts separated by semicolon for the 'mail_smtphost' parameter, but sending a test mail fails as the whole hosts string is treated as one host which obviously can't be connected to

  • In the source code it doesn't look like Swiftmailer's multiple hosts features are used, e.g. Swift_FailoverTransport or Swift_LoadBalancedTransport...

Hope I'm wrong though as I would like to use the feature. Maybe someone can shed some light on this? Thanks :)

@nickvergessen
Copy link
Member

Yeah, I didn't know this was ever supported. But shouldn't be too hard to bring it back in general I guess.
The only problem I see is, that all servers have to work with the same credentials etc.

If that is expected and enough, it can be easily added to

$transport = \Swift_SmtpTransport::newInstance();

@GitHubUser4234
Copy link
Contributor Author

Hm, so was it actually there before and somehow got scrapped? :D

Yeah, for a start just covering what is written in the documentation sounds sufficient. And individual credentials, protocols etc. for each server could then for example be added as a further enhancement.

@nickvergessen
Copy link
Member

Hm, so was it actually there before and somehow got scrapped? :D

I'm not sure, if so it got killed with the introduction of swiftmailer in 8.0

@MorrisJobke
Copy link
Member

@nickvergessen I would say we don't support it. Because it doesn't seem to work for a longer time, which means it isn't used at all :( Instead of adding more complexity here I would vote for adjusting the documentation.

@GitHubUser4234
Copy link
Contributor Author

I would say we don't support it. Because it doesn't seem to work for a longer time, which means it isn't used at all :( Instead of adding more complexity here I would vote for adjusting the documentation.

Well thing is, it at least works with only one SMTP server. But that doesn't mean backup servers wouldn't be needed. When emails can't be sent out due to SMTP server failure, it indeed can have a critical impact especially on large scale projects. Having the option to employ backup servers isn't really that special, last but not least that's also why email providers offer more than one SMTP server for backup.

And as discussed above, it is not all that much effort to re-implement this feature. We would really need this on the long run, and I'm sure there are other Nextcloud users who would welcome the feature.

@MorrisJobke
Copy link
Member

And as discussed above, it is not all that much effort to re-implement this feature. We would really need this on the long run, and I'm sure there are other Nextcloud users who would welcome the feature.

We are happy about pull requests. But many people here are already doing other stuff that is also needed. As this doesn't work right now I would not rate this a bug but a wrong documentation. I will make this a enhancement ticket then :)

@MorrisJobke MorrisJobke changed the title Multiple SMTP servers not working Allow multiple SMTP servers Jan 26, 2017
@GitHubUser4234
Copy link
Contributor Author

We are happy about pull requests. But many people here are already doing other stuff that is also needed. As this doesn't work right now I would not rate this a bug but a wrong documentation. I will make this a enhancement ticket then :)

Perfect, thanks :D

@nextcloud-bot nextcloud-bot added the stale Ticket or PR with no recent activity label Jun 20, 2018
@nextcloud-bot nextcloud-bot mentioned this issue Sep 14, 2018
@skjnldsv skjnldsv added the 1. to develop Accepted and waiting to be taken care of label Jun 12, 2019
@ghost ghost removed the stale Ticket or PR with no recent activity label Jun 12, 2019
@szaimen
Copy link
Contributor

szaimen commented May 21, 2021

I am going to close this since there doesn't seem to be a lot of interest (no upvotes) and no respond since around 2 years. Please reopen if you still want to implement this.

@szaimen szaimen closed this as completed May 21, 2021
@szaimen szaimen added 0. Needs triage Pending check for reproducibility or if it fits our roadmap Nice to have and removed 1. to develop Accepted and waiting to be taken care of 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Jun 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants