Alex Pankratov :
Mar 27, 2015
Ah, nevermind. I can reproduce it locally. I'll follow up in a bit...Darol :
Mar 27, 2015
Hello,Alex Pankratov :
Mar 27, 2015
What do you have in %LocalAppData%\Bvckup2\bvckup2-smtp.log ? If you don't feel like sharing it here, drop me an email instead at support-at-pipemetrics.com.Darol :
Mar 27, 2015
SORRY ABOUT THAT Alex,Alex Pankratov :
Mar 31, 2015
Alright, I got this resolved in a development build and it will be in the next minor release - R73 revision 7 - should be ready to go tomorrow or the day after.Darol :
Mar 31, 2015
Ok, seriously, that was awesome of you. Too many software developers / companies could learn a thing from you. I'll get this purchased very soon. Thank you so much Alex and please continue this work. It is greatly appreciated.Alex Pankratov :
Apr 05, 2015
Resolved in 73.3 - https://www.bvckup2.com/support/forum/topic/539/3286Darol :
Apr 07, 2015
Alex,Darol :
Apr 07, 2015
Meh, never mind.Alex Pankratov :
Apr 07, 2015
I googled a bit and it looks like there is indeed some legwork required on the Outlook's service end to make this work. Something to do with on-premises vs. off-premises servers and account bindings... not my domain by any means, though it does look like a default lock-down that can be removed if needed.damobeanrod :
Jul 27, 2017
To revive an old thread I found it was failing for my Outlook account... Clicking more and changing the from: parameter fixed the issue. From was noreply@bvckup or something along those lines. I set it to myemailaddress@outlook.com.au and it would then allow me to send... Presumably they recently added a restriction that you must send from a domain you are authoritative for... I haven't tested bvckup@outlook.com.au mind you. So they may even restrict to smtp alias.