On Monday, 21 Jun 2004 20:02, Daniel Klein wrote: > Alright, I'm gonna give that a shot soon. Thanks a lot for the help. Do > you think I should repost this bug description on debian-user then? Sure, the people there are generally very knowledgeable and helpful if you ask good questions, as you have done. I'm also subscribed to debian-kde, kde-debian, and a couple of dozen more lists for good measure. Be warned that debian-user is high traffic. I expire messages after a week, and still have about 1200 messages from there. > PS: This is completely unrelated: What would be the easiest way to > enable me to just reply to mailinglist messages with my email client's > reply function? Right now that defaults to mailing back to ONLY the user > who sent mail, and that's not very helpful. Is there some simple way of > changing that, in thunderbird? It doesn't sound too promising. That's surprising; I've always thought highly of Thunderbird. http://bugzilla.mozilla.org/show_bug.cgi?id=242860 http://bugzilla.mozilla.org/show_bug.cgi?id=245029 > I see that the messages is forwarded with > the original "From:" intact and the mailinglist is only mentioned in the > to: section, with no specific reply-to in the mail. I've started putting > in a reply-to to kde@xxxxxxxxxxxx now, but that is a bothersome thing to > do for every single mail as well.. there's got to be a simple way to > have this done automatically. One would think so. Personally, I use KMail, which I find has excellent list handling skills. In addition to the Reply function being intelligent, it also has a function for only replying to the list. It would be a lot of work, but you might be able to set something up with procmail or any internal filters of Thunderbird to rewrite the headers of mails from mailing lists as a hack, but I agree -- there should be a simpler way. -- Alex Nordstrom ___________________________________________________ . Account management: https://mail.kde.org/mailman/listinfo/kde. Archives: http://lists.kde.org/. More info: http://www.kde.org/faq.html.