Wooo! Update to Voyager nearing release

[Segfault]

I've pleasure in announcing the imminent release of a slight update to
Voyager for Orpheus subscribers. I'm just testing it now.

As many of you will know, Voyager was originally intended to work with
Argonet and thus only knew about a single domain - ie. it assumed that all
emails automatically ended in @argonet.co.uk

This is not necessarily the case with Orpheus, as we allow people to choose
from multiple domains for their email accounts.

However, an unfortunate side-effect of this was that, after you'd run the
VoyUpdate utility to convert Voyager to Orpheus compatibility, any
additional user accounts you may have had got the domains confused so that
your second or subsequent email addresses may have become incorrectly
tagged to the wrong domain.

In addition, since the closure of Argonets server, people have been unable
to enable or disable extra email addresses correctly.

To rectify this, I've killed two birds with one stone and written a
stand-alone utility which will let people add and remove email accounts
from Posty as well as hopefully fix the problem with existing email
addresses becoming linked with the wrong domains.

The solution will be two part; the utility (called !VoyEmail) which will
enable/disable accounts and a new version of Posty, which will fix
(hopefully) the bug where extra email addresses are changed.

I'm hoping to release both updates in the next few days - although if
you're impatient, you can email me and try it out.

I'm not sure if everyone reads argonet.acorn.voyager, so please feel free
to pass this message onto any Voyager users you know who might not see this
announcement.

Paul

[Dave Stratford]

Post by Segfault
I've pleasure in announcing the imminent release of a slight update to
Voyager for Orpheus subscribers. I'm just testing it now.

<snip>

Post by Segfault
To rectify this, I've killed two birds with one stone and written a
stand-alone utility which will let people add and remove email accounts
from Posty as well as hopefully fix the problem with existing email
addresses becoming linked with the wrong domains.
The solution will be two part; the utility (called !VoyEmail) which will
enable/disable accounts and a new version of Posty, which will fix
(hopefully) the bug where extra email addresses are changed.
I'm hoping to release both updates in the next few days - although if
you're impatient, you can email me and try it out.

Thanks Paul, but will !Calypso be corrected as well?

Dave

[Segfault]

Post by Dave Stratford
Thanks Paul, but will !Calypso be corrected as well?

Unfortunately, Calypso was never an official Argonet project, but something
Jason Tribbeck started writing. You'd probably have to contact him about
it, as I don't have access to the source code for that one.

AFAIK it was just an email fetcher so, depending upon where it picks up the
various settings from, it /may/ be possible to change it quite easily. The
standard Voyager !POPFetch was pretty easy to convert - in fact I don't
think it needed converting at all, once the rest of Voyager had been made
Orpheus compatible.

However, emailing Jason is probably your best bet, or checking his website
at http://www.tribbeck.com/

regards,
Paul

[Dave Stratford]

Post by Segfault

Post by Dave Stratford
Thanks Paul, but will !Calypso be corrected as well?

Unfortunately, Calypso was never an official Argonet project, but
something Jason Tribbeck started writing. You'd probably have to contact
him about it, as I don't have access to the source code for that one.

Oh. Sorry, I wasn't aware of that. For some reason When I click on the
green mail-fetch light it calls calypso which then just hangs and gives me
an error message. To actually collect email I have to go into
!Voyager.apps.transports and click on !POP3Fetch, which, you'll have to
admit, is somewhat unfriendly.

Dave

[Nick Roberts]

Post by Dave Stratford

Post by Segfault

Post by Dave Stratford
Thanks Paul, but will !Calypso be corrected as well?

Unfortunately, Calypso was never an official Argonet project, but
something Jason Tribbeck started writing. You'd probably have to
contact him about it, as I don't have access to the source code for
that one.

Oh. Sorry, I wasn't aware of that. For some reason When I click on
the green mail-fetch light it calls calypso which then just hangs and
gives me an error message. To actually collect email I have to go
into !Voyager.apps.transports and click on !POP3Fetch, which, you'll
have to admit, is somewhat unfriendly.

That should be easy enough to change, given the overall architecture of
Voyager.

Quit !Voyager, & try the following:

Open up Voyager's Transports folder, and then open the !CalPOP3
directory - there should be a file in there called !Vixen. Rename this
file to !Vixen0.

Close !CalPOP3 and open the !POP3Fetch directory. There should be two
text files in there, one called !Help, and the other called something
like Old!Vixen, or !Vixen0, or similar. Change the name of this file to
!Vixen. The close !POP3 Fetch and restart Voyager - when you connect it
should use POP3Fetch rather than Calypso.

If there is no candidate for a !Vixen file inside !POP3Fetch, save the
following text to the directory as !Vixen:

----------- Start Here -----------
vixen
author © Argo Interactive 1996-1998
name Email Fetcher
id 00000011
help This is the Voyager Email fetcher
enable 1

files
mailrun !Run
web
disable 0000000a

led
help This is the Voyager Email fetcher.|MClick SELECT to start fetching POP3 email.
string Mail fetch
---------------- End Here ------------

[Dave Stratford]

Post by Nick Roberts
That should be easy enough to change, given the overall architecture of
Voyager.
----------- Start Here -----------
vixen
author © Argo Interactive 1996-1998
name Email Fetcher
id 00000011
help This is the Voyager Email fetcher
enable 1
files
mailrun !Run
web
disable 0000000a
led help This is the Voyager Email fetcher.|MClick SELECT to start
fetching POP3 email. string Mail fetch ---------------- End Here
------------

Thank you, this worked a treat.

Dave

[Rosemary Miskin]

Post by Dave Stratford
To actually collect email I have to go into
!Voyager.apps.transports and click on !POP3Fetch, which, you'll have to
admit, is somewhat unfriendly.

You can soon fix that: go into !Voyager.Transports You'll see !Calpop3 and
!Pop3fetch, inter alia.

Inside !Calpop3, rename the file !Vixen (to anything - I use x!Vixen)
and inside !Pop3fetch, identify the text file that used to be called !Vixen,
and restore that name.

It should then all work.

Rosemary

[Tennant Stuart]

Post by Segfault
I've pleasure in announcing the imminent release of a slight update
to Voyager for Orpheus subscribers. I'm just testing it now.
As many of you will know, Voyager was originally intended to work with
Argonet and thus only knew about a single domain - ie. it assumed that
This is not necessarily the case with Orpheus, as we allow people to
choose from multiple domains for their email accounts.
However, an unfortunate side-effect of this was that, after you'd run
the VoyUpdate utility to convert Voyager to Orpheus compatibility, any
additional user accounts you may have had got the domains confused so
that your second or subsequent email addresses may have become
incorrectly tagged to the wrong domain.
In addition, since the closure of Argonets server, people have been
unable to enable or disable extra email addresses correctly.
To rectify this, I've killed two birds with one stone and written a
stand-alone utility which will let people add and remove email accounts
from Posty as well as hopefully fix the problem with existing email
addresses becoming linked with the wrong domains.
The solution will be two part; the utility (called !VoyEmail) which will
enable/disable accounts and a new version of Posty, which will fix
(hopefully) the bug where extra email addresses are changed.
I'm hoping to release both updates in the next few days - although if
you're impatient, you can email me and try it out.
I'm not sure if everyone reads argonet.acorn.voyager, so please feel
free to pass this message onto any Voyager users you know who might not
see this announcement.

That's excellent news Paul, though I was wondering who this guy Segfault
is, who has been messing about with Mr.Vigay's software... ;-)


Tennant Stuart