[rohangirishrao]

As interrupted transfers are restarted correctly, the interrupted email notification to the user is mostly irrelevant and can lead to confusions. In the interest of debugging and wanting to keep track of such events, the notification has been parametrized.

Additionally, as mentioned in issue #31, there can be a race where the AD look up for the email address fails because the system is shutting down.

Changed:

• New config option SendInterruptedNotification (AtxCommon/Serializables/ServiceConfig.cs), default false
• SendTransferInterruptedMail() in AtxService/Email.cs only sends the mail if this option is enabled, which can be set in the config.common.xml file.

Testing:

• Tested with default option false and interrupted a transfer by stopping the service in the middle of one. No email.
• Enabled the notification option, resumed and interrupted again -> the mail was delivered.

I'm not sure this is a breaking change, as the option doesn't need to be set in the config.

[ehrenfeu]

Actually I disagree this fixes #31. It only makes sending the respective email optional, if that option is enabled the issue described there will still occur. Also see the related comment there.

☝️Note: this does NOT mean this PR is pointless or wrong! It's just about that it's not a fix for the referenced issue.