In article <haberg-0710062008570001@c83-250-192-69.bredband.comhem.se>,
haberg@math.su.se (Hans Aberg) wrote:

> One filter feature lost was the distinction between manual and
> automatic filtering. I had Eudora set up so that personal incoming
> mail belonging to a list was sorted into the inbox, and after that, I
> just applied manual sorting to get it into the list mailbox. This I
> cannot do in Mail.

I assume that you mean a private reply to a message on a list. True,
there is no manual triggering of rules. However, it is just about as
easy to drag a message to a folder as it is to click a button or pull
down a menu to trigger a filter or rule.

> For me, the main thing was to get over the mail. My mailboxes were on
> several MB's though.

When I transfered from Emailer to Mail.app (about the same time that
MTNW was carbonized so it could run natively under OS X), I had no
problems transferring messages to mail from emailer, so long as emailer
itself was on the system and that Classic could be run.

I transferred the address book by exporting it as LDAP and importing it
into Address Book.

> I do not want to do another port, though.

I don't blame you; I don't want to do that either

--
Stop Mad Cowboy Disease: Impeach the son of a Bush.

In article <michelle-978B18.18384507102006@news.west.cox.net>, Michelle
Steiner <michelle@michelle.org> wrote:

> > One filter feature lost was the distinction between manual and
> > automatic filtering. I had Eudora set up so that personal incoming
> > mail belonging to a list was sorted into the inbox, and after that, I
> > just applied manual sorting to get it into the list mailbox. This I
> > cannot do in Mail.
>
> I assume that you mean a private reply to a message on a list.

If there is a private reply on a list, it is common to reply to both the
person and the list. I then set up an automatic, but not manual, sorting
rule so that one or both replies would end up in the inbox, overriding the
rule that sorts it into the list mailbox. As it is not valid with manual
sorting, doing that latter would send the mail into the list mailbox. Very
convenient.

Now I still have that rule, but sorting by hand must be done via the GUI,
and then one must know where each list mailbox is.

In fact, I used this method also not only for lists, but for other
frequent exchange mailboxes. This way, I do not need to keep track of
where the mailbox is.

Now, I use a mixture for frequent exchange mailboxes. Some I sort directly
into the mailbox, but then it may be easy to miss private mail. - I can
see it in the GUI, but some mailboxes are hidden by another window used
for displaying the list mailboxes. Others, I sort into the inbox, but then
I need to sort it by hand via the GUI into the final destination mailbox.

> True,
> there is no manual triggering of rules.* However, it is just about as
> easy to drag a message to a folder as it is to click a button or pull
> down a menu to trigger a filter or rule.

Not really, if one has a large volume. I have several hundred email boxes
to sort for. :-)

> > For me, the main thing was to get over the mail. My mailboxes were on
> > several MB's though.
>
> When I transfered from Emailer to Mail.app (about the same time that
> MTNW was carbonized so it could run natively under OS X), I had no
> problems transferring messages to mail from emailer, so long as emailer
> itself was on the system and that Classic could be run.
>
> I transferred the address book by exporting it as LDAP and importing it
> into Address Book.

Even though I had an address book, I really didn't use it. Instead I copy
the address from the latest exchange. It is safest, in view of address
changes.

> > I do not want to do another port, though.
>
> I don't blame you; I don't want to do that either

One advices is to have a mail program which stores the email messages as
is when they come in, instead of converting to an internal format. Then
the messages can always be retrieved, would one need to migrate.

--
Hans Aberg

In article <michelle-978B18.18384507102006@news.west.cox.net>, Michelle
Steiner <michelle@michelle.org> wrote:

> > One filter feature lost was the distinction between manual and
> > automatic filtering. I had Eudora set up so that personal incoming
> > mail belonging to a list was sorted into the inbox, and after that, I
> > just applied manual sorting to get it into the list mailbox. This I
> > cannot do in Mail.
>
> I assume that you mean a private reply to a message on a list.

If there is a private reply on a list, it is common to reply to both the
person and the list. I then set up an automatic, but not manual, sorting
rule so that one or both replies would end up in the inbox, overriding the
rule that sorts it into the list mailbox. As it is not valid with manual
sorting, doing that latter would send the mail into the list mailbox. Very
convenient.

Now I still have that rule, but sorting by hand must be done via the GUI,
and then one must know where each list mailbox is.

In fact, I used this method also not only for lists, but for other
frequent exchange mailboxes. This way, I do not need to keep track of
where the mailbox is.

Now, I use a mixture for frequent exchange mailboxes. Some I sort directly
into the mailbox, but then it may be easy to miss private mail. - I can
see it in the GUI, but some mailboxes are hidden by another window used
for displaying the list mailboxes. Others, I sort into the inbox, but then
I need to sort it by hand via the GUI into the final destination mailbox.

> True,
> there is no manual triggering of rules.* However, it is just about as
> easy to drag a message to a folder as it is to click a button or pull
> down a menu to trigger a filter or rule.

Not really, if one has a large volume. I have several hundred email boxes
to sort for. :-)

