UPDATE! UPDATE! UPDATE3
Just had a breakthrough! Although my ISP have not contacted me yet, having configured Calibre to send via gmail and outlook successfully, I thought I'd go back and try my ISP configuration again.
It wouldn't work on their advised smtp setting of mail.btinternet.com (which is the same as their incoming server and which it was at and worked prior to 2 weeks ago). I changed that bit only to smtp.binternet.com AND also changed to the same in my emClient ..... (still on port 25 for both though) .... sent a Test email, which came through WITHOUT me having to run the Diagnostics tab on my emClient to get the Test Email.
AND I have just sent myself and a friend a mobi file via those ISP settings too! Several times! Going through my ISP does still generate the Verify email from Amazon before the book is actually received onto the device though.
So, either my ISP changed from incoming mail.btinternet.com to smtp.btinternet.com (which it actually was before a year or so ago) and haven't told anyone
OR
they've temporarily switched the server to smtp.btinternet.com because it wasn't working via their advised mail.btinternet.com setting
It'll be interesting to see what they have to say.
Furthermore, it now leaves me with the following options via Calibre:
1. Send via my ISP but everyone I send to will receive a Verify email from Amazon and will have to click Verify within in within 48hrs of generation to actually get the file onto their kindle (otherwise, they won't and they'll have to tell me so I can re-send it)
2. Send via gmail and book arrives without having an Amazon email to verify first (in which case I'll have to tell all my group members and friends to add my gmail address to their Personal Doc Settings/Safe Sender
3. Same as 2 but with my outlook.com address.
So I will also be able to question my ISP and Amazon on why the Amazon verify email is required when a file is sent out via my ISP but not via gmail or outlook.
AND
Why the Amazon email only allows a 48hr window in which to respond or it blocks it from the device it was sent to
I'll update again if anything changes again.
|