synchronise outlook 2007 between desktop & laptop

M

Martin ©¿©¬

Hi
I'm looking for a program to synchronise outlook 2007 beteen my
desktop & laptop.
Desktop windows 7, laptop vista
 
V

VanguardLH

Martin said:
Hi
I'm looking for a program to synchronise outlook 2007 beteen my
desktop & laptop.
Desktop windows 7, laptop vista

Drop POP accounts. Move to IMAP accounts.

http://en.wikipedia.org/wiki/Post_office_protocol
http://en.wikipedia.org/wiki/Imap

If your current ESP (email service provider) doesn't include IMAP access
to your account then you'll have to find an ESP that does.

If you really need to stick with POP access then configure your e-mail
clients (all of them) to:

- Leave messages on server.
- Delete messages N days after download.

By default, POP deletes a message once it has been retrieved from the
server. Change the option to NOT delete the message (by leaving it on
the server). You must have this same option configured the same by all
your POP clients. If just one of them is configured for the default (of
RETRieve and DELEte) then that message won't be there for the other POP
clients to find.

Eventually you want old POP messages to get removed from your mailbox.
If you want to keep them, you should've have moved them into a different
folder (but then only the client where you moved the e-mail will have a
copy unlike IMAP where you can have all clients subscribe to the same
folder which is actually defined up on the server). POP only has a
concept of a mailbox (which you see as the Inbox when using the webmail
client to access your account). There are no commands in POP to create
or change focus to a folder. If, say, you want to keep old e-mails
around for a month, then configure "Delete 30 days after download" on
all your clients. If you want to leave all e-mails in your mailbox,
never do any cleanup, and risk its corruption, then don't bother with
this cleanup option.
 
M

Martin ©¿©¬

Hi Vanguard
I have been unable to reply to you sooner

I have changed my outlook 2007 from Pop to Imap & now I seem to have
several .pst files.

How would I find out which is the correct one?
 
V

VanguardLH

Martin said:
I have changed my outlook 2007 from Pop to Imap & now I seem to have
several .pst files. How would I find out which is the correct one?

POP and Exchange accounts get rolled into one message store (.pst file).
Each HTTP account gets its own message store. Each IMAP account gets
its own message store.

Right-click on the root node in the folder tree for a message store.
Look at its properties. Under there you find where is its .pst file.


Note: Is there a reason why you configured your newsreader (Forte Agent)
to generate an illegally syntaxed value for your From header?
 
M

Martin ©¿©¬

POP and Exchange accounts get rolled into one message store (.pst file).
Each HTTP account gets its own message store. Each IMAP account gets
its own message store.

Right-click on the root node in the folder tree for a message store.
Look at its properties. Under there you find where is its .pst file.


Note: Is there a reason why you configured your newsreader (Forte Agent)
to generate an illegally syntaxed value for your From header?

At the time (a few years back) I did not want to get spammed out of I
would be interestedexistance & have not bothered with it since.
I you can offer a better suggestion I would be interested
 
V

VanguardLH

Martin said:
At the time (a few years back) I did not want to get spammed out of I
would be interestedexistance & have not bothered with it since.
I you can offer a better suggestion I would be interested

Proper syntax is still '"commentstring" <emailaddress>', something like
'"Martin" <[email protected]>'. That doesn't mean you have to
display a valid e-mail address. As you know, you could munge it or use
a completely bogus one. If you use a munged one, don't bother adding
"nospam" to it as spambots have several strings they parse out for such
common munges. If you use a bogus one, decide on one that is not
currently registered (otherwise you are pointing spambots at a someone's
domain) or cannot be registered. One trick is to use .invalid as the
TLD (top-level domain) instead of .com, .net, .org, and the like.
Another is to use characters that aren't allowed in domain names.
Remember that even a domain that not registered now might be in the
future, and it might then be hosted somewhere. It is rude to point
spambots at someone's domain to afflict them with the spam that you
energized at them.

