Re: Change folders

2008-06-02 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, June  2 at 03:42 PM, quoth Ravi Uday:
> When I select a different  folders using 'c' and '?' it starts to 
> load the folder and msgs from start. Is there a way to bypass/cache 
> this and make mutt load the folder faster ?

That depends. If you're using MH, maildir or imap and you have mutt 
1.5.7 or newer, then yes, you can use the $header_cache (see the 
documentation for details). If you're using mbox or mutt 1.4.x, then 
you're outta luck. Mbox won't get much faster with a cache (the best 
you can do is make your disk faster and get a faster cpu), and 1.4.x 
doesn't have that feature yet (it'll be in the forthcoming 1.6 
version).

~Kyle
- -- 
I have not failed. I've just found 10,000 ways that won't work.
   -- Thomas Edison
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhEeQUACgkQBkIOoMqOI17I0ACgjTt2d4wUK7LFJXXhGG1ZplQ/
bn8An2Xo0Wkh1pZBVaCvsDao3HdTbVGr
=v1VG
-END PGP SIGNATURE-


Change folders

2008-06-02 Thread Ravi Uday
Hi mutt folks,

When I select a different  folders using 'c' and '?' it starts to load
the folder and msgs from start.
Is there a way to bypass/cache this and make mutt load the folder faster ?

Thanks,
Ravi


Re: folder-hook in my .muttrc doesn't work

2008-06-02 Thread Rudolf Bahr
* Kyle Wheeler ([EMAIL PROTECTED]) [080602 22:19]:

...
> I would have done something like this:
> 
>  alias -group lisagroup lisa Lisa Lady <[EMAIL PROTECTED]>
>  set use_from=no
>  send-hook '%C lisagroup' 'my_hdr From: [EMAIL PROTECTED]'
>  fcc-save-hook '%C lisagroup' +fanciulla/lisa

Hello Kyle,

I think it is a good advice to write an own .muttrc from scratch. 
I will do that around your code suggestion above.

Thank you again!

Rudolf


Re: folder-hook in my .muttrc doesn't work

2008-06-02 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, June  2 at 09:39 PM, quoth Rudolf Bahr:
>> On Monday, June  2 at 12:29 PM, quoth Rudolf Bahr:
>>> folder-hook +fanciulla/lisa   'set use_from=no'
>>> folder-hook +fanciulla/lisa   'unmy_hdr *'
>>> folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'
>> Those three should work fine.
> Sorry, they don't, in this case, at least. The From: address is 
> still a combination of my username and PC's hostname.

Hmmm In that case, I'm not sure. Let's try something different to 
see if this works (all one line, of course):

 send-hook '~C [EMAIL PROTECTED]' 'my_hdr From:
 [EMAIL PROTECTED]'

>>  folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'
>
>
> Ok, I removed the folder-hooks which can't be preset by me and are 
> indeed unnecessary. Instead I added as you suggested:
>
> folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'
>
> But Mutt gives me still back: '[EMAIL PROTECTED]' instead of 
> '=fanciulla/lisa'.

Very interesting. That's not a typical mutt-default Fcc, so I suspect 
you have other hooks in your configuration that are re-setting it... 
particularly fcc-hooks or fcc-save-hooks.

>> *answer* email (r), as opposed to compose new email (m)? If you're 
>> *replying* to email (r), then the recipient (To:) is set based on 
>> the message you're replying to.
>> 
>> What exactly are you trying to achieve?
>
> I'm entering the folder 'fanciulla/lisa' in order to answer a message 
> there by 'r' or ',a'.

Well, I guess my point is... I generally prefer using send-hooks (or 
reply-hooks) instead of folder-hooks for changing these sorts of 
settings, because they allow me to have the message anywhere, and get 
triggered for every message (thus, they over-rule folder-hooks). 
Often, the only reason people choose to use folder-hooks is because 
they haven't yet discovered send-hooks. On the other hand, some people 
strongly associate a given folder with a given role, and associating 
folder with sending address (for example) makes more sense in their 
head.

