Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
I am a very grateful user of Backup and migrate, and it works flawlessly in a shared server.
Nevertheless, I am also usint it in a local server (without mail server) configured to send mail through SMTP Autentication Support module.
All the text mails generated by drupal are sent properly, but the backup mails generated by Backup and migrate are not sent.
Could anyone tell me whether Backup and Migrate is compatible with STMP Authentication Protocol?
Thanks
Comment | File | Size | Author |
---|---|---|---|
#4 | backup_migrate-1146746-swiftmailer_integration-4.patch | 2.45 KB | PatchRanger |
Comments
Comment #1
samyue CreditAttribution: samyue commentedyes, I have same problem. Looks like Backup module still use the php's mail() function to send email.
Comment #2
kkrehl CreditAttribution: kkrehl commentedLooks like the problem still persists.
Comment #3
Anonymous (not verified) CreditAttribution: Anonymous commentedThis is still a problem.... can anyone help?
Comment #4
PatchRanger CreditAttribution: PatchRanger commentedI have found a workaround: integration with Swiftmailer, which has support for both SMTP and attachments simultaneously.
Please review the patch, which tends to eliminate the issue by such integration - so anyone who is interested in sending via SMTP will use Swiftmailer while the module continues to work as expected for others who aren't interested in such functionality.
How it works:
1) Apply the patch.
2) Download and install Swiftmailer basing on its installation instructions.
3) Setup Swiftmailer as default mail system.
4) Configure Swiftmailer via its UI.
5) Get rid of SMTP Autentication Support module as it is not needed anymore.
That's it! Now you will get your backups to your mailbox, which are sent through SMTP server of your choice.
Hope it is going to be incorporated into B&M code base.
Comment #5
FranciscoLuz CreditAttribution: FranciscoLuz commentedApplying the patch and following the instructions at #4 fixed the issue.
Comment #6
DamienMcKennaFYI even the backup failure/success messages are sent directly via the mail() function, so I opened a new issue to replace it with drupal_mail(): #2498179: Use drupal_mail() for system notifications
Comment #7
couturier CreditAttribution: couturier as a volunteer commentedIs this patch ready to be ported? Note that it may need to be rewritten based on the newest 7.x-3.2 release.
Comment #8
DamienMcKennaThe patch still applies cleanly to the 7.x-3.x branch.
Comment #9
couturier CreditAttribution: couturier as a volunteer commentedLooks like users in comments #4 and #5 applied the patch successfully. Do we need more reviews?
Comment #10
DamienMcKennaComment #11
Alex Andrascu CreditAttribution: Alex Andrascu at Intellix commentedRTBC anyone please ?
Comment #12
DamienMcKennaI'd really like someone to explain whether this is still needed after #2498179: Use drupal_mail() for system notifications was committed. Thanks.
Comment #13
couturier CreditAttribution: couturier as a volunteer commentedSwiftmailer is in beta for D8 but has had no new recommended releases in a year. It does appear that someone is still working on D8 development versions, but I am in favor of closing this feature request given the ever-increasing need for a stable Backup & Migrate release for D8 and the limited resources to devote to duplicating functionality that already exists, as you pointed out.
Comment #14
DamienMcKennaClosing this feature request would be the wrong approach to take just because there's a D8 version available. Lets see what the testbot says and go from there.
Comment #15
BrankoC CreditAttribution: BrankoC as a volunteer commentedIn 7.x-3.x, Warning: mail(): Multiple or malformed newlines found in additional_header in mime_mail->send() was committed. That patch replaces mail() by drupal_mail() for mailing out back-ups. Would that fix this problem?