Re: Gmail style alias setting
Hello Take a look at lbdb (Little brother database, http://www.spinnaker.de/lbdb/). You can pipe all mail through this little app which then stores all found email adresses. Additionaly it has the possibility to fetch more adresses from other sources too. If you don't use procmail or any other tool to process mail on receiving, you can use the filter-functionality of mutt to parse the mail on reading. Greetings Hello, Gmail can do a lot of work automatically, but I believe mutt can do it better. Such as alias setting, gmail can 1. store all mails appeared in all mail headers, e.g., From/To/CC/BCC 2. auto-complete when your key-in any part of a mail address. e.g., when you key in ab, addresses like [EMAIL PROTECTED] [EMAIL PROTECTED] Ab Barth, [EMAIL PROTECTED] will show up for your choice. 3. when storing alias, if the person's name is included in header, gmail will save it too, for example, if you receive a mail from Ab Barth, [EMAIL PROTECTED], the name and address will both be saved. Do you think it's possible to let mutt do the alias thing as smart as gmail? Please tell me how to. Thank you very much! Best Lars -- cu --== Jerri ==-- Homepage: http://www.jerri.de/ ICQ: 54160208 Public PGP Key: http://www.jerri.de/jerris_public_key.asc signature.asc Description: Digital signature
Re: Gmail style alias setting
On Nov 18, 2008, at 5:54 AM, Gerhard Siegesmund wrote: Hello Take a look at lbdb (Little brother database, http://www.spinnaker.de/lbdb/). You can pipe all mail through this little app which then stores all found email adresses. Additionaly it has the possibility to fetch more adresses from other sources too. If you don't use procmail or any other tool to process mail on receiving, you can use the filter-functionality of mutt to parse the mail on reading. I agree, i use lbdb on my mac to query the system Address Book. J
Re: New line characters in message body.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It took me a while to discover your message because your DKIM signature is broken. It may be that the mutt mailing list is breaking it, but you may want to take a look anyway. On Saturday, November 8 at 10:54 AM, quoth Maruvada, Suryakiran: When I give echo first line \n second line \n the out put is first line second line but when I use the same with mutt i.e echo first line \n second line \n | mutt -a attachment mail-id my body of the mail come like : first line \n second line \n Interesting. Well, normally (on linux, anyway), echo only translates \n into a newline character if you give it the -e flag. I don't know why it behaves differently in the two different ways you're using it, but I'd guess it has something to do with your shell's setup. So, try this: echo -e first line \n second line \n | mutt -a attachment mail-id ~Kyle - -- No matter what side of the argument you are on, you always find people on your side that you wish were on the other. -- Jascha Heifetz -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkki+KYACgkQBkIOoMqOI17+jQCg9gfsrZYQ9F/rcYPO5cyqxj7K TRkAniNSj1+ev2nCwqghBRZVh00Xc5yg =SHkR -END PGP SIGNATURE-
Re: Customize To: field
* Michael Elkins [EMAIL PROTECTED], 2008-11-17 21:46:02 Mon: On Mon, Nov 17, 2008 at 09:32:52PM -0800, Brendan Cully wrote: Seems fine. Does anyone object? I think this makes sense. The user is already requesting that it be displaying this way in the index, so it should not be a problem to display it this way when replying. I was about to suggest making the To: change conditional on the value of a configuration variable, because reverse aliases may be used to reply to people who don't know how to spell their own name properly, and we may want to keep that kind of fix private. But then I noticed that the reverse-alias name is already being used in attribution lines, leaking the local alias to the recipient, so that adding it to the To header as well does not change the situation much. So, unless someone else advocates in favor of an extra configuration variable controlling this behavior, I guess I consider this change acceptable. -- David Haguenauer pgpaoJnY1fAF9.pgp Description: PGP signature
Re: Customize To: field
On Tue, Nov 18, 2008 at 03:48:05PM -0500, David Haguenauer wrote: I was about to suggest making the To: change conditional on the value of a configuration variable, because reverse aliases may be used to reply to people who don't know how to spell their own name properly, and we may want to keep that kind of fix private. But then I noticed that the reverse-alias name is already being used in attribution lines, leaking the local alias to the recipient, so that adding it to the To header as well does not change the situation much. Excellent observation. I did consider that someone might want the display name to be kept private, but I imagine that use is probably a distinct minority--most of the time its to fix the sender's address for them since they can't seem to be bothered. The fact that we already leak this information it a boost to the change. me
Blocking when sending mail
Hello, Mutt is blocked when sending mail. It takes a long time if the mail is large. Is it possible to send mail in a non-blocking mode? Thanks Lars
Re: Blocking when sending mail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday, November 19 at 03:37 PM, quoth Chengqi(Lars) Song: Mutt is blocked when sending mail. It takes a long time if the mail is large. Is it possible to send mail in a non-blocking mode? Yes, unless you're using the built-in smtp support. If you're using an external mail program (such as sendmail, postfix, or msmtp), then you just need to set $sendmail_wait to some low non-zero number. However, if you're using the built-in smtp support (read: $smtp_url), then no, there's no way to send mail in a non-blocking way. Mutt isn't multithreaded, and so can't really do multiple things at the same time. ~Kyle - -- There can be but little liberty on earth while men worship a tyrant in heaven. -- Robert Green Ingersoll -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iEYEARECAAYFAkkjws8ACgkQBkIOoMqOI14VxACdFtlcGG5pvS6su+QinlWlgNjn 1V4AmgMtla1deRwyE8cNJ5ATw1vUsu7R =HNo6 -END PGP SIGNATURE-
