powermail-discuss Digest #2712 - Monday, October 22, 2007
Re(2): Powermail support (Was: Re: Exporting from PowerMail - all mail is
by "Winston Weinmann" <[EMAIL PROTECTED]>
Re(2): Powermail support (Was: Re: Exporting from PowerMail - all mail is
by "Winston Weinmann" <[EMAIL PROTECTED]>
Re: Powermail support (Was: Re: Exporting from PowerMail - all mail is Un
by "Mikael Byström" <[EMAIL PROTECTED]>
Re: Powermail support (Was: Re: Exporting from PowerMail - all mail is Un
by "Mikael Byström" <[EMAIL PROTECTED]>
Re(2): Powermail support (Was: Re: Exporting from PowerMail - all mail is
by "Winston Weinmann" <[EMAIL PROTECTED]>
----------------------------------------------------------------------
Subject: Re(2): Powermail support (Was: Re: Exporting from PowerMail - all mail
is Unread)
From: "Winston Weinmann" <[EMAIL PROTECTED]>
Date: Sun, 21 Oct 2007 16:53:16 -0500
That is a great idea, and one CTM should have both on its site and in a
Read Me with the installer.
- Winston
Mikael Byström wrote:
>I'd prefer if we had a bug list or something and could point to that.
----------------------------------------------------------------------
Subject: Re(2): Powermail support (Was: Re: Exporting from PowerMail - all mail
is Unread)
From: "Winston Weinmann" <[EMAIL PROTECTED]>
Date: Sun, 21 Oct 2007 17:08:00 -0500
Mikael Byström wrote:
>We on this list are not employed by you, which seems to be the common
>feature for most of the situations you list where you have found this
>approach productive.
The point is not about my trying to influence the discussion list, but
about trying to influence CTM. CTM is "employed" by its users, as we
have paid them for a product.
>While I agree with your position on this particular matter of HTML-
>printing I think you should follow-up directly to CTM if you want to see
>any changes. *Then* you report to the list, if needed.
We have a difference of opinion on strategy. However, I do not have an
plan or program to keep bugging CTM about HTML printing. If they
responded to direct contact I certainly would report that back to the
list, but as you and others have noted, CTM rarely responds, and only by
the mailing list, as far as I can tell.
Regards,
- Winston
----------------------------------------------------------------------
Subject: Re: Powermail support (Was: Re: Exporting from PowerMail - all mail is
Unread)
From: "Mikael Byström" <[EMAIL PROTECTED]>
Date: Mon, 22 Oct 2007 00:19:57 +0200
Winston Weinmann suggested:
>That is a great idea, and one CTM should have both on its site and in a
>Read Me with the installer.
In a Readme? What other products put their buglists there? Isn't an URL
to some kind of online source sufficient?
After all buglists are not primarily around to warn people, but to focus
bug-*fixing*.
I can imagine when an open bugfix list could be of use for the
developers of PowerMail, but as there isn't one in place I assume they
think otherwise or at least that the developers don't find it worth the
effort.
I would think CTM do keep an inhouse buglist for internal use.
Mikael
Tech facts:
PM 5.5.3 Swedish | OS X 10.4.8 | Powerbook G4/400 Mhz | 1GB RAM | 80GB HD
----------------------------------------------------------------------
Subject: Re: Powermail support (Was: Re: Exporting from PowerMail - all mail is
Unread)
From: "Mikael Byström" <[EMAIL PROTECTED]>
Date: Mon, 22 Oct 2007 00:11:18 +0200
Winston Weinmann suggested:
>That is a great idea, and one CTM should have both on its site and in a
>Read Me with the installer.
In a Readme? What other products put their buglists there? Isn't an URL
sufficient?
Mikael
Tech facts:
PM 5.5.3 Swedish | OS X 10.4.8 | Powerbook G4/400 Mhz | 1GB RAM | 80GB HD
----------------------------------------------------------------------
Subject: Re(2): Powermail support (Was: Re: Exporting from PowerMail - all mail
is Unread)
From: "Winston Weinmann" <[EMAIL PROTECTED]>
Date: Mon, 22 Oct 2007 12:54:50 -0500
As an example providing information on bugs, see Mike Bombich's forum
page for Carbon Copy Cloner:
<http://forums.bombich.com/viewforum.php?
f=12&sid=f1fc006f711bb1c03a2502b875bd32ff>
Another program I use, PDFPen, has several workarounds listed in its
FAQs for specific problems.
I have seen similar "known issue" lists with other software. Apple does
something vaguely similar (although more opaque) with articles on its
support site.
Closer to home, SpamSieve has a FAQ, blog archive, and a forum, as well
as a /request/ soliciting comments on improving the software.
<http://c-command.com/spamsieve/support>
Noting bugs, known issues, and workarounds for users is not unprecedented.
Regards,
- Winston
Mikael Byström wrote:
>Winston Weinmann suggested:
>
>>That is a great idea, and one CTM should have both on its site and in a
>>Read Me with the installer.
>In a Readme? What other products put their buglists there? Isn't an URL
>to some kind of online source sufficient?
>After all buglists are not primarily around to warn people, but to focus
>bug-*fixing*.
>
>I can imagine when an open bugfix list could be of use for the
>developers of PowerMail, but as there isn't one in place I assume they
>think otherwise or at least that the developers don't find it worth the
>effort.
>
>I would think CTM do keep an inhouse buglist for internal use.
>
>Mikael
>
>Tech facts:
>PM 5.5.3 Swedish | OS X 10.4.8 | Powerbook G4/400 Mhz | 1GB RAM | 80GB HD
>
>
>
>
----------------------------------------------------------------------
End of powermail-discuss Digest
