Re: default character set for outbound messages?
On Tue, Dec 29, 2009 at 06:33:53PM +0100, Hans Vanpee wrote: > After searching a bit further I think I solved my problem. Mutt retrieves > charset info from the locale, but it doesn't adapt the $send_charset variable > (it always defaults to us-ascii:iso-8859-1:utf-8). I specified the correct > value in .muttrc and it seems to work fine now. > Is this a bug in mutt? > > +++ Hans Vanpee [28/12/09 15:02 +0100]: >> Hello, >> >> I am having a small problem with mutt: when composing a message it isn't >> always created with the right character set. My locale (on Ubuntu) is >> configured as nl_BE.UTF-8, so I would expect mutt to use the same charset >> when creating a message. Sometimes it uses US_ASCII. >> How can I setup mutt to use UTF-8 by default? >> I use vim for editing messages. >> >> My locale output: >> LANG=nl_BE.UTF-8 >> LANGUAGE=nl_BE.UTF-8 >> LC_CTYPE=en_US.UTF-8 >> LC_NUMERIC=nl_BE.UTF-8 >> LC_TIME=nl_BE.UTF-8 >> LC_COLLATE=C >> LC_MONETARY=nl_BE.UTF-8 >> LC_MESSAGES=nl_BE.UTF-8 >> LC_PAPER=nl_BE.UTF-8 >> LC_NAME=nl_BE.UTF-8 >> LC_ADDRESS=nl_BE.UTF-8 >> LC_TELEPHONE=nl_BE.UTF-8 >> LC_MEASUREMENT=nl_BE.UTF-8 >> LC_IDENTIFICATION=nl_BE.UTF-8 >> LC_ALL= Why should the message be sent in UTF-8 if it only contains ASCII characters? What additional value does that bring? The only difference is the encoding specified in the headers. If it only contains iso-8859-1 characters, why should it be sent in utf-8, which will result in more bytes and greater chance that a reader's MUA does not understand the encoding? Of course, UTF-8 is so widely supported now that the $send_charset magic is less useful than it once was.
Re: How to count new emails in mbox format mailbox?
grep ^From | wc -l
Re: smtp in mutt
The SMTP client is a new-ish addition. It doesn't make a real MTA out of mutt, though, just a MUA that submits mail via SMTP like the GUI ones.
Re: wrong charset (fwd)
On Wed, May 20, 2009 at 01:37:40AM -0300, Luis A. Florit wrote: > > On Saturday, May 16 at 10:54 AM, quoth Luis A. Florit: > > > My problem is with iso-8859-1. They seems to understand only UTF-8. > > > > Yup. Well, I guess at this point the question boils down to: what's > > wrong with using UTF-8 for displaying things on the Nokia? > > That ISO-8859-1 text files, 99% of my files, are shown as garbage... Even in vim? They shouldn't. If they are, your vim is broken or misconfigured. With cat and other "dumb" tools this is to be expected, of course, and then you have little choice except changing the terminal character encoding to match your files, since you can't change the locale (except to C, which should be iso-8859-1 and might even work to make mutt speak iso-8859-1). -- Jussi Peltola
Re: utf8 file corruption after transmission over email
On Fri, May 08, 2009 at 06:23:15PM -0700, zion wrote: > On Fri, May 08, 2009 at 04:34:14PM -0700, zion wrote: > > Well, I just captured smtp session of loopback interface (same box where > > mutt is running). Here is the relevant part: > > 03d0: 746f 3e38 353c 2f74 6f3e 0d0a 0909 093c to>85.< > > 03e0: 7265 6164 3e21 d091 e288 9ae2 9591 3c2f read>!п.Б..Б.. > > > 03f0: 7265 6164 3e0d 0a09 0909 3c77 7269 7465 read>. > > > As you can see, this character is already messed up before reaching > > server. So, @gmail is not guilty here ;-). > Turns out it's my locale. having this causes the problem: > LC_CTYPE=ru_RU.KOI8-R > if LC_CTYPE is unset, file doesn't get corrupted. I think mutt is reading your file, assuming it's KOI8-R as stated in your locale, and converting it to UTF-8 for sending. It has to do that; plain text won't tell it what charset it's in and it has to guess. If you want to send files over email byte-per-byte, renaming them to .bin or something else that has the mime type of application/octet-stream should work better. -- Jussi Peltola
Re: wrong charset
I use mutt on a Nokia N810 over ssh. The xterm in mine, having selected English as the language in the GUI and not having fiddled with locales manually, uses UTF-8. The locales provided with the machine are named fi_FI, en_GB, etc. but they still seem to use UTF-8 - try grep UTF-8 /usr/share/locale-archive. Some terminals silently switch to ISO-8859-1 if you print something that isn't valid UTF-8, requiring you to restart them to get back to UTF-8. That, combined with a signature, motd, etc. in ISO-8859-1 can be very confusing. Remember that you can't change the xterm's locale with .profile, that will only change the locale within the shell the xterm runs, not in the xterm's environment itself. BTW, where did you get a maemo binary of mutt? -- Jussi Peltola
Re: Forward message and leave From: intact?
On Fri, Feb 27, 2009 at 08:21:00PM +, Dave Woodfall wrote: > I need to forward messages to a certain email address and have it so that > the recipient will reply to original sender rather than me. > > Is this possible? > > I can do this automagically with procmail but the problem is that some spam > is getting through, which I'd rather not have forwarded. > bounce-message?
Re: Not getting any new mail
On Sat, Dec 20, 2008 at 09:43:35AM -0500, James Dunleavy wrote: > set folder=imap://exchange.hq.domain.com/ # Point to IMAP server > mailboxes =imap://exchange.hq.domain.com/INBOX This is wrong, mailboxes is not a variable and that will expand to imap://exchange.hq.domain.com/imap://exchange.hq.domain.com/INBOX. You want mailboxes =INBOX -- Jussi Peltola
Re: Strange Characters In Emails
On Fri, Oct 03, 2008 at 04:05:54PM -0500, Kyle Wheeler wrote: > One of the things that I've experienced with some webmail clients > before, though, is that they simply ignore the character set that the > browser sends with the message content (assuming one is sent---maybe > one isn't, making it a bit of a hard problem) One rarely is sent, unless you use browser-specific hacks. Thank IE which failed to send it, and CGI scripts written for IE that break when the charset is mentioned, making it impossible for standards-complying browsers to do it properly...
Re: extract header from current message (to pass to shell)?
On Wed, Aug 27, 2008 at 02:44:41PM +0100, Marianne Promberger wrote: > Non-mutt related question in case someone with server experience would > like to comment: > > I'm not directly rsyncing up, but am calling a shell script that first > does one ping to see whether I can reach the server. Would it put > noticeable strain on the server to call this script every 15 (10? 5?) > minutes? I have a free shell account and I don't want to be rude. rsyncing a single file with --times is practically free, except for SSH connection setup. However, you probably could use a flag file that you touch whenever you rsync, and then add a condition to check the file has been changed since the last rsync. if [ "$file" -nt "$flag" ]; then rsync --foo-bar && touch "$flag"; fi or something like that. -- Jussi Peltola
Re: Mutt hangs, Network Issue?
Try enabling SSH keepalives.
Re: lbdb, ldap and SASL
On Mon, Feb 18, 2008 at 01:58:51PM +0100, Nathan Huesken wrote: > Hello, > > I have succesfully setup ldap on my server with SASL (digest-md5). > I have also succesfully setup lbdb on my computer to query the ldap server. > > Only problem: How can I make lbdb use digest-md5? I do not want to sent > cleartext passwords over the internet. Use TLS? I found SASL to be quite a hassle with LDAP. -- Jussi Peltola
Re: Moving a non-trivial mail setup to mutt
On Wed, Jan 23, 2008 at 01:50:10PM +0100, Dan H wrote: > On Wed, 23 Jan 2008 14:05:16 +0200 > Jussi Peltola <[EMAIL PROTECTED]> wrote: > > > Try: > > set folder="imap://[EMAIL PROTECTED]/" > > c = > > Typing '?' at this point results in an immediate segfault > (v1.5.13'). What gives? I have no idea. >With 'c' it works though. Is there a way of > only having to specify part of the folder name? I'm using the TAB key > all the time in bash. Tab completion should work with 'c'. > My .muttrc has now grown to this: > > > set folder=imap://server/ > set imap_user="xx" > set imap_pass="xx" > > mailboxes =INBOX /var/mail/dh > > ignore * > unignore from date subject to cc > > > When I start mutt, it shows me the stuff in the local spool. As soon > as I do some folder-oriented stuff it dives into the IMAP server, but > how can I now access my local hierarchy under ~/Mail? c ~/Mail > In principle I'd like to keep all locally (POP3) receiced mail in the > ~/Mail hierarchy and the other stuff on the IMAP server. You should be able to configure fetchmail / procmail to save it in your home directory. -- Jussi Peltola
Re: Moving a non-trivial mail setup to mutt
ripting vim or emacs to do all the things you want will take a lifetime :) > In short, my requirements are: > > - Multiple accounts (both local and remote) > - Multiple identites > - Folders with subfolders > - Powerful address management > > Does mutt cutt it? It does that for me. If you don't want to spend some time customizing it and reading the man page, I guess you are better off with another mailer. For me, going through every muttrc option and setting it to my liking resulted in the first usable configuration and I was hooked (no pun intended) pretty soon after. -- Jussi Peltola
Re: Display problem
Hi, On Mon, Nov 26, 2007 at 03:10:12PM +0100, Steve wrote: > After this short introduction, here is my problem, which isn't critical > but tiring. When I use TAB to go to the next unread message, sometimes > the display starts to move up and the whole message becomes mixed up. > After some investigation, all I found to fix this problem is to Ctrl-L > which redisplays the screen correctly. But this fix only works for a > while and I can be sure that a half a dozen messages later the problem > comes up again. I've seen that kind of weirdness when the terminal and programs don't agree on the character set to use. If I read correctly, the problem exists on a local terminal too, so it's improbable it's a charset mismatch problem. Anyway, pasting the output of the locale program wouldn't hurt, though (and the character encoding putty is using). -- Jussi Peltola
Re: Asian fonts / xterm with Mutt
On Fri, Oct 26, 2007 at 12:55:45PM -0600, Joseph wrote: > # dispatch-conf > WARNING: terminal is not fully functional > > I've never seen it before. It's because the remote machine doesn't have termcap/terminfo data for urxvt. Doing TERM=rxvt ssh [EMAIL PROTECTED] works as a workaround, although not perfectly. Installing the terminfo is a better solution, see: http://cvs.schmorp.de/rxvt-unicode/doc/rxvt.7.html#When_I_log_in_to_another_system_it_t -- Jussi Peltola
