Hi all,
I'm thinking of going to a monthly-rotated file, as my current scheme
of a different folder per correspondent is getting out of hand.
Still, for some people I still want the individual files.
So I have:
set mbox=+archive
set record=+archive
set save_name
All that works perfectly, excep
At 03:44 +0200 10 Dec 1999, Mikko Hänninen <[EMAIL PROTECTED]> wrote:
> Mike Bell <[EMAIL PROTECTED]> wrote on Thu, 09 Dec 1999:
> > Would it be possible to arrange for the contents of the from: header in sent
> > mail to be exported to the sendmail command, maybe as an environment
> > variable? I
> I suppose the functionality could be added to Mutt easily enough, but
> then you run into issues such as different MTA's which determine the
> envelope sender address in different ways... So there won't be a
> solution that works in all cases, and possibly not even in "most"
> cases.
That's w
Hi.
I have tried to create a save-hook for a mailing list that I am on, but it doesn't
seem to work. I may be confusing the way save-hook works though, so please correct me
if I am way off.
I created a hook in my .muttrc file:
save-hook linuxsa +linux
I assumed this was going to save any mail
Mike Bell <[EMAIL PROTECTED]> wrote on Thu, 09 Dec 1999:
> Would it be possible to arrange for the contents of the from: header in sent
> mail to be exported to the sendmail command, maybe as an environment
> variable? I'd like to have my envelope-sender mirror the address I use in my
> from: line
Would it be possible to arrange for the contents of the from: header in sent
mail to be exported to the sendmail command, maybe as an environment
variable? I'd like to have my envelope-sender mirror the address I use in my
from: line, since I send email from multiple accounts. Right now I'm settin
> > I haven't yet encountered an ISP POP3 server that doesn't do TOP.
> > I've only found one that didn't do UIDL.
>
> So would you have mutt use, or not use, the TOP command, and the UIDL
> command?
I'd have it try both. If TOP fails, I'd have it give up in disgust,
because you might as well d
On Thursday, 09 December 1999 at 10:45, Chris Green wrote:
> IMAP4 - typically corporate or university 'intranet' with fast,
> reliable links to your IMAP mailboxes. Thus it makes
> sense to use IMAP4 maiboxes for everything.
>
> POP3 - typically used by individual (
Tim --
...and then Timothy Ball said...
% I'm using mutt 1.0i and vim to to edit my mail... I've set the
% edit_headers thing and I have a sig on the bottom om my mail. Is there
% a way to start vim at the first blank line of my mail and be ready to
% start editing, instead of having to hit "i" t
I'm a little reluctant to reply to this message since I guess I have a
personal interest in mutt's IMAP support, but what the hell...
On Thursday, 09 December 1999 at 00:54, Kim DeVaughn wrote:
> On Wed, Dec 08, 1999, Thomas Roessler ([EMAIL PROTECTED]) said:
> |
> | On 1999-12-08 01:54:57 -0700,
On Thu, Dec 09, 1999 at 12:14:48PM -0800, Eugene Lee wrote:
> On Thu, Dec 09, 1999 at 01:40:18PM -0600, David DeSimone wrote:
> :
> :See, now we get to the case of why users are pointed to fetchmail:
> :Because fetchmail has been bloated, er, I mean, specifically written to
> :understand these bu
Raju --
...and then [EMAIL PROTECTED] said...
% hi,
%
% Since send-hook works before editing the message, it is useless when edit_headers is
set. Is there any patch which will invoke send-hook after editing is over that is just
before the actually sending the mail?
You may find it best to tur
Christian --
I'd love to hear a better answer, but I found that the easiest way for me
to accomplish a complete-thread-older-than-X save was to order by date,
tag everything older than X, re-order by thread, and tag the rest of the
thread (I actually had a working mailbox and I would save complet
I've been lurking on this list for a while and monitoring this thread on
and off. Now it is time to uncloak.
A key point in the Unix philosophy is to keep it simple, stupid
(KISS). The Unix way is lots of very stupid little programs, which you can
then glue together in new ways to produce new and
On Thu, Dec 09, 1999 at 01:40:18PM -0600, David DeSimone wrote:
:
:See, now we get to the case of why users are pointed to fetchmail:
:Because fetchmail has been bloated, er, I mean, specifically written to
:understand these buggy servers and try its best to deal with them.
:Trying to add this P
Zsombor Gergely <[EMAIL PROTECTED]> wrote:
>
> This is a call for help! The problem is still unresolved
What is the problem?
> I inserted set allow_8bit and set charset="iso-8859-2" into .muttrc,
> but nothing happened.
What was supposed to happen? What happened instead?
> I see everything co
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> wrote:
>
> I haven't yet encountered an ISP POP3 server that doesn't do TOP.
> I've only found one that didn't do UIDL.
So would you have mutt use, or not use, the TOP command, and the UIDL
command?
> Note that fetchmail quite happily uses "TOP n 99"
* Mikko Hänninen <[EMAIL PROTECTED]> wrote:
> Scott Scriven <[EMAIL PROTECTED]> wrote on Wed, 08 Dec 1999:
> > Is there some way to create a macro which simply runs a shell
> > command? I'd like to replace the "G" fetchmail key with a more
> > powerful script..
> bind index G "!yourscript\n" "Yo
This is a call for help! The problem is still unresolved
> I have just downloaded and compiled the newest version of mutt and gpg. They
> work fine together, but I was not able to configure everything well.
> I am Hungarian, so I would like to use accented letters (8 bit).
These are like áéőú, n
On Thu, Dec 09, 1999 at 01:40:17PM +, Edmund GRIMLEY EVANS wrote:
> > Have you ever stored a message in a POP3 folder without going
> > through the mail transport agent, i.e., without resending the
> > message? There is no standard way to do this.
>
> I'm not even aware of a non-standard way
On Thu, Dec 09, 1999 at 01:34:06PM +0100, Thomas Roessler wrote:
> On 1999-12-09 12:17:23 +, Chris Green wrote:
>
> >> Show us working code, or stop complaining, please.
>
> > See tkrat, mahogany and several other Unix MUAs.
>
> Do these have working IMAP support in _external_ programs?
>
> > That isn't "All you can reasonably do with POP3", it's perfectly
> > reasonable to treat a POP3 server as a single mailbox much the
> > same as a local mailbox file. You can see a list of the E-Mail
> > messages in a POP3 mailbox, you can selectively view messages in
> > a POP3 mailbox and yo
On 1999-12-09 12:17:23 +, Chris Green wrote:
>> Show us working code, or stop complaining, please.
> See tkrat, mahogany and several other Unix MUAs.
Do these have working IMAP support in _external_ programs?
--
http://www.guug.de/~roessler/
On Thu, Dec 09, 1999 at 12:50:42PM +0100, Thomas Roessler wrote:
> Show us working code, or stop complaining, please.
>
See tkrat, mahogany and several other Unix MUAs.
--
Chris Green ([EMAIL PROTECTED])
Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED]
WWW: http://www.isbd.co.uk/
On 1999-12-09 10:45:23 +, Chris Green wrote:
> That isn't "All you can reasonably do with POP3", it's perfectly
> reasonable to treat a POP3 server as a single mailbox much the
> same as a local mailbox file. You can see a list of the E-Mail
> messages in a POP3 mailbox, you can selectively
On Thu, Dec 09, 1999 at 10:53:17AM +0100, Thomas Roessler wrote:
> On 1999-12-09 00:54:26 -0700, Kim DeVaughn wrote:
>
> >> You are free to write such a program, and you are also free to
> >> design a generic interface between mutt and external mailbox
> >> backends. Note, however, that just dow
On 1999-12-09 00:54:26 -0700, Kim DeVaughn wrote:
>> You are free to write such a program, and you are also free to
>> design a generic interface between mutt and external mailbox
>> backends. Note, however, that just downloading messages into
>> some local folder and using the usual mbox/maildi
On 1999-12-09 09:28:40 +, Edmund GRIMLEY EVANS wrote:
>> mutt -s "Subject here" 'A. Recipient <[EMAIL PROTECTED]>'
>> < msg_file
> If you try this, I think you'll find the To field gets rewritten as:
> To: "A . Recipient" <[EMAIL PROTECTED]>
So just use this:
mutt -s "subject" '
> You mean like with:
>
> mutt -s "Subject here" 'A. Recipient <[EMAIL PROTECTED]>' < msg_file
If you try this, I think you'll find the To field gets rewritten as:
To: "A . Recipient" <[EMAIL PROTECTED]>
I discovered this slightly annoying behaviour last night while
investigating why a piece
29 matches
Mail list logo
