You must not have four children in three schools all of whom attend various games, practices, parties, classes and other events in obscure locations. Or live in a city where directions are needed often.
Then there are school instructions, lists of dates for the above activities, invitations, contact lists, event notices, travel itineraries, etc. These need to be posted or responded to (for example, by sending a check in for payment), or kept for easy reference. Yes, we print a lot of email, and for good reason. - Winston Matthias Schmidt wrote: >well, my 80-year old parents are happily using PM as well as my wife. >I have no problem recommending PM to anyone. >But I'm wondering why some people need to print some many emails? >Isn't it enough to archive the important stuff and have a backup strategy? > >Thanks and all the best > >Matthias > > >Am/On Thu, 19 Apr 2007 10:04:24 -0400 schrieb/wrote Winston Weinmann: > >>Wayne wrote: >>>I doubt that a ton of effort is going to be spent on this issue >>>because most of us don't really use that feature often and I, and I'm >>>sure others, would rather see CTM Dev spend their time improving or >>>fixing other issues rather than HTML email. >> >>That is a valid point. CTM should definitely work on the issues of >>greatest concern to its user base. I am curious how many other PM users >>find the HTML printing problems more than just a minor annoyance. >> >>I waste paper and ink with blank printouts, or printouts with more pages >>than needed. (Yes, I re-use the pages printed with only a header.) >>Sometimes I find (for example) directions I had printed not ready as I >>am going out the door. >> >>I can learn to live with the problem, but I am not happy. It would be OK >>to get an error notice or warning which says I have to go to my web >>browser to print HTML mail. Then at least I'd get what I expect. >> >> >>Also, I do not think it makes CTM look professional to have such an >>obvious bug. It certainly prevents me from recommending PowerMail to >>others, even if I keep using it. The problem is too quirky for new users >>to have to deal with. >