I would have done something like this:

 alias -group lisagroup lisa Lisa Lady <[EMAIL PROTECTED]>
 set use_from=no
 send-hook '%C lisagroup' 'my_hdr From: [EMAIL PROTECTED]'
 fcc-save-hook '%C lisagroup' +fanciulla/lisa
 # Reply-To isn't usually useful

Note that the send-hook and fcc-save-hook trigger whenever I send a 
message to lisa regardless of what folder I'm in. The $use_from 
setting stays the same always, unless I add hooks to change it (in 
which case it'll have to go into a hook as well). The use of a group 
means I can later add addresses for lisa (e.g. 'group -group lisagroup 
- -addr [EMAIL PROTECTED]') and not have to change my hooks.

Without the "group" bit, that would be rewritten as:

 alias lisa Lisa Lady <[EMAIL PROTECTED]>
 set use_from=no
 send-hook '~C [EMAIL PROTECTED]' 'my_hdr From:
 [EMAIL PROTECTED]'
 fcc-save-hook '~C [EMAIL PROTECTED]' +fanciulla/lisa
 # Reply-To isn't usually useful

>> Keep in mind, these hooks are only triggered when you enter the 
>> folder. If you have other hooks that override them (such as 
>> send-hooks or reply-hooks or message-hooks), they will not be 
>> re-triggered until you re-enter the folder.
>
> Yes, therefore I commented all other lines which have something to 
> do with 'lisa' or '=fanciulla/lisa'. It seems to help nothing.

Depending on your configuration, you may have plenty of "default" 
hooks that don't contain the text "lisa", but apply anyway. For 
example the patterns "~A" and "." in send/reply/message/display-hooks 
will match your emails... there may be lots more hooks being triggered 
than you're aware of. I'd start by following the debug steps outlined 
here: http://wiki.mutt.org/?DebugConfig

This is why I usually recommend that, once you start getting serious 
about configuring your own mutt, you start your own muttrc from 
scratch. It'll take some time to read the descriptions of all the 
relevant settings, but it's *well* worth your time.

> Kyle, many thanks for your answer with the explanations!

Happy to help!

~Kyle
- -- 
If we knew what it was we were doing, it would not be called research, 
would it?
   -- Albert Einstein, 1941
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhEU64ACgkQBkIOoMqOI172lQCcDYXz+ht0y1WnmxgK4UYQQ2zb
KJUAoPlsoVLonvGYQ0Ifi5pXd4tBZTYR
=Z/PN
-END PGP SIGNATURE-


Re: folder-hook in my .muttrc doesn't work

2008-06-02 Thread Rudolf Bahr

* Kyle Wheeler ([EMAIL PROTECTED]) [080602 16:19]:

Hello Kyle,

> On Monday, June  2 at 12:29 PM, quoth Rudolf Bahr:
> >folder-hook +fanciulla/lisa   'set use_from=no'
> >folder-hook +fanciulla/lisa   'unmy_hdr *'
> >folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'
> 
> Those three should work fine.
> 

Sorry, they don't, in this case, at least. The From: address is still a 
combination 
of my username and PC's hostname. 


> >folder-hook +fanciulla/lisa   'my_hdr   To: [EMAIL PROTECTED]'
> >folder-hook +fanciulla/lisa   'my_hdr  Fcc: =fanciulla/lisa'

> Those two won't do anything (well... they will, but not what you 
> expect). First of all, every time you compose a message, mutt asks you 
> who the recipient is. Setting a To: header ahead of time doesn't 
> change that, so whatever To: header you had set before will get 
> overwritten. Secondly, the Fcc: setting isn't a *header*, it's a 
> *setting* (that mutt displays in the compose screen as if it was a 
> header). Here's how you'd do it the "right" way:
> 
>  folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'


Ok, I removed the folder-hooks which can't be preset by me and are 
indeed unnecessary. Instead I added as you suggested:

folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'

But Mutt gives me still back: '[EMAIL PROTECTED]' instead of '=fanciulla/lisa'. 
 
> 
> *answer* email (r), as opposed to compose new email (m)? If you're 
> *replying* to email (r), then the recipient (To:) is set based on the 
> message you're replying to.
> 
> What exactly are you trying to achieve?

I'm entering the folder 'fanciulla/lisa' in order to answer a message
there by 'r' or ',a'.

> 
> Keep in mind, these hooks are only triggered when you enter the 
> folder. If you have other hooks that override them (such as send-hooks 
> or reply-hooks or message-hooks), they will not be re-triggered until 
> you re-enter the folder.
> 

Yes, therefore I commented all other lines which have something to do with 
'lisa'
or '=fanciulla/lisa'. It seems to help nothing.

Any additional ideas?

Kyle, many thanks for your answer with the explanations!

Rudolf




Re: Hi all, is there anyone knows how to send bigger attachments

2008-06-02 Thread David Champion
> Thanks. But I am using a Linux system, and the file is just about 6M.
> 
> I am just curious that where can I find the so-called "system restriction" ?

It could be on your system, or it could be on the one that your system
relays to when it sends the message on to the recipient.

Where you find the configuration depends on what MTA you're using.

If you're using sendmail, it's probably in /etc/mail/sendmail.cf and/or
/etc/mail/sendmail.mc.  If you're using postfix, it's probably in one
of the files in /etc/postfix -- perhaps main.cf.  Check your MTA's
docuementation for whatever distribution of Linux you're using.

-- 
 -D.[EMAIL PROTECTED]NSITUniversity of Chicago


Re: folder-hook in my .muttrc doesn't work

2008-06-02 Thread Rocco Rutte

Hi,

* Kyle Wheeler wrote:

Secondly, the Fcc: setting isn't a *header*, it's a 
*setting* (that mutt displays in the compose screen as if it was a 
header). Here's how you'd do it the "right" way:



folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'


Yes, this form is better.

But for the record, you can add the "special" Fcc: and Attach: headers 
in the editor for mutt to pick up. It'll then attach all files mentioned 
and set the fcc accordingly (if headers are given).


Users in general should be aware of this because it can be a quite 
dangerous "feature" and easily abused:


  mutt 'mailto:[EMAIL PROTECTED]/.gnupg/secring.gpg'

could send out files you really want to keep private if you don't pay 
enough attention to the compose menu.


Now that I see it, maybe mutt shouldn't allow for Fcc: and Attach: user 
defined headers at all.


Rocco


Re: folder-hook in my .muttrc doesn't work

2008-06-02 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, June  2 at 12:29 PM, quoth Rudolf Bahr:
>folder-hook +fanciulla/lisa   'set use_from=no'
>folder-hook +fanciulla/lisa   'unmy_hdr *'
>folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'

Those three should work fine.

>folder-hook +fanciulla/lisa   'my_hdr   To: [EMAIL PROTECTED]'
>folder-hook +fanciulla/lisa   'my_hdr  Fcc: 
>=fanciulla/lisa'

Those two won't do anything (well... they will, but not what you 
expect). First of all, every time you compose a message, mutt asks you 
who the recipient is. Setting a To: header ahead of time doesn't 
change that, so whatever To: header you had set before will get 
overwritten. Secondly, the Fcc: setting isn't a *header*, it's a 
*setting* (that mutt displays in the compose screen as if it was a 
header). Here's how you'd do it the "right" way:

 folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'

>folder-hook +fanciulla/lisa   'my_hdr Reply-To: 
>[EMAIL PROTECTED]'

That's another one that mutt often generates at compose-time (just 
like the "To:" header) and overwrites any previous settings. For 
example, mutt obeys the environment variable REPLYTO.

> Hopelessly, it doesn't work. if I answer to an e-mail in this 
> folder, I still allways have to correct some of the header fields. 

*answer* email (r), as opposed to compose new email (m)? If you're 
*replying* to email (r), then the recipient (To:) is set based on the 
message you're replying to.

What exactly are you trying to achieve?

Keep in mind, these hooks are only triggered when you enter the 
folder. If you have other hooks that override them (such as send-hooks 
or reply-hooks or message-hooks), they will not be re-triggered until 
you re-enter the folder.

~Kyle
- -- 
Suppose ye that I am come to give peace on earth? I tell you, Nay; but 
rather division: For henceforth there shall be five in one house 
divided, three against two, and two against three. The father shall be 
divided against the son, and the son against the father; the mother 
against the daughter, and the daughter against the mother; the mother 
in law against her daughter in law, and the daughter in law against 
her mother in law.
   -- Prince of Peace, Jesus Christ (Luke 12:51-53)
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhD/lUACgkQBkIOoMqOI15TMQCgg8KKrpfe1srdiQyPGeBMPk4V
f8QAoNG85Z3RNne7p6Mka1aKXQMVlYnj
=T3JL
-END PGP SIGNATURE-


Re: folder-hook in my .muttrc doesn't work

2008-06-02 Thread Rado S
=- Rudolf Bahr wrote on Mon  2.Jun'08 at 12:29:05 +0200 -=

> Up to now I used a .muttrc-file which I found on the internet and
> it worked rather fine.

Catchup with rtfm then. :)
Once you know what you do, you can analyze what's wrong.
For example you set fcc-hook rather than Fcc: header your way.

For general debugging advice see also the welcome message with links
to the wiki.

-- 
© 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: Hi all, is there anyone knows how to send bigger attachments

2008-06-02 Thread Awflasher(GuoQirui)
Thanks. But I am using a Linux system, and the file is just about 6M.

I am just curious that where can I find the so-called "system restriction" ?

Would u please give me some further tips ? Thanks very much in advance!

On Mon, Jun 2, 2008 at 8:46 PM, Marcus Franke <[EMAIL PROTECTED]> wrote:
> On Sun, Jun 01, 2008 at 09:27:35PM +0200, Michelle Konzack wrote:
>> Can not be...
>>
>
> Size of mails is a system restriction enforced by your mail server.
> Your mail client just sends data to the mail server and somewhere in
> the line it may be restricted.
>
> Your server may be configured for 50MB files, Microsoft Exchange
> servers accept per default just 10MB. And thats about the raw message
> size, so if you have some 9MB file that gets uuencoded up to 11M, you
> crossed the line and the mail will be rejected.
>
>
>
> Marcus
>



-- 
Blog in Chinese
http://www.awflasher.com/blog/

Blog in English
http://www.ifgogo.com/


Re: Hi all, is there anyone knows how to send bigger attachments

2008-06-02 Thread Marcus Franke
On Sun, Jun 01, 2008 at 09:27:35PM +0200, Michelle Konzack wrote:
> Can not be...
> 

Size of mails is a system restriction enforced by your mail server.
Your mail client just sends data to the mail server and somewhere in
the line it may be restricted.

Your server may be configured for 50MB files, Microsoft Exchange
servers accept per default just 10MB. And thats about the raw message
size, so if you have some 9MB file that gets uuencoded up to 11M, you
crossed the line and the mail will be rejected.



Marcus


Re: Hi all, is there anyone knows how to send bigger attachments (a 6M sized file) with mutt?

2008-06-02 Thread Michelle Konzack
Can not be...

Am 2008-06-01 16:58:36, schrieb Awflasher(GuoQirui):
> Mutt is really great but I cannot get anything when sending a 6M file.
> 
> It's ok for sending small files but when i'm trying to send a big
> file, it stopped working.
> 
> Hope to get some tips, thanks very much!!
> 
 END OF REPLIED MESSAGE 

Today morning I have send an attachment of 26 MByte
(Debian Package) per mutt over then net...

It take some time because Up-Stream is only 128 kBit
(50 MBit Down-Stream) per Satelite but it works.

Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
+49/177/935194750, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature


folder-hook in my .muttrc doesn't work

2008-06-02 Thread Rudolf Bahr

Hello everybody,

it's the first time I'm posting a question here though I used to be a mutt
user for a longer time. As OS I'm using debian, 2.6.24-1-686; my Mutt works in 
mbox_type=Maildir mode and in conjunction with fetchmail, procmail and postfix.

Up to now I used a .muttrc-file which I found on the internet and it worked
rather fine. Now I'd like to intend to have some changes and try the 
configuration 
command "folder-hook" as follows:

folder-hook +fanciulla/lisa   'set use_from=no'
folder-hook +fanciulla/lisa   'unmy_hdr *'
folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'
folder-hook +fanciulla/lisa   'my_hdr   To: [EMAIL PROTECTED]'
folder-hook +fanciulla/lisa   'my_hdr  Fcc: =fanciulla/lisa'
folder-hook +fanciulla/lisa   'my_hdr Reply-To: [EMAIL PROTECTED]'

Hopelessly, it doesn't work. if I answer to an e-mail in this folder, I still 
allways 
have to correct some of the header fields. Though I set and unset a lot of 
other 
parameters of which I thought they could have an impact to folder-hook, mutt 
doesn't 
honor any of the desired parameters. 

The only command with a certain influence to the folder-hook command with
respect to the from: header field I found in the manual is the "use_from" 
command:

"When set, Mutt will generate the `From:' header field when sending
messages. If unset, no `From:' header field will be generated unless the
user explicitly sets one using the ``my_hdr'' command."

Where could be my mistake? Which command prevents mutt from taking over
the desired parameters?

Rudolf

PS.: Here my Mutt's capabilities:

---
[EMAIL PROTECTED]:~$ mutt -v
Mutt 1.5.18 (2008-05-17)
Copyright (C) 1996-2008 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 2.6.24-1-686 (i686)
ncurses: ncurses 5.6.20080503 (compiled with 5.6)
libidn: 1.8 (compiled with 1.8)
hcache backend: GDBM version 1.8.3. 10/15/2002 (built Apr 24 2006 03:25:20)
Einstellungen bei der Compilierung:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
+USE_FCNTL  -USE_FLOCK
+USE_POP  +USE_IMAP  +USE_SMTP  -USE_GSS  -USE_SSL_OPENSSL  +USE_SSL_GNUTLS  
+USE_SASL  +HAVE_GETADDRINFO
+HAVE_REGCOMP  -USE_GNU_REGEX
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME
-EXACT_ADDRESS  -SUN_ATTACHMENT
+ENABLE_NLS  -LOCALES_HACK  +COMPRESSED  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET 
 +HAVE_LANGINFO_YESEXPR
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
MIXMASTER="mixmaster"
Um die Entwickler zu kontaktieren, schicken Sie bitte
eine Nachricht (in englisch) an <[EMAIL PROTECTED]>.
Um einen Bug zu melden, besuchen Sie bitte http://bugs.mutt.org/.

patch-1.5.13.cd.ifdef.2
patch-1.5.13.cd.purge_message.3.4
patch-1.5.13.nt+ab.xtitles.4
patch-1.5.4.vk.pgp_verbose_mime
patch-1.5.6.dw.maildir-mtime.1
patch-1.5.8.hr.sensible_browser_position.3
---


Re: read a file named ^

2008-06-02 Thread Rocco Rutte

Hi,

* Patrick Shanahan wrote:


I use mbox, so I am guessing that MailDir is using some indexing ???
that is not providing the correct parameters to mutt.


Maildir doesn't have any indexing or meta data files, it's just one file 
per message. It encodes important flags into the path and filename so 
that tools can get some flags from just the path.