> > How does this delete the personal copy, but not the list copy?
>
> Both messages will have the same Message-ID field in the header.
Correct answer, but to the question "how does it recognise duplicates".
I should have been more specific - what I meant was: how does it delete
the personal co
[examples of directory structures]
> Mutt's default for saving messages seems to revolve around the From
> address (e.g. mail from [EMAIL PROTECTED] wants to save to ~/Mail/foo). Does
> anyone have some good ideas about how to manage their mailboxes? What
I tried
fcc-save-hook (mutt-users.*@mut
> > However, when you make fetchmail deliver directly to procmail, fetchmail
> > does not generate a "From " line at all, and neither does procmail - big
> > barf results. In that case, use fetchmail -> formail | procmail.
>
> I believe that this is misleading/incorrect information. I have
> m
> via mapi or imap protocol?
Imap
> > I am running: Debian Linux woddy kernel 2.4.7 with imaptool 0.9-4
>
> $ apt-cache search imaptool
> imaptool - A tool for creating client-side image maps
I have also installed imap
> > All folders i have Problems with have subdirectories. In my
> pager the
Michael Elkins [Mon, Apr 15, 2002 at 09:23:59AM -0700]:
> Nico Schottelius wrote:
> > I am wondering why mutt has to be locked while G-taking pop mails.
> > I think I still could work/send new mails while mutt does this work.
> > I also think that it would be senseful, if I get 500 messages, I co
17-Apr-02 at 10:23, Nico Schottelius ([EMAIL PROTECTED]) wrote :
> okay, this will be what I will do soon, but I am wondering why we shouldn't
> allow mutt to fork out the pop process.
POP3 support seems to be more of an afterthought. Most people who use POP
to access their mailboxes swear by fet
Michael,
BRAVO! Worked like a charm! Thank you very much!
This is clearly one for the mutt archives. Congratulations to you.
John
On 04/17/02, 04:59:46PM +0200, Michal 'hramrach' Suchanek wrote:
Yes, the files are identical, you do not need to attach the same thing
> twice ;-)
> The differe
Eduardo Gargiulo ([EMAIL PROTECTED]) muttered:
> I'm running mutt 1.3.28 and i have set followup_to honor_followup_to.
Good. :)
> I want to configure mutt to set mail-followup-to header just only with the
> address of the mailing list i'm posting to, and not with my address.
> Is there any way t
begin Simon White quotation:
>
> Can you not just do
>
> $ fetchmail (options) &
> $ mutt
Or, better:
fetchmail -d300
mutt
--
Shawn McMahon| McMahon's Laws of Linux support:
http://www.eiv.com | 1) There's more than one way to do it
AIM: spmcmahonfedex, sm
--+QahgC5+KEYLbs62
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* Eduardo Gargiulo <[EMAIL PROTECTED]>, 2002-04-17 13:03 -0400:
> Hi all.
Hi Eduardo!
> It is possible to use mutt as news reader?
My favorite nntp patch is Or
On Wed, Apr 17, 2002 at 01:17:53PM -0400, Dan Lowe wrote:
> Previously, s. keeling wrote:
> >
> > I think that last bit is the important part here. Why does it matter?
> > Who cares how it got to you. What's important is what you do with it
> > now. Are you goingg to reply to the poster who cc:
--+HP7ph2BbKc20aGI
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
* Andre Berger <[EMAIL PROTECTED]>, 2002-04-17 13:39 -0400:
> * Eduardo Gargiulo <[EMAIL PROTECTED]>, 2002-04-17 13:03 -0400:
[...]
> I wrote a little wrapper around NNTPPost:
Here's the correct version:
--0ntfKIWw70PvrIHh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* Andre Berger <[EMAIL PROTECTED]>, 2002-04-17 13:48 -0400:
> * Andre Berger <[EMAIL PROTECTED]>, 2002-04-17 13:39 -0400:
> > * Eduardo Gargiulo <[EMAIL PROTECTED
* Volker Kuhlmann <[EMAIL PROTECTED]> [04-17-02 02:28]:
> > > However, when you make fetchmail deliver directly to procmail, fetchmail
> > > does not generate a "From " line at all, and neither does procmail - big
> > > barf results. In that case, use fetchmail -> formail | procmail.
> >
> > I be
* Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> [2002-04-17 11:51:51 +0100]:
> I think getmail does better than fetchmail if the network goes down
> while it's polling the server: fetchmail has an annoying habit of
> losing its fetchids when this happens, resulting in the delivery of
> several hundred
Michael Tatge <[EMAIL PROTECTED]> wrote:
>
> set alternates appropriately and configure the lists you are subscribed to
> with the subscribe command. If you list-reply to a mailinglist mail
> which has a mft header mutt will only reply to the adresses in the mft
> header.
>
> HTH,
thanks, it wo
> (the mail would end up in my inbox instead of the list folder).
That should not happen. What does, say, your mutt-users procmail recipe look
like?
Mine's:
:0 H
* ^TO.*@mutt.org
mutt/
(plus a few others, for guug.de and gbnet.net messages too)
If you were to send a message to both me and mut
I want my sentbox folder to show me the recipient's name,
the date, etc. So I use this line in .muttrc. But all I get are blank
lines.
folder-hook sentbox set index_format="%d %t (%3l) %s"
If I use this line:
folder-hook sentbox set index_format="%d %s"
All I get is the date. What am I mi
On Wed, Apr 17, 2002 at 04:18:18PM +1200, Volker Kuhlmann wrote:
> > > However, when you make fetchmail deliver directly to procmail, fetchmail
> > > does not generate a "From " line at all, and neither does procmail - big
> > > barf results. In that case, use fetchmail -> formail | procmail.
> >
Eduardo Gargiulo wrote:
>
> I'm running mutt 1.3.28 and i have set followup_to honor_followup_to.
> I want to configure mutt to set mail-followup-to header just only with the
> address of the mailing list i'm posting to, and not with my address.
> Is there any way to do that? I mean remove other
* Eduardo Gargiulo <[EMAIL PROTECTED]> [2002-04-17 14:06]:
> I use diferent email addresses to subscribe to diferent lists,
> ejg-mutt for mutt-users and ejg-qmail for qmail lists. I use ejg too.
> Is the following alternetes set appropriately for my scenario?
>
> set alternates="^ejg.*(-mutt|-qm
Hi,
* Michael Montagne [04/17/02 20:25:08 CEST] wrote:
> I want my sentbox folder to show me the recipient's name,
> the date, etc. So I use this line in .muttrc. But all I get are blank
> lines.
> folder-hook sentbox set index_format="%d %t (%3l) %s"
Works here.
Why not use %v or %L inst
On Wed, Apr 17, 2002 at 02:16:47PM -0400, Mike Schiraldi wrote:
> > (the mail would end up in my inbox instead of the list folder).
>
> That should not happen. What does, say, your mutt-users procmail recipe look
> like?
>
> Mine's:
>
> :0 H
> * ^TO.*@mutt.org
> mutt/
Isn't that supposed to be
> Isn't that supposed to be "* ^TO_.*@..."? Aren't you missing an
> underscore there?
From the procmailrc man page:
If the regular expression contains `^TO_' it will be sub
stituted by `(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-
Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA
* Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> [2002-04-17 21:31:00 +0100]:
> Nicolas Rachinsky <[EMAIL PROTECTED]>:
>
> > > I think getmail does better than fetchmail if the network goes down
> > > while it's polling the server: fetchmail has an annoying habit of
> > > losing its fetchids when this
On Wed, Apr 17, 2002 at 10:42:46PM +0200, Nicolas Rachinsky wrote:
> * Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> [2002-04-17 21:31:00 +0100]:
> > Nicolas Rachinsky <[EMAIL PROTECTED]>:
> >
> > > > I think getmail does better than fetchmail if the network goes down
> > > > while it's polling the se
Hi,
* David Rock <[EMAIL PROTECTED]> [02-04-17 05:38]:
>On Thu, Apr 11, 2002 at 02:51:56PM +0200, Thorsten Haude wrote:
>> I have something similar:
>> Mail/in
>> Mail/ML/Mutt
>> Mail/ML/NEdit
>> Mail/ML/Debian/user
>> Mail/ML/Debian/misc
>> etc.
>Mutt's default for saving
Nicolas Rachinsky <[EMAIL PROTECTED]>:
> > I think getmail does better than fetchmail if the network goes down
> > while it's polling the server: fetchmail has an annoying habit of
> > losing its fetchids when this happens, resulting in the delivery of
> > several hundred duplicate messages in my
Hi,
* Edmund GRIMLEY EVANS [04/17/02 22:31:00 CEST] wrote:
> The start of my .procmailrc is below. The in-line Perl script removes
> all header fields except Date, From, Subject, To and Cc. MD5 sums are
> appended to $MAILDIR/MD5, so you should remove the beginning of that
> file from time to tim
--ZfOjI3PrQbgiZnxM
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Dan Lowe spake thus:
> Once you're on enough lists, sorting them into proper contains (folders)
> becomes important. I, like many, use Procmail for that.
--R+My9LyyhiUvIEro
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Mike Schiraldi spake thus:
> That should not happen. What does, say, your mutt-users procmail recipe l=
ook
> like?
>=20
> Mine's:
>=20
> :0 H
> * ^TO.*@mut
Alas! Mike Schiraldi spake thus:
> I'm
> not sure what kind of procmail voodoo you would need to grab this
> information from Delivered-To and fulfill the user's request, but it would
> be weird and scary.
You're so simple-minded. All you have to do is set up a temporal anomaly
in which procmail
On Wed, Apr 17, 2002 at 05:20:45PM -0600, Rob 'Feztaa' Park wrote:
> Alas! Mike Schiraldi spake thus:
> > I'm
> > not sure what kind of procmail voodoo you would need to grab this
> > information from Delivered-To and fulfill the user's request, but it would
> > be weird and scary.
>
> You're so
OK. I suppose that I can not locate a folder with new email using something
like /~N.
> How can I search a string or go to a folder with new emails in file browser?
> The / command seems to be working in a different way as that in index.
> Thanks.
> --
> Bo Peng
> Department of Statistics
> Ri
How do you limit to subjects in CAPS only,
ie containing not a single lowercase letter?
caveat: the subjects may have other characters -
but all the letters are uppercase.
note:
a pattern containing only
lowercase letters default
to checking uppercase
letters, too.
so this does not work:
! ~s
Have you tried this pattern?
[^a-z]
Joel
On Thu, Apr 18, 2002 at 04:14:18AM +0200, Sven Guckes wrote:
> How do you limit to subjects in CAPS only,
> ie containing not a single lowercase letter?
> caveat: the subjects may have other characters -
> but all the letters are uppercase.
>
> note:
>
in message <[EMAIL PROTECTED]>,
wrote s. keeling thusly...
>
> - _Something_ doesn't show you new mail 'til a few days after it
> arrives ('cause you have to wait for possible duplicates to
> arrive). Inconvenient, but for those who can't stand seeing
> duplicates (or the wrong dupl
On Thu, Apr 18, 2002 at 04:14:18AM +0200, Sven Guckes wrote:
> How do you limit to subjects in CAPS only,
> ie containing not a single lowercase letter?
> caveat: the subjects may have other characters -
> but all the letters are uppercase.
I've used this as a search pattern in the pager to highl
* Joel Hammer <[EMAIL PROTECTED]> [2002-04-18 02:20]:
> Have you tried this pattern? [^a-z]
no - because the limit command would then
match all subject lines which contain
at least one non-letter, such as
Subject: can you spot the non-letter?
to repeat:
i'm trying to limit all mails to those
* Gary Johnson <[EMAIL PROTECTED]> [2002-04-18 03:04]:
> On Thu, Apr 18, 2002 at 04:14:18AM +0200, Sven Guckes wrote:
> > How do you limit to subjects in CAPS only,
> > ie containing not a single lowercase letter?
> > caveat: the subjects may have other characters -
> > but all the letters are upp
* Sven Guckes <[EMAIL PROTECTED]> [2002-04-18 03:16]:
> > > How do you limit to subjects in CAPS only,
> > > ie containing not a single lowercase letter?
> ~s '^[^a-z]+$'
> YES! :-)
silly me. this solves another nice problem,
of course, but not the one I proposed. *sigh*
any more ideas, folks
--IS0zKkzwUGydFO0o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Sven Guckes spake thus:
> * Joel Hammer <[EMAIL PROTECTED]> [2002-04-18 02:20]:
> > Have you tried this pattern? [^a-z]
>=20
> no - because the limit comma
* Rob 'Feztaa' Park <[EMAIL PROTECTED]> [2002-04-18 03:28]:
> > > Have you tried this pattern? [^a-z]
> > no - because the limit command would then
> > match all subject lines which contain
> > at least one non-letter, such as
> > Subject: can you spot the non-letter?
>
> So then how about ^[^a
* On 2002.04.17, in <[EMAIL PROTECTED]>,
* "Rob 'Feztaa' Park" <[EMAIL PROTECTED]> wrote:
> So then how about ^[^a-z]+$ ? That would match anything that contained
> only non-lowercase-letters, wouldn't it?
No, because mutt makes that a case-insensitive match since the pattern
contains only
On Thu, Apr 18, 2002 at 05:15:54AM +0200, Sven Guckes wrote:
> * Gary Johnson <[EMAIL PROTECTED]> [2002-04-18 03:04]:
> > So you could probably adapt it for your
> > subject search. Maybe this (untried):
> > ~s "\^[A-Z0-9 [:punct:]]+$"
>
> sorry, no. the subject line may have
> a LOT of ot
Shawn McMahon writes:
> IMHO, if you hit "list-reply" and Mutt doesn't recognize a list, it
> should assume you know what you're talking about, and pop up the "To:"
> address as a "yes/no" default. Then if you say no, it should cycle
> through the Cc: addresses until you say "yes" or "q".
>
> Al
Hi. I'm having a bad problem with mutt: it tends to hang whenever it decides
it says "Sorting mailbox..." (any time I try to quit, change folders, or
recall a postponed message). It simply stops responding, and only SIGKILL
seems to kill it. My version is 1.3.28-1 from Debian sid; the full output
47 matches
Mail list logo