> > For me, the main thing was to get over the mail. My mailboxes were on
> > several MB's though.
>
> When I transfered from Emailer to Mail.app (about the same time that
> MTNW was carbonized so it could run natively under OS X), I had no
> problems transferring messages to mail from emailer, so long as emailer
> itself was on the system and that Classic could be run.
>
> I transferred the address book by exporting it as LDAP and importing it
> into Address Book.

Even though I had an address book, I really didn't use it. Instead I copy
the address from the latest exchange. It is safest, in view of address
changes.

> > I do not want to do another port, though.
>
> I don't blame you; I don't want to do that either

One advices is to have a mail program which stores the email messages as
is when they come in, instead of converting to an internal format. Then
the messages can always be retrieved, would one need to migrate.

--
Hans Aberg

In article <haberg-0810060754300001@c83-250-192-69.bredband.comhem.se>,
haberg@math.su.se (Hans Aberg) wrote:

> > > One filter feature lost was the distinction between manual and
> > > automatic filtering. I had Eudora set up so that personal
> > > incoming mail belonging to a list was sorted into the inbox, and
> > > after that, I just applied manual sorting to get it into the list
> > > mailbox. This I cannot do in Mail.
> >
> > I assume that you mean a private reply to a message on a list.
>
> If there is a private reply on a list, it is common to reply to both
> the person and the list.

Not for me, it isn't. If the reply is public, it goes to the list; if
it is private, I send it only to the person.

I get annoyed when I get a private reply that is the same as the public
reply to the list. There is no need for me to receive it twice.

--
Stop Mad Cowboy Disease: Impeach the son of a Bush.

In article <haberg-0810060754300001@c83-250-192-69.bredband.comhem.se>,
haberg@math.su.se (Hans Aberg) wrote:

> > > One filter feature lost was the distinction between manual and
> > > automatic filtering. I had Eudora set up so that personal
> > > incoming mail belonging to a list was sorted into the inbox, and
> > > after that, I just applied manual sorting to get it into the list
> > > mailbox. This I cannot do in Mail.
> >
> > I assume that you mean a private reply to a message on a list.
>
> If there is a private reply on a list, it is common to reply to both
> the person and the list.

Not for me, it isn't. If the reply is public, it goes to the list; if
it is private, I send it only to the person.

I get annoyed when I get a private reply that is the same as the public
reply to the list. There is no need for me to receive it twice.

--
Stop Mad Cowboy Disease: Impeach the son of a Bush.

In article <michelle-D8D6B9.05375308102006@news.west.cox.net>, Michelle
Steiner <michelle@michelle.org> wrote:

> > If there is a private reply on a list, it is common to reply to both
> > the person and the list.
>
> Not for me, it isn't. If the reply is public, it goes to the list; if
> it is private, I send it only to the person.

It is standard on all the technical lists I am on, including GNU. Part for
attention, part for list delivery delays.*Turns out it is hard to avoid
the practice.

> I get annoyed when I get a private reply that is the same as the public
> reply to the list.*

Be aware of that not sending a duplicate on a list where it is normal
practice might be viewed as rude, as though you want to avoid*personal
exchange.

> There is no need for me to receive it twice.

Some do not like the extras copies. So one may want to have extra filters
to sort them away.*I have done that with some lists.

In the end, it is simplest just not bothering about duplicaes. In the
past, data space was expensive, people even cleaning up their mailboxes
yearly. Nowadays, it is not worth the effort, at least not for me.

--
Hans Aberg

In article <michelle-D8D6B9.05375308102006@news.west.cox.net>, Michelle
Steiner <michelle@michelle.org> wrote:

> > If there is a private reply on a list, it is common to reply to both
> > the person and the list.
>
> Not for me, it isn't. If the reply is public, it goes to the list; if
> it is private, I send it only to the person.

It is standard on all the technical lists I am on, including GNU. Part for
attention, part for list delivery delays.*Turns out it is hard to avoid
the practice.

> I get annoyed when I get a private reply that is the same as the public
> reply to the list.*

Be aware of that not sending a duplicate on a list where it is normal
practice might be viewed as rude, as though you want to avoid*personal
exchange.

> There is no need for me to receive it twice.

Some do not like the extras copies. So one may want to have extra filters
to sort them away.*I have done that with some lists.

In the end, it is simplest just not bothering about duplicaes. In the
past, data space was expensive, people even cleaning up their mailboxes
yearly. Nowadays, it is not worth the effort, at least not for me.

--
Hans Aberg

In article <haberg-0810060754300001@c83-250-192-69.bredband.comhem.se>,
haberg@math.su.se (Hans Aberg) wrote:

> One advices is to have a mail program which stores the email messages as
> is when they come in, instead of converting to an internal format. Then
> the messages can always be retrieved, would one need to migrate.

Which is why I have switched to forwarding all of my mail to my gmail
account, and using the mail.app as my front end.

In article <haberg-0810060754300001@c83-250-192-69.bredband.comhem.se>,
haberg@math.su.se (Hans Aberg) wrote:

> One advices is to have a mail program which stores the email messages as
> is when they come in, instead of converting to an internal format. Then
> the messages can always be retrieved, would one need to migrate.

Which is why I have switched to forwarding all of my mail to my gmail
account, and using the mail.app as my front end.