Re: 8.5.6 MSI files
Hello Maxim, Sunday, July 8, 2018, 1:02:35 AM, you wrote: > https://www.ritlabs.com/download/the_bat/thebat_64_8-5-6.msi > Problems of previous versions that arose after sending a message should be > resolved in 8.5.6. Please confirm. I can confirmed the problem is resolved. Thank you, Jerry -- Best regards, Ethanmailto:supp...@thedesk.ca Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Voyager v.8.5.4.1
Luca: > > Maxim Masiutin: > > > > > Could you pleast try Voyager v.8.5.4.1 from > > > https://www.ritlabs.com/download/the_bat/voyager_install-8-5-4-1.exe > Oh no. Again! This time the Oauth process stops after accepting the password, > when asking that The Bat would like to read and send email, view contacts etc. > Now these are the possibilities [...] I don't know if this is of any importance: the culprit is an IMAP account hosted by Gmail, the type @my.domain.it (not @gmail.com) where my.domain.it is a domain hosted by Google. These are my email settings for that account in TB: Mail server: imap.gmail.com User: myn...@my.domain.it Authentication: OAUTH (using web browser) Connection: Secure to dedicated port (TLS) - Port 993 SMTP server: smtp.gmail.com Authentication: Perform SMTP authentication Same user/password as for mail retrieval Connection: Secure to dedicated port (TLS) - Port 465 The last Voyager working version with that account is 8.2.4.3. Problem only occurs with all following versions. -- Luca - e-mail: p.stevens at libero.it Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.5.6 MSI files
Hello Curt, Sunday, July 8, 2018, 9:20:32 AM, you wrote: > I received no such warning. I saw smartscreen.exe launch (in > processes), then evaporate, which is normal behavior. > All was really terribly "normal." Thank you. We will keep our regular (normal) code signing certificate then rather then buying an EV-certificate. -- Best regards, Maxim Masiutin Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Voyager v.8.5.4.1
Luca:
> Maxim Masiutin:
>
> > Could you pleast try Voyager v.8.5.4.1 from
> > https://www.ritlabs.com/download/the_bat/voyager_install-8-5-4-1.exe
>
> This time everything seems fine with my Gmail IMAP accounts. Thank you.
Oh no. Again! This time the Oauth process stops after accepting the password,
when asking that The Bat would like to read and send email, view contacts etc.
Now these are the possibilities (sorry if the English button labels are
different, I'm translating from the Italian version):
- The "Accept" button seems to work but the same request keeps on coming again
and again, I'm not getting anywhere by pressing it repeatedly.
- The "Refuse" button works, the response is correct ("You denyed access to
the application"), but from here I can't go anywhere, because...
- The "Cancel" button is available but it always brings me back me to the
permission request.
- The close window button [X] on the upper right corner of the window works,
but it brings me back to the Google "choose account to login" request. From
here the cancel button works, and it loops back to the same request.
- The Ok button is never available, in any of the above situations (always
grayed out)
My only possibility to keep on working with email is to kill the Voyager
process with Windows Task Manager and downgrade, reinstalling version 8.2.4.3.
This is getting weird.
--
Luca - e-mail: p.stevens at libero.it
Current beta is 8.5.4.4 | 'Using TBBETA' information:
http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Voyager 8.5.0.1
Hello Luca, >> > Please try Voyager 8.5.0.1: >> > https://www.ritlabs.com/download/files3/the_bat/voyager_install-8-5-0-1.exe >> Btw, which Antispam plugin can be used with Voyager? Antispamsniper >> is not accepted as a plugin. > It should work, I've always been using Antispamsniper with Voyager. Already got here the hint that only the 32 bit version of ASS works with Voyager. And because I for many years only had the 65 bit at my PC, I even did not think of the 32 bit version at my 64 bit tablet. :-) -- Kind regards, Gunivortus The Bat! Professional 64 bit, version 8.5.4 Windows Pro 64 bit version 10, build nr. 17134 NordVPN vs. 6.11.12.0 Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Voyager 8.5.0.1
Gunivortus Goos: > > Please try Voyager 8.5.0.1: > > https://www.ritlabs.com/download/files3/the_bat/voyager_install-8-5-0-1.exe > > Installed and running fine so far. > Btw, which Antispam plugin can be used with Voyager? Antispamsniper > is not accepted as a plugin. It should work, I've always been using Antispamsniper with Voyager. -- Luca - e-mail: p.stevens at libero.it Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.5.6 MSI files
Hello Maxim, I received no such warning. I saw smartscreen.exe launch (in processes), then evaporate, which is normal behavior. All was really terribly "normal." -- Best regards, Curt Akin using TheBat! 8.5.6 under Windows 10.0 Build 17074 with HughesNet Gen5 satellite Internet. Sunday, July 8, 2018, 2:10:40 AM, you wrote: > Hello Curt, > Sunday, July 8, 2018, 8:33:25 AM, you wrote: >> U No shutdown after send. > Did you receive the "SmartScreen" warning when you have installed this MSI? > I have found out that if a developer has a standard code signing > certificate, some time will be needed for the application to build > "trust" with the SmartScreen. Microsoft affirms that an Extended > Validation (EV) Code Signing Certificate allows to skip this period of trust > building. > https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-smartscreen-extended-validation-ev-code-signing-certificates/ > According to the information from the link, extended validation > certificates allow the developer to immediately establish reputation > with SmartScreen. Otherwise, the users will see a warning like > "Windows Defender Smartscreen prevented an unrecognized app from > starting. Running this app might put your PC at risk.", with the two > buttons: "Run anyway" and "Don't run". > https://blogs.msdn.microsoft.com/vsnetsetup/2013/01/09/windows-smartscreen-prevented-an-unrecognized-app-from-running-running-this-app-might-put-your-pc-at-risk/ > Another Microsoft resource from the second link (above) states the > following (quote): "Although not required, programs signed by an EV > code signing certificate can immediately establish reputation with > SmartScreen reputation services even if no prior reputation exists > for that file or publisher. EV code signing certificates also have a > unique identifier which makes it easier to maintain reputation across > certificate renewals." > My question is how long does it take for The Bat! new MSI files to > build "trust" with the Smartscreen? Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.5.6 MSI files
Hello Curt, Sunday, July 8, 2018, 8:33:25 AM, you wrote: > U No shutdown after send. Did you receive the "SmartScreen" warning when you have installed this MSI? I have found out that if a developer has a standard code signing certificate, some time will be needed for the application to build "trust" with the SmartScreen. Microsoft affirms that an Extended Validation (EV) Code Signing Certificate allows to skip this period of trust building. https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-smartscreen-extended-validation-ev-code-signing-certificates/ According to the information from the link, extended validation certificates allow the developer to immediately establish reputation with SmartScreen. Otherwise, the users will see a warning like "Windows Defender Smartscreen prevented an unrecognized app from starting. Running this app might put your PC at risk.", with the two buttons: "Run anyway" and "Don't run". https://blogs.msdn.microsoft.com/vsnetsetup/2013/01/09/windows-smartscreen-prevented-an-unrecognized-app-from-running-running-this-app-might-put-your-pc-at-risk/ Another Microsoft resource from the second link (above) states the following (quote): "Although not required, programs signed by an EV code signing certificate can immediately establish reputation with SmartScreen reputation services even if no prior reputation exists for that file or publisher. EV code signing certificates also have a unique identifier which makes it easier to maintain reputation across certificate renewals." My question is how long does it take for The Bat! new MSI files to build "trust" with the Smartscreen? -- Best regards, Maxim Masiutin Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 8.5.6 MSI files
Hello Ira, Sunday, July 8, 2018, 8:53:14 AM, you wrote: > Thank you so much, this fixes that most annoying problem. One of the most annying and hard-to-diagnose problem that we ever had. -- Best regards, Maxim Masiutin Current beta is 8.5.4.4 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