If you look at the From header in my posts, it is a bogus e-mail address
*BUT* it is in valid syntax for an e-mail address. There is no .LH
top-level domain so any domain that I specify won't be registered.

It is possible to specify a legitimate e-mail address (i.e., a defined
and active account) but eliminate getting any non-human generated spam
targeting it. Simply open an account that is ONLY used for when you
want to take discussions offline of Usenet and into e-mail. Then define
a server-side rule that discards any e-mails that don't contain a
specific string, called a passcode, in the Subject header. In the
signature of your posts, you note "E-mail: Append <passcode> to Subject
to avoid immediate delete." The passcode can be any string you like as
long as it isn't anything that would normally be used in the Subject
header, like "&MRTN-38#". Any e-mails sent to that account that don't
have the passcode in the Subject get immediately deleted by your rule.
Of course, there are e-mail accounts where you can set a server-side
option to make the account exclusive in that only e-mails from known
senders (in your address book) are accepted - except they typically dump
the "bad" e-mails in a Junk folder rather than actually delete them.
Spambots don't know how to read instructions in a signature. Any spams
sent to you won't have your passcode in the Subject header. Spambots
harvest e-mail addresses, not the bodies of posts, so the spammer won't
ever see your instructions on how to circumvent your passcode filter.
Even if the spambots did collect the bodies of posts, spammers aren't
going to wade through them all to read instructions. If some malcontent
in the newsgroup submits your [unmunged] e-mail address to a mailing
list, that source won't be adding the passcode to the Subject so you
still won't get their spam that the malcontent was hoping to afflict you
with. So it is possible to use a legit e-mail address. Just use an
account that is only for taking newsgroup discussions offline to e-mail,
add a passcode filter on the Subject header, and tell users how to add
the passcode if they don't want to run afoul of your filter.

If you never want to take Usenet discussions offline via e-mail (as I
do) then don't bother opening an e-mail account for use only with
newsgroups (or forums) and using a passcode filter to avoid spam. Just
use a bogus From header but *do* use a properly syntaxed value. Also,
there are some NNTP servers that won't accept posts that do not contain
a validly syntaxed e-mail address in the From header and another reason
to use a proper value for the From header. Unless you want to get into
ISO encoding of the commentstring portion of the From header, only use
ASCII-7 characters; otherwise, your use of upper-ASCII characters often
results in not having the effect you wanted. Instead of seeing your
wonderfully chosen set of upper-ASCII characters, other users may simply
see square boxes representing non-displayable characters.
 
M

Martin ©¿©¬

This new address,

Is this the address I use to post to newsgroups, or my reply to
address?

I was considering something like Martin ©¿©¬ <[email protected]>
--
Martin
©¿©¬



Martin said:
At the time (a few years back) I did not want to get spammed out of I
would be interestedexistance & have not bothered with it since.
I you can offer a better suggestion I would be interested

Proper syntax is still '"commentstring" <emailaddress>', something like
'"Martin" <[email protected]>'. That doesn't mean you have to
display a valid e-mail address. As you know, you could munge it or use
a completely bogus one. If you use a munged one, don't bother adding
"nospam" to it as spambots have several strings they parse out for such
common munges. If you use a bogus one, decide on one that is not
currently registered (otherwise you are pointing spambots at a someone's
domain) or cannot be registered. One trick is to use .invalid as the
TLD (top-level domain) instead of .com, .net, .org, and the like.
Another is to use characters that aren't allowed in domain names.
Remember that even a domain that not registered now might be in the
future, and it might then be hosted somewhere. It is rude to point
spambots at someone's domain to afflict them with the spam that you
energized at them.

If you look at the From header in my posts, it is a bogus e-mail address
*BUT* it is in valid syntax for an e-mail address. There is no .LH
top-level domain so any domain that I specify won't be registered.

