Re: Voyager versus installed version

2015-06-06 Thread MFPA
Hi


On Saturday 6 June 2015 at 3:17:33 PM, in
, Luca wrote:



> The one thing I miss in Voyager is the chance to
> associate it to the mailto: protocol. I tried every
> hack I am capable of in the Windows registry but still
> I can't get mailto: urls to open in Voyager. I still
> guess it must be possible somehow. I searched around, I
> asked here twice (still asking) but nobody came out
> with a solution so far.

I would have thought not touching the host computer's settings was one 
of the points of a portable app. 

That said, can't you edit the Mailto handler in Windows Explorer via
Tools | Folder Options | Filetypes? And in Firefox via Tools | Options
| Applications?

-- 
Best regards

MFPA  

To steal ideas from one person is plagiarism; 
to steal from many is research.

Using The Bat! v4.0.38 on Windows XP 5.1 Build 2600 Service Pack 3 



Current version is 6.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: Voyager versus installed version

2015-06-06 Thread Rick
>The one thing I miss in Voyager is the chance to associate it to the mailto: 
>protocol. I tried every hack I am capable of in the Windows registry but still 
>I can't get mailto: urls to open in Voyager. I still guess it must be possible 
>somehow. I searched around, I asked here twice (still asking) but nobody came 
>out with a solution so far.

The problem comes because voyager is portable and doesn't make registry entries
The keys you could BACKUP and then play with are
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Clients\Mail\The Bat! Simple MAPI 64-bit
and / or
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Clients\Mail\The Bat! Simple MAPI 32-bit



Current version is 6.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Re: Voyager versus installed version

2015-06-06 Thread Luca
Trash:

> I  have started to try Voyager. There is no documentation comparing it
> to the "full version" (apart from saying it includes all the features)
> 
> I have two basic questions:
> 
> a)  Is  there  any  disadvantage  at  all  of using Voyager as my main
> software,  i.e.  as  the  main software  on  my desktop as well as USB, and
> discarding the installed version altogether -- what will I lose??

The one thing I miss in Voyager is the chance to associate it to the mailto:
protocol. I tried every hack I am capable of in the Windows registry but still
I can't get mailto: urls to open in Voyager. I still guess it must be possible
somehow. I searched around, I asked here twice (still asking) but nobody came
out with a solution so far.

Except for that, I think it's all the same. The installed version betas
usually come out more frequently than Voyager updates but I can live with
that.

> b) Does the E-mail data *have* to be encrypted on Voyager. I am mainly
> interested  in  portability,  and take care of security in other ways.
> Encryption in Voyager would (possibly) make me more susceptible to data
> loss.

I seem to remember that yes, the Voyager database must be encrypted. I'm not
100% sure, though.

-- 
Luca - e-mail: p.stevens at libero.it



Current version is 6.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html


Voyager versus installed version

2015-06-06 Thread Trash
I  have started to try Voyager. There is no documentation comparing it
to the "full version" (apart from saying it includes all the features)

I have two basic questions:

a)  Is  there  any  disadvantage  at  all  of using Voyager as my main
software,  i.e.  as  the  main software  on  my desktop as well as USB, and
discarding the installed version altogether -- what will I lose??

b) Does the E-mail data *have* to be encrypted on Voyager. I am mainly
interested  in  portability,  and take care of security in other ways.
Encryption in Voyager would (possibly) make me more susceptible to data
loss.

-- 
  Aubrey mailto:trash876...@btinternet.com



Current version is 6.6 | 'Using TBUDL' information:
http://www.silverstones.com/thebat/TBUDLInfo.html