Re: Problem with Regular Expression
On 2010-06-23, Rado S wrote:
> =- Michelle Konzack wrote on Mon 21.Jun'10 at 11:27:15 +0200 -=
>
> > I need someone who want to save my live! ;-)
> > {...}
> > but while the first is working perfectly as default, the second
> > one is screwed up du to the changeing name in the () at the end of
> > the subject.
> > {...}
> >
> > Can some one enlight me how to solv the problem with the changeing
> > name in the () at the end of the subject please?
>
> What do you want to achieve specifically, conceptually?
I think he wants to thread messages by subject, ignoring the leading
message ID in brackets and the trailing author's name in
parentheses. The reply_regexp can tell mutt to ignore one
contiguous string in the subject, which is usually anchored to the
start of the subject, but Michelle wants mutt to ignore two
strings--one at the start of the subject and one at the end--and
consider only the string in the middle when threading by subject.
As far as I know, mutt can't do that with the current reply_regexp
mechanism.
Regards,
Gary
Re: Detecting new mail and read mail in 1.4 and 1.5
Christian Ebert schrieb am 22.06.2010 um 23:16 (+0200): > * Michael Ludwig on Tuesday, June 22, 2010 at 22:27:06 +0200 > > Is that also the cause of the now dysfunctional new mail detection > > in 1.5, broken at least in my configuration and on Cygwin? > > > > How can new mail detection be repaired for 1.5? > > I'm using Maildir, but > > set check_mbox_size=yes > > looks like a good candidate. Indeed. It is unknown as of 1.4,2, but solves the issue in 1.5.20. -- Michael Ludwig
Re: Pick sendmail command based on sender address
Michael Tatge schrieb am 22.06.2010 um 23:19 (+0200): > * On Mon, Jun 21, 2010 04:27PM +0200 Michael Ludwig (mil...@gmx.de) > muttered: > > I send mail using ssmtp (a simple standalone SMTP library) and one > > of the SMTP servers for the different freemail addresses I have. > > I'd recommend switching to esmtp. You don't have to mess with > send-hooks because it supports using the correct server based on the > envelope (identities) > See http://wiki.mutt.org/?LightSMTPagents/Esmtp where I described the > config in detail. Thanks. I've switched to msmtp, which can also parse the envelope to figure out the SMTP server to use. But it's not even needed now as Mutt passes the sender address to msmtp and so has it select the correct account. -- Michael Ludwig
Re: Show new mail in subfolders from root folder?
=- Roger wrote on Mon 21.Jun'10 at 21:44:56 -0800 -= > However, when I am within the root maildir folder, my email > folders being listed, I can only see when new email has arrived > after I use the TAB key. The folder browser has no check_new call/ routine. Actually it hasn't even IMAP-keepalive, so when you "hang around" there for too long, your IMAP connections will drop. -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
Re: Problem with Regular Expression
=- Michelle Konzack wrote on Mon 21.Jun'10 at 11:27:15 +0200 -=
> I need someone who want to save my live! ;-)
> {...}
> but while the first is working perfectly as default, the second
> one is screwed up du to the changeing name in the () at the end of
> the subject.
> {...}
>
> Can some one enlight me how to solv the problem with the changeing
> name in the () at the end of the subject please?
What do you want to achieve specifically, conceptually?
--
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.
Re: Pick sendmail command based on sender address
* On Mon, Jun 21, 2010 04:27PM +0200 Michael Ludwig (mil...@gmx.de) muttered: > I send mail using ssmtp (a simple standalone SMTP library) and one of > the SMTP servers for the different freemail addresses I have. I'd recommend switching to esmtp. You don't have to mess with send-hooks because it supports using the correct server based on the envelope (identities) See http://wiki.mutt.org/?LightSMTPagents/Esmtp where I described the config in detail. HTH, Michael -- BOFH excuse #95: Pentium FDIV bug PGP-Key-ID: 0xDC1A44DD Jabber: init...@amessage.de
Re: Detecting new mail and read mail in 1.4 and 1.5
* Michael Ludwig on Tuesday, June 22, 2010 at 22:27:06 +0200 > Yesterday I built Mutt 1.5 on Cygwin, which worked fine; and today I > discovered the Cygwin maintainers have done so as well. So Cygwin 1.7 > now has Mutt 1.5. > > One problem that comes with the update is Mutt's notion of what is new > mail and what is read mail. In 1.4, it worked as it should: mailboxes > containing new mail were flagged, and reading it unset the flag. Now in > 1.5, every mailbox is flagged as containing new mail each time I start > Mutt. > > When building Mutt 1.5, I noticed that the --enable-buffy-size configure > script flag has disappeared. > > When building 1.4, it seemed to me that this flag is needed to make mutt > remember having read new mail in a box so it isn't flagged as new any > more. > > Is that also the cause of the now dysfunctional new mail detection in > 1.5, broken at least in my configuration and on Cygwin? > > How can new mail detection be repaired for 1.5? I'm using Maildir, but set check_mbox_size=yes looks like a good candidate. Look in man(5) muttrc whether it is available for your version. c -- theatre - books - texts - movies Black Trash Productions at home: http://www.blacktrash.org/ Black Trash Productions on Facebook: http://www.facebook.com/blacktrashproductions
Detecting new mail and read mail in 1.4 and 1.5
Yesterday I built Mutt 1.5 on Cygwin, which worked fine; and today I discovered the Cygwin maintainers have done so as well. So Cygwin 1.7 now has Mutt 1.5. One problem that comes with the update is Mutt's notion of what is new mail and what is read mail. In 1.4, it worked as it should: mailboxes containing new mail were flagged, and reading it unset the flag. Now in 1.5, every mailbox is flagged as containing new mail each time I start Mutt. When building Mutt 1.5, I noticed that the --enable-buffy-size configure script flag has disappeared. When building 1.4, it seemed to me that this flag is needed to make mutt remember having read new mail in a box so it isn't flagged as new any more. Is that also the cause of the now dysfunctional new mail detection in 1.5, broken at least in my configuration and on Cygwin? How can new mail detection be repaired for 1.5? -- Michael Ludwig
Show new mail in subfolders from root folder?
When I am within a subfolder of the root email folder (ie. $HOME/.maildir/.myemail), I can see Mutt automatically check & show when new email arrives for this folder. However, when I am within the root maildir folder, my email folders being listed, I can only see when new email has arrived after I use the TAB key. Is this because $HOME/.maildir isn't a real maildir? Is this normal? muttrc: set timeout = '15' set mail_check = '30' mailboxes `find ~/.maildir/ -type d -name cur -printf '%h '` -- Roger http://rogerx.freeshell.org/
