Re: 8.2.0.4 cannot use imap on gmail
Anyone? Any idea? -- That is not dead which can eternal lie, yet with strange aeons even death may die On Thu, Jan 25, 2018 at 7:04 PM, George Μ. Menegakis <menega...@gmail.com> wrote: > Hello, > > I decided finally to stop using pop3 to get mail and use imap instead. > > Problem is when trying to download mail a google authorization page is > opened and notifies my that I need to authorize The Bat v7 (yes, it says > v7). No matter how many times I press allow it does nothing and finally > fetching mail fails > > [image: Inline image 1] > > Note that in google settings I have ON the setting "Access for less secure > apps". > > From the log: > > 25/01/2018, 18:56:59: IMAP - Connected to IMAP server (imap.gmail.com) > >25/01/2018, 18:56:59: IMAP - Gimap ready for requests from > 2a02:587:2d0f:4a00:ec5e:d681:eec6:f50b d6mb156569965wrc > 25/01/2018, 18:56:59: IMAP - Authenticating (user: "menega...@gmail.com", > method: "XOAUTH2")... > !25/01/2018, 18:57:04: IMAP - Authentication failed, IMAP server response > is "Invalid credentials (Failure)" > 25/01/2018, 18:57:04: IMAP - Authenticating (user: "menega...@gmail.com", > method: "XOAUTH2")... > !25/01/2018, 18:57:08: IMAP - Authentication failed, IMAP server response > is "Invalid credentials (Failure)" > 25/01/2018, 18:57:08: IMAP - Authenticating (user: "menega...@gmail.com", > method: "XOAUTH2")... > !25/01/2018, 18:57:13: IMAP - Authentication failed, IMAP server response > is "Invalid credentials (Failure)" > 25/01/2018, 18:57:13: IMAP - Authenticating (user: "menega...@gmail.com", > method: "XOAUTH2")... > !25/01/2018, 18:57:18: IMAP - Authentication failed, IMAP server response > is "Invalid credentials (Failure)" > 25/01/2018, 18:57:18: IMAP - Authenticating (user: "menega...@gmail.com", > method: "XOAUTH2")... > !25/01/2018, 18:59:11: IMAP - Server reports error. The response is: BYE > Too many commands before auth d6mb156569965wrc > > Please excuse me if this mail is HTML, I' m using the gmail web client > since I cannot use The Bat!!! > > -- > That is not dead which can eternal lie, > yet with strange aeons even death may die > Current beta is 8.2.4.2 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
8.2.0.4 cannot use imap on gmail
Hello, I decided finally to stop using pop3 to get mail and use imap instead. Problem is when trying to download mail a google authorization page is opened and notifies my that I need to authorize The Bat v7 (yes, it says v7). No matter how many times I press allow it does nothing and finally fetching mail fails [image: Inline image 1] Note that in google settings I have ON the setting "Access for less secure apps". >From the log: 25/01/2018, 18:56:59: IMAP - Connected to IMAP server (imap.gmail.com) >25/01/2018, 18:56:59: IMAP - Gimap ready for requests from 2a02:587:2d0f:4a00:ec5e:d681:eec6:f50b d6mb156569965wrc 25/01/2018, 18:56:59: IMAP - Authenticating (user: "menega...@gmail.com", method: "XOAUTH2")... !25/01/2018, 18:57:04: IMAP - Authentication failed, IMAP server response is "Invalid credentials (Failure)" 25/01/2018, 18:57:04: IMAP - Authenticating (user: "menega...@gmail.com", method: "XOAUTH2")... !25/01/2018, 18:57:08: IMAP - Authentication failed, IMAP server response is "Invalid credentials (Failure)" 25/01/2018, 18:57:08: IMAP - Authenticating (user: "menega...@gmail.com", method: "XOAUTH2")... !25/01/2018, 18:57:13: IMAP - Authentication failed, IMAP server response is "Invalid credentials (Failure)" 25/01/2018, 18:57:13: IMAP - Authenticating (user: "menega...@gmail.com", method: "XOAUTH2")... !25/01/2018, 18:57:18: IMAP - Authentication failed, IMAP server response is "Invalid credentials (Failure)" 25/01/2018, 18:57:18: IMAP - Authenticating (user: "menega...@gmail.com", method: "XOAUTH2")... !25/01/2018, 18:59:11: IMAP - Server reports error. The response is: BYE Too many commands before auth d6mb156569965wrc Please excuse me if this mail is HTML, I' m using the gmail web client since I cannot use The Bat!!! -- That is not dead which can eternal lie, yet with strange aeons even death may die Current beta is 8.2.4.1 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Re[2]: TB As System Default on W7-64
On Fri, Sep 30, 2011 at 03:11, Paul Van Noord pau...@for-him.net wrote: 9/29/2011 8:09 PM Hi George, On 9/29/2011 George M. Menegakis wrote: I had hoped with my changing from XP to W7-64 this old problem would have been gone: TB is not [fully] used for MAPI or even just MAILTO. GMM Furthermore on x64 the exchange protocol is not working. I have GMM do some research and it appears to be that in GMM order to be able to use the x64 mapi protocol the bat must be GMM compiled against it. Since Bat is 32bit GMM application and until becomes 64 bit and be compiled against x64 mapi you can forget all that. If this is true why does 4.2.44.2 work perfectly here with Win 7 Pro 64 bit? I assume that's because you haven't installed Office 2010 64 bit. The exerpt below is from http://blogs.msdn.com/b/officedevdocs/archive/2009/11/25/developing-outlook-2010-solutions-for-32-bit-and-64-bit-systems.aspx MAPI Applications for Outlook If your existing 32-bit MAPI application is going to be running on a computer with 64-bit Outlook installed, you will need to rebuild your 32-bit application as a 64-bit application. Outlook 2010 provides a set of MAPI header files that support MAPI applications to work with both 32-bit and 64-bit Outlook 2010. Make sure you download these header files from Outlook 2010: MAPI Header Files and rebuild your MAPI application using these header files. In general, the bitness of the MAPI application must be the same as the bitness of the MAPI subsystem on the computer that the application is targeted to run on. The bitness of the MAPI subsystem, in turn, is determined by and always the same as the bitness of the installed version of Outlook. So if you plan to develop a MAPI application that will be run on computers with either a 32-bit or 64-bit version of Outlook 2010 installed, you will need to build two separate versions of the application, one to work with 32-bit Outlook and one to work with 64-bit Outlook. For more information about MAPI support for 64-bit Outlook, see Building MAPI Applications on 32-Bit and 64-Bit Platforms. Aside from rebuilding MAPI applications, sometimes it's necessary to check the version of Outlook to ensure that a MAPI application calls API elements that are supported by the currently running version of Outlook. To learn how to check the version of Outlook and whether the installed version of Outlook is 64-bit Outlook 2010, see How to: Check the Version of Outlook. Also, to learn how to decipher Outlook version information and the expected values for different parts of a version string for certain released versions of Outlook, see How to determine Outlook version information. Current beta is 5.0.22.15 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Working MAPI on 64 bit Windows
Is there any chance that the users of 64bit windows got a working mapi? TB can't use the 64bit outlook mapi and TB's mapi (32 bit) can't be a primary mapi on an 64 bit windows system. So, are there plans to address this? -- That is not dead which can eternal lie, yet with strange aeons even death may die Current beta is 5.0.12.6 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: Working MAPI on 64 bit Windows
On Mon, May 23, 2011 at 11:58, Dierk Haasis dierk.haa...@dh2publishing.info wrote: Hello George! On Monday, May 23, 2011 at 10:22:34 AM you wrote: Is there any chance that the users of 64bit windows got a working mapi? TB can't use the 64bit outlook mapi and TB's mapi (32 bit) can't be a primary mapi on an 64 bit windows system. Really? I mean, REALLY? So, MAPI on XP doesn't work well if Outlook and ActiveSync are necessary, but upgrading my whole system to W7 64 will not work either? Worse, it would make TB completely useless? The problem is not with windows 7 64bit but with Office 64bit. While I don't blame Ritlabs for this, thing is that in order for a MAPI application to work with 64 bit Outlook installed, the application should be built as 64 bit application. Yeah, I know... snowball in hell. The exerpt below is from http://blogs.msdn.com/b/officedevdocs/archive/2009/11/25/developing-outlook-2010-solutions-for-32-bit-and-64-bit-systems.aspx MAPI Applications for Outlook If your existing 32-bit MAPI application is going to be running on a computer with 64-bit Outlook installed, you will need to rebuild your 32-bit application as a 64-bit application. Outlook 2010 provides a set of MAPI header files that support MAPI applications to work with both 32-bit and 64-bit Outlook 2010. Make sure you download these header files from Outlook 2010: MAPI Header Files and rebuild your MAPI application using these header files. In general, the bitness of the MAPI application must be the same as the bitness of the MAPI subsystem on the computer that the application is targeted to run on. The bitness of the MAPI subsystem, in turn, is determined by and always the same as the bitness of the installed version of Outlook. So if you plan to develop a MAPI application that will be run on computers with either a 32-bit or 64-bit version of Outlook 2010 installed, you will need to build two separate versions of the application, one to work with 32-bit Outlook and one to work with 64-bit Outlook. For more information about MAPI support for 64-bit Outlook, see Building MAPI Applications on 32-Bit and 64-Bit Platforms. Aside from rebuilding MAPI applications, sometimes it's necessary to check the version of Outlook to ensure that a MAPI application calls API elements that are supported by the currently running version of Outlook. To learn how to check the version of Outlook and whether the installed version of Outlook is 64-bit Outlook 2010, see How to: Check the Version of Outlook. Also, to learn how to decipher Outlook version information and the expected values for different parts of a version string for certain released versions of Outlook, see How to determine Outlook version information. Current beta is 5.0.12.5 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: tbmapi.dll
On windows 7 64bit I keep getting !29/04/2011, 15:33:04: FETCH - Cannot connect to the server. Error loading MAPI Library I have opened https://www.ritlabs.com/bt/view.php?id=8653 Is there any chance to get a working MAPI in Windows 7 64 bit ? -- That is not dead which can eternal lie, yet with strange aeons even death may die Current beta is 5.0.9.6 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 5.0.0.142
On Wed, Feb 23, 2011 at 20:08, Maxim Masiutin m...@ritlabs.com wrote: The Bat! 5.0.0.142 BETA is available at http://www.ritlabs.com/download/files3/the_bat/a-5/tb500142.rar What's new in 5.0.0.142 since 5.0.0.141: Exchange doesn't work on the last three versions (and maybe earlier, I haven't checked) https://www.ritlabs.com/bt/view.php?id=8488 -- That is not dead which can eternal lie, yet with strange aeons even death may die Current beta is 5.0.0.142 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Critical: in 5.0.0.140 and 5.0.0.141 send to through Excange server stopped working
Hello, Last thursday I first installed 5.0.0.140 at my work but I hadn't try to send an email. Today I did and the message was kept at outbox. Then I saw finally the account log: 21/02/2011, 09:46:31: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:46:31: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:46:31: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:46:31: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:46:43: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:46:43: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:46:43: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:46:43: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:46:44: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:46:44: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:46:44: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:46:44: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:46:54: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:46:54: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:46:54: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:46:54: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:46:55: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:46:55: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:46:55: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:46:55: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:47:45: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:47:45: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:47:45: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:47:45: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:47:46: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:47:46: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:47:46: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:47:46: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:49:58: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:49:59: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:49:59: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:49:59: SEND - Some messages were not sent - check the log for details 21/02/2011, 09:51:48: SEND - sending mail message(s) - 1 message(s) in queue 21/02/2011, 09:51:49: SEND - connected to the Exchange server MAILVAULT02.xxx.xxx.xx as user menes 21/02/2011, 09:51:49: SEND - connection finished - 0 message(s) sent 21/02/2011, 09:51:49: SEND - Some messages were not sent - check the log for details OTE - Central Domain I installed v5.0.0.141 but the problem wasn't solver. Finally I have to revert to v4.2.33.9 in order to be able to send mail through exchange server. The following are from ex_log.txt v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:31.640 MapiTask:TMapiThread.Execute.DoInitialize EAccessViolation Access violation at address 00BD677A in module 'thebat.exe'. Read of address v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:31.640 Thread Finished:TMapiThread 2652 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:38.218 Thread Started:TMLHTaskThread 5672 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:38.281 Thread Finished:TMLHTaskThread 5672 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:43.093 Thread Started:TMapiThread 4592 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:43.312 MapiTask:TMapiThread.Execute.DoInitialize EAccessViolation Access violation at address 00BD677A in module 'thebat.exe'. Read of address v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:43.328 Thread Finished:TMapiThread 4592 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:44.328 Thread Started:TMapiThread 1632 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:44.484 MapiTask:TMapiThread.Execute.DoInitialize EAccessViolation Access violation at address 00BD677A in module 'thebat.exe'. Read of address v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:44.484 Thread Finished:TMapiThread 1632 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:45.859 Thread Started:TMLHTaskThread 2536 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:45.875 Thread Finished:TMLHTaskThread 2536 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:46.500 Thread Started:TMLHTaskThread 4292 v5.0.0.140 BETA MENEGAKIS/menes 21/02/2011 09:46:46.500 Thread
Re: full list
On Fri, Nov 26, 2010 at 22:19, Rick rick.grunwald.groupm...@gmail.comwrote: * Hello Tbbeta, Could you please make a full list what's left to do to make a release? * Are not the folder compacting and folder purge and compact descriptions redundant? * * No, they aren't. Compact removes deleted messages from a folder permenantly. Purge delete messages from folders, according to rules set in Folder Properties/General (Maximum Number of stored messages Keep messages in the base for X days). Purge Compact, first purges then compacts the folder. Current beta is 5.0.0.131 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Are the v5 alphas private ?
Hello, I keep seeing messages about v5 alpha builds but the links are always down. Is alpha private and if yes could you please move the discussions about it off-list in order not to confuse us about what's private and what's public ? -- That is not dead which can eternal lie, yet with strange aeons even death may die Current beta is 4.2.33.9 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
Re: 4.1.11.9
On Sun, Apr 5, 2009 at 03:41, MAU m...@rancho-k.com wrote: Hello Rick, Also the Attachments glyph now shows the NUMBER of attachments Not until you focus on the Message List pane for the first time and not for all messages. See attachment. And it doesn't work in any virtual folder. Anyway, I wish this new feature was optional. I don't like it neither with the default attachment glyph nor with the one from my Yellowish Icons set. Plus, I don't find it useful for anything. On the contrary I find it very useful provided it works correctly. In all folders and whether the focus is in the message list or not. Current beta is 4.1.11.9 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html