It is possible to specify a legitimate e-mail address (i.e., a defined
and active account) but eliminate getting any non-human generated spam
targeting it. Simply open an account that is ONLY used for when you
want to take discussions offline of Usenet and into e-mail. Then define
a server-side rule that discards any e-mails that don't contain a
specific string, called a passcode, in the Subject header. In the
signature of your posts, you note "E-mail: Append <passcode> to Subject
to avoid immediate delete." The passcode can be any string you like as
long as it isn't anything that would normally be used in the Subject
header, like "&MRTN-38#". Any e-mails sent to that account that don't
have the passcode in the Subject get immediately deleted by your rule.
Of course, there are e-mail accounts where you can set a server-side
option to make the account exclusive in that only e-mails from known
senders (in your address book) are accepted - except they typically dump
the "bad" e-mails in a Junk folder rather than actually delete them.
Spambots don't know how to read instructions in a signature. Any spams
sent to you won't have your passcode in the Subject header. Spambots
harvest e-mail addresses, not the bodies of posts, so the spammer won't
ever see your instructions on how to circumvent your passcode filter.
Even if the spambots did collect the bodies of posts, spammers aren't
going to wade through them all to read instructions. If some malcontent
in the newsgroup submits your [unmunged] e-mail address to a mailing
list, that source won't be adding the passcode to the Subject so you
still won't get their spam that the malcontent was hoping to afflict you
with. So it is possible to use a legit e-mail address. Just use an
account that is only for taking newsgroup discussions offline to e-mail,
add a passcode filter on the Subject header, and tell users how to add
the passcode if they don't want to run afoul of your filter.

If you never want to take Usenet discussions offline via e-mail (as I
do) then don't bother opening an e-mail account for use only with
newsgroups (or forums) and using a passcode filter to avoid spam. Just
use a bogus From header but *do* use a properly syntaxed value. Also,
there are some NNTP servers that won't accept posts that do not contain
a validly syntaxed e-mail address in the From header and another reason
to use a proper value for the From header. Unless you want to get into
ISO encoding of the commentstring portion of the From header, only use
ASCII-7 characters; otherwise, your use of upper-ASCII characters often
results in not having the effect you wanted. Instead of seeing your
wonderfully chosen set of upper-ASCII characters, other users may simply
see square boxes representing non-displayable characters.
 
V

VanguardLH

Martin said:
This new address,

Is this the address I use to post to newsgroups, or my reply to
address?

I was considering something like Martin ©¿©¬ <[email protected]>

It's been a long time since I last trialed Forte Agent. In the account
definition, you should be able to specify a legitimately syntaxed e-mail
address. It might point to a domain that can never exist (e.g., the TLD
is not assignable), illegal chars are used in the domain if the
newsreader doesn't forbid them, it could be a munged address, or be
bogus one but valid syntax. example.com and <anything>.invalid can
never be assigned and are special cases used for testing. No mail
server can be assigned the example.com domain and none of them are
allowed to use the .invalid TLD. The one you gave is legitimate in that
it is validly syntax but can never be used because of the .invalid TLD.
I have, however, run across an NNTP server that wouldn't let me use a
TLD of .invalid.

There should also be somewhere you identify your moniker (i.e., your
identity's name). While upper ASCII chars are allowed (although not
displayed by some newsreaders), I'd stay away from them. No one is
going to be able to find your old posts based on just "Martin" as your
name since it isn't unique enough to point at mostly just your posts.
The upper-ASCII characters (as well as non-alphanumeric characters) are
usually discarded in searches. If it isn't important to you that others
can find your old posts then your new posts are probably just as
unimportant.
 
M

Martin ©¿©¬

Thanks for all your help Vanguard
I wiil go to the Forte newsgroup and see what they recommend
 
L

LiamLiam

Hey there,

I had the same problem a few months abck. I wanted found a lot of stuff on
slipstick.com - you should check this out. I tested CodeTwo Public Folders
- it worked great, but you have to buy minimum 3license base package (not
two). I bought 3 then and now I sync my outlook with three machines.

It lets you sync all outlook items in real time - great software.
http://www.codetwo.com/public-folders/

Liam
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top