After a profile has been run, SyncBackPro can email the log file. This is especially useful when SyncBackPro is located on a remote machine. The log file can optionally be sent as an email attachment.
In today's world of junk email, many email servers are configured to reject any email that appears to be spam. If your email server is rejecting your log email please make sure you have filled out the settings correctly, e.g. valid To and From addresses are used. Also, when using the autodiscover/autoconfig option, it is more likely to be treated as spam.
This profile settings page can use and create shared settings.
•Email the log file after the profile has run: To email the log file, enable this option. If the profile is disabled then no log will be sent.
Sending Server Connection Details
•Email Service: If you use a public email service, e.g. GMail, then you may be able to choose it from the drop-down list. If so, some of the settings will be set automatically for you. Note that you may still need to set things like the login username as they are unique to your account.
•Server Type: For most people this should be left as SMTP. However, if you're using a Microsoft Exchange server then you can change this as appropriate. If you are using Microsoft Exchange 2007 or newer then do not use the WebDAV option unless you are using an old version of Microsoft Exchange (2000 or 2003). If the autodiscover/autoconfig is enabled then this setting is not required and so not available.
•Hostname: This is the hostname of your email server, e.g. smtp.mailserver.com. If you're using Microsoft Exchange then enter just the hostname and not the URL (also set the Server Type as appropriate). If you do not specify a hostname then SyncBackPro will use the hostname specified in the MX record for the To email address (the first one if more than one is specified). If the autodiscover/autoconfig is enabled then this setting is not required and so not available. If the search icon 
is visible (you are using SMTP and have supplied a To email address), and pressed, then SyncBack will try and find the hostname by using the To email address. If found then it will prompt if you want to use the hostname it has found. If you know which hostname you should use then it is recommended to use that instead. This is only for cases where you do not know what hostname to use.
•To: The email address to send the log file to. Variables can be used. You can enter multiple email addresses by separating them with semi-colons or commas, e.g. [email protected]; [email protected]. If the search icon is visible (you are using SMTP and have supplied a To email address), and pressed, then SyncBack will check to see if the To email address is valid (if you provide multiple email addresses then only the first is used). To do this it connects to the SMTP server and checks if the email address is correct. Note that many email servers will accept any email address, so this may only be useful if the server explicitly states the email address is invalid.
•From: The email address from which the log file has been sent. Variables can be used. Typically you would put your own email address here. Note that some email servers may reject the email if it is not from a valid email address or an email address on that server.
•Subject: The subject to use for the email. You can use variables, e.g. %PROFILENAME%, in the subject, e.g. Log file for %PROFILENAME%. The subject is part of the shared settings, so it is advisable to use variables.
•Use autodiscover/autoconfig to send directly: For some email services (typically ones you manage and can configure), you can enable this option and not require many of the other settings (Server Type, Hostname and login details). This can greatly simplify configuration and not require a password that may change. You can check if this setting can be used by setting To and From and then clicking the Test Email Settings button. This option is only available if the Server Type is SMTP and a linked account is not being used. See the section below for details.
•Login: If you must login to your email server (and if you are using Microsoft Exchange then you must) then select Must login to email server and enter your login username and password below. Note that some servers require a login whereas others may fail if you do attempt to login. Check with your email provider or systems administrator. Some email services have 2-step verification for added security. In this case the password may need to be an application specific password and not your actual password. Refer to your email services documentation on how to create an application specific password. Due to spam, most email servers now require you to login. SyncBackPro can login to email servers that require a username and password in clear-text, NTLM, CRAM-MD5, or MSN. If the autodiscover/autoconfig is enabled then these settings are not required and so not available.
oUsername: The username used to login. This is only enabled if Login is set to Must login to email server. You can use a secret for the username.
oPassword: The password used to login. This is only enabled if Login is set to Must login to email server. If your password has spaces in it, and you're not using Exchange, then you may need to enter it with double-quotes. For example, if your password is abc 123 then enter "abc 123" as the password. If you are using Gmail, and have 2FA, then this is the App password you created. You can use a secret for the password.
oPrompt for the password when run (profile will fail if run unattended): If this option is enabled then every time the profile is run SyncBackPro will prompt you for the password. If the profile is being run unattended, then no prompt will be displayed and the profile run will fail.
•Test Email Settings: When clicked SyncBackPro will use the settings above to send a test email. Note that it will only email the summary page (if using HTML logs) and not the entire log as the test is to make sure the settings are correct.
Gmail (without 2FA)
If you are using a Gmail account, and are not using 2FA (Two Factor Authentication) with your Google Account, the following explains how to configure it so it can be used with SyncBackPro:
•Click Settings link in top-right
•Go to Forwarding and POP/IMAP tab in Settings
•Enable Enable POP for all mail (even mail that's already been downloaded) and Enable IMAP
•Change When messages are accessed with POP to keep Gmail's copy in the Inbox
•Click Save Changes
•You also need to allow access via less secure apps. To do this visit https://myaccount.google.com/lesssecureapps
The problem with Gmail is that it sometimes forgets these settings and so you may have the problem of SyncBackPro saying there are no emails. This is because the Gmail POP server is saying there aren't any emails because the Enable POP for all mail setting is sometimes "forgotten" by Gmail. Also, sometimes Gmail doesn't appear to delete emails that SyncBackPro asks it to delete.
Gmail (with 2FA)
If you are using 2FA (Two Factor Authentication) with your Google Account then you need to create an App Password for SyncBack. You then use that password instead of your Google password.
How does the "Use autodiscover/autoconfig to send directly" option work? It takes the domain name from the To email address and looks up its MX record via a DNS lookup. That gives SyncBack the SMTP server for that email address. If there is no MX record then it will use the domain name itself.
If this option does not work (and it does not for major email services like GMail, Hotmail, etc.) then there can be several reasons:
•This option is unlikely to work unless the SMTP server can whitelist IP addresses, and your IP address is in that whitelist. This also means you (the sender) need a fixed IP address.
•If the SMTP server is using DKIM, SPF, DMARC, etc. then it is likely to fail. SMTP servers are either connected to directly by email clients (like SyncBack) or by other email servers. To avoid spam, when connected to by clients, they rely on username and password authentication. When connected to by other servers (that do not use usernames and passwords) they will use other techniques, e.g. DKIM, SPF, etc. to validate the connection.
•You are sending to multiple recipients. In this case it will use the first senders SMTP server to send to all recipients, which will probably fail if they are not using the same domain.
•Other security restrictions or requirements.
Note that if it does not work then this is due to the configuration of the receiving email server (based on the To email address), e.g. DKIM or SPF settings, blacklisting, , etc.
All Content: 2BrightSparks Pte Ltd © 2003-2024