Re: mutt sucks...
Jacek Wojaczynski wrote: 4. Folders - it really sucks! I even cannot see how many read/unread messages there are in a particular folder if I don't enter it... Sounds like you haven't listed your mailboxes in .muttrc: mailboxes ! mailboxes =mutt =procmail-user =linux-kernel =vim-user mailboxes =list1 5. Using up/down arrows I scroll through messages (index view). Why it skips whole page? I'd like it to work same as in slrn. Read the manual, assign a new keybinding. 6. What's the default shortcut for Mark all tagged messages as read? The manual is here: http://www.mutt.org/doc/manual/ You are looking for tag and patterns. 7. C - copies messages to a different folder. What key moves them? saving them does that. 8. Can I import my Address Book from The Bat!? Probably. Can the Bat export them in a useful format? 9. Au! There is no address book built in. What would you suggest? Abook or sth else? There is, you didn't read the manual. 10. I still do not understand this Tab completion thing - it seems that sometimes it simply DOES NOT work as expected. Does it behave the way the manual expects it to behave? If not, file a bug. 11. What's the newest version of mutt? Is there a lot of problems using beta versions? (when I used TB! it was almost always the newest beta). These are at the top of the www.mutt.org page. In general, don't use a development release unless you need a feature in it or are doing development work. 12. How do I create multiple identities? Different from, attribute line and language settings for different mailing lists. Possible? How? Folder-hooks or only send-hooks? Have you looked at the sample .muttrc's provided at http://www.mutt.org/links.html#config ? 13. How can I move old mail to a different folders? Automatically of course. For example for this list? How? Depends. Do you want shiny clean folders with nothing in them except fresh email that you've never seen? Do you want folders with relatively recent email, so that anything over n days/weeks/months old is archived? Think about folder-hooks, and read those sample .muttrc files. 14. Can I send within mutt mail to all users on my system? Sure. If you have an alias established by your MTA or in mutt, this becomes easier. vim related problems: Really ought to go to the vim lists. For example: [EMAIL PROTECTED] ([EMAIL PROTECTED], [EMAIL PROTECTED], archive at http://groups.yahoo.com/group/vim) 15. It's very very tiring manually stripping those signatures and manually adding signs when reformatting a paragraph. In TB! it was automatic... If you need to reformat a paragraph, use fmt or par, or learn regexps. 16. I have ispell installed. It works fine. I can switch between english and polish dictionaries. Is it possible to automatically set proper dictionary? I mean: English for english language mailing lists and polish for polish language lists? I don't use spellcheckers; however, I imagine that you would read the ispell docs to find out how to switch dictionaries according to a command line or environment variable, and set that in a folder-hook. 17. When spellchecker underlines a word - can I add it to the user dictionary? How? I'm having only console - so no mouse right click. ispell documentation almost certainly has this. 18. Why ispell spells too much? It even tries to spell quoted text or header lines. It's stupid. Can I change it? Yes. It's open source. -dsr- -- Lois McMaster Bujold and Terrance Dicks's _Dr Who: Miles Away!_, in which the heroic Time Lord's attempts to overthrow an oppressive star empire are repeatedly thwarted by an infuriating dwarf. --Graham Woodland
Re: location of signature.
Bo Peng wrote: I am sorry but I could not find this message. Could you tell me its subject or date? Is it in mutt-user group? This discussion (Message-ID 8gcg1a$qte$[EMAIL PROTECTED]) may be helpful for you. It's a message ID. Go search Google Groups for it; you'll get a 12 message thread. -dsr- -- Robin: Where'd you get a live fish, Batman? Batman: The true crimefighter always carries everything he needs in his utility belt, Robin.
Re: [Re: NuBe: upgrade question]
Kevin Coyner said: Since I'm just getting started and haven't invested a huge amount of time, effort and config files yet, what application chain would you recommend? At this point it won't be hard for me to make major changes since I'm not set in my ways nor have any predispositions. Right now I'm headed towards: mutt, sendmail, fetchmail and procmail. But I'm selecting these for no particular reason other than they seem standard and common. What might be a better setup (with 'better' meaning having more tools yet less complexity!)? mutt is good -- but on this list, did you expect any disagreement? sendmail is the most complex MUA. I highly recommend any of the big three alternatives: qmail, Postfix, and exim. If you use Debian Linux, exim is your default and extremely easy to setup. No matter what OS you use, if qmail is your choice, please install it from source and using the www.lifewithqmail.org guide. getmail is simpler than fetchmail, but not as powerful. maildrop has a simpler configuration language than procmail, but is again not quite as powerful. The basics - duplicate elimination, filtering mail through SpamAssassin, sorting mail into folders, dropping idiots you never want to hear from again - can be done in a less arcane way in maildrop. -dsr-
Re: [Re: NuBe: upgrade question]
Thorsten Haude said: * -dsr- [EMAIL PROTECTED] [02-06-06 20:34]: maildrop has a simpler configuration language than procmail, but is again not quite as powerful. Since I am one of the most vocal Supporters of Maildrop, I would be interested to hear some examples where Procmail can do more. (Background: I used Procmail for a few years, then went looking for an alternative. I found Maildrop, liked it, but found Mail::Audit much more powerful, so I never used Maildrop.) ...whereas I use procmail at work and maildrop at home. The primary example of procmail's power is the ability to create, call and distribute modules. If it were only a bit more powerful, one could managed named functions and procedures, which would be nice, but at that point, one might as well go to Mail::Audit and have all of Perl at your command. -dsr-
Re: weird color behaviour with aterm rxvt
Maximilian Szengel said: Hi, I've just edited my mutt colors to have a white background. (color normal black white etc.) I am using aterm and when I call mutt with the white background setting it looks awful, not white. Have a look at the screenshot [1]. I tried it with rxvt and it looks the same. Am I doing something wrong? Maybe it's not mutt's fault, then just ignore this post and I am going to find help somewhere else. 1. http://che23.de/mutt_aterm.jpg You told Mutt to use a white background, but you didn't tell aterm (or rxvt). Invoke your term with -bg white and tell us what happens. -dsr-
Re: OT: What are RFCs? (Was: Re: Outh...)
On Mon, Apr 08, 2002 at 11:21:46PM +0200, Martin Karlsson wrote: * David Champion [EMAIL PROTECTED] [2002-04-08 14.06 -0500]: [...snip...] (This is recommended, not required.) See RFC 2822, section 3.6.4. Sorry for going OT, but could someone please point me to a site or document which explains _what_ an RFC (yeah, request for comment, I managed to google that far :-) ) really /is/, and what types of RFCs there are and why thera are more than one type of RFC? http://www.rfc-editor.org/ To answer the other questions backwards: There is more than one type of RFC because people need more than one type. The types of RFC are Standards, Informational, and Experimental. Standards are exactly that: if you want to interoperate with other people using a particular protocol, this is the official description of how to do it. Informational/Experimental are exactly that: if you want to know how other people are doing things which haven't been standardized yet, or can't or won't be standardized, or aren't easily standardized, or a summary of several approaches, this is what you want to read. Typical labels: STD for standard, BCP for best current practices, FYI for informational. Finally, why they are called RFCs: At a meeting discussing what would become NCP in 1969, a grad student was assigned to take notes. As he wasn't sure he had written everything down exactly right, he wrote Request For Comments across the top when he made copies and distributed them. -dsr-
