Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread Christian Ebert 
* Zhengquan Zhang on Saturday, April 11, 2009 at 23:25:34 -0500
> I tried to use lisd-id to filter mutt mailing list in with procmail.
> But I did not find it in mutt mailing list emails.
> 
> So how do you filter out mutt mailing list emails?

I use List-Post for mutt and other lists. A bit simplified my
rule looks like this (for Maildir):

:0
* $ ^List-Post:.*mailto:\/[...@]+
Lists/$MATCH/

For mbox it would be:

:0:
* $ ^List-Post:.*mailto:\/[...@]+
Lists/$MATCH


c
-- 
  Was heißt hier Dogma, ich bin Underdogma!
[ What the hell do you mean dogma, I am underdogma. ]
_F R E E_  _V I D E O S_  http://www.blacktrash.org/underdogma/
  http://www.blacktrash.org/underdogma/index-en.html

Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread Zhengquan Zhang 
On Sun, Apr 12, 2009 at 02:23:06PM +0200, Christian Ebert wrote:

> :0
> * $ ^List-Post:.*mailto:\/[...@]+
> Lists/$MATCH/

I just noticed for other mailing list there is also such header.
Could you explain $MATCH here a little bit?

Thanks,

-- 
Zhengquan

Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread Zhengquan Zhang 
On Sun, Apr 12, 2009 at 07:54:48AM +0200, Markus Mueller wrote:
> 
> :0:
> * ^to.*mutt-us...@mutt\.org
> ml1/mutt-users/
> 
So, why do you use :0: instead of :0 here? when you are using a maildir?

Thanks,

-- 
Zhengquan

Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread Zhengquan Zhang 
On Sun, Apr 12, 2009 at 08:34:14AM +0200, Markus Mueller wrote:
> However,
> if you look at all headers, 'h' as default in pagermode, you will most
> likely find some unique header. Be it 'To:' or something else.
> The mutt-users list also is quite distinguishable:
> 
> Return-Path: owner-mutt-users+m12486=akamoto=ml1@mutt.org 
>   
> X-Mail-from: owner-mutt-users+m12486=akamoto=ml1@mutt.org 
>   
> To: mutt-users   
>   
> Mail-Followup-To: mutt-users 
>   
> List-Post:    
>   
> List-Unsubscribe: send mail to majord...@mutt.org, body only "unsubscribe 
> mutt-users"   
> Sender: owner-mutt-us...@mutt.org 
>   
> 
> Sender probably is the best field for this purpose, as nobody besides the
> admin can influence what is put there, whereas one could write mail 
> 'To: f...@invalid, mutt-users@mutt.org'

Thanks for the insight, I have a question, do you mean that only the
sender header is only influenced by the admin but other headers can be
rewritten by MTAs or others?


> 
> But if you make your matchexpression broad enough, you have several

Could you explain "make your matchexpression broad enough"?

Thanks,

-- 
Zhengquan

Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread Christian Ebert 
* Zhengquan Zhang on Sunday, April 12, 2009 at 10:22:48 -0500
> On Sun, Apr 12, 2009 at 02:23:06PM +0200, Christian Ebert wrote:
>> :0
>> * $ ^List-Post:.*mailto:\/[...@]+
>> Lists/$MATCH/
> 
> I just noticed for other mailing list there is also such header.
> Could you explain $MATCH here a little bit?

man 5 procmailrc says:

   MATCH   This variable is assigned to by procmail whenever it is
   told  to  extract  text  from  a matching  regular
   expression.   It will contain all text matching the regular
   expression past the `\/' token.


So List-Post: mailto:mutt-users@mutt.org is stored in Lists/mutt-users/

c
-- 
\black\trash movie_C O W B O Y_  _C A N O E_  _C O M A_
Ein deutscher Western/A German Western
-->> http://www.blacktrash.org/underdogma/ccc.html
-->> http://www.blacktrash.org/underdogma/ccc-en.html

Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread Cameron Simpson 
On 12Apr2009 10:30, Zhengquan Zhang  wrote:
| On Sun, Apr 12, 2009 at 08:34:14AM +0200, Markus Mueller wrote:
| > However,
| > if you look at all headers, 'h' as default in pagermode, you will most
| > likely find some unique header. Be it 'To:' or something else.
| > The mutt-users list also is quite distinguishable:
[...]
| > Sender: owner-mutt-us...@mutt.org   

| > 
| > Sender probably is the best field for this purpose, as nobody besides the
| > admin can influence what is put there, whereas one could write mail 
| > 'To: f...@invalid, mutt-users@mutt.org'
| 
| Thanks for the insight, I have a question, do you mean that only the
| sender header is only influenced by the admin but other headers can be
| rewritten by MTAs or others?

Pretty much. Sender can be written too. However, we're not defeating forgery,
we're trying to identify all mutt-users posts. The mailing list software
_always_ puts that header in, regardless of what people put in the to/cc/bcc
lines etc. So it is reliable in that sense.

Cheers,
-- 
Cameron Simpson  DoD#743
http://www.cskk.ezoshosting.com/cs/

Rules of Optimization:
Rule 1: Don't do it.
Rule 2 (for experts only): Don't do it yet.
- M.A. Jackson

[solved, Thanks!]Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread Zhengquan Zhang 
On Mon, Apr 13, 2009 at 06:48:18AM +1000, Cameron Simpson wrote:
> On 12Apr2009 10:30, Zhengquan Zhang  wrote:
> | On Sun, Apr 12, 2009 at 08:34:14AM +0200, Markus Mueller wrote:
> | > However,
> | > if you look at all headers, 'h' as default in pagermode, you will most
> | > likely find some unique header. Be it 'To:' or something else.
> | > The mutt-users list also is quite distinguishable:
> [...]
> | > Sender: owner-mutt-us...@mutt.org 
>   
> | > 
> | > Sender probably is the best field for this purpose, as nobody besides the
> | > admin can influence what is put there, whereas one could write mail 
> | > 'To: f...@invalid, mutt-users@mutt.org'
> | 
> | Thanks for the insight, I have a question, do you mean that only the
> | sender header is only influenced by the admin but other headers can be
> | rewritten by MTAs or others?
> 
> Pretty much. Sender can be written too. However, we're not defeating forgery,
> we're trying to identify all mutt-users posts. The mailing list software
> _always_ puts that header in, regardless of what people put in the to/cc/bcc
> lines etc. So it is reliable in that sense.
> 
> Cheers,
> -- 
> Cameron Simpson  DoD#743
> http://www.cskk.ezoshosting.com/cs/
> 
> Rules of Optimization:
> Rule 1: Don't do it.
> Rule 2 (for experts only): Don't do it yet.
> - M.A. Jackson

-- 
Zhengquan

Makefile:120: *** missing separator. Stop.

2009-04-12 Thread rj 
As a user on a FreeBSD system (without root access) I'd like to try to
install (in my home dir, for now) mutt-1.5.19.  I want to have it use
S-Lang 2.1.4.

Fisrt off, is this even possible for me to do without root access?

(This is also the first time I've ever tried to build / compile / install
mutt.)

In any event, here's what I've done, and what I've gotten:

[shell:~]  [v4.3.9]  zsh  1210 --> ls -la /usr/ports/mail/mutt-devel
total 48K
 2K drwxr-xr-x   5 root wheel   512 Feb 20 04:35 ./
18K drwxr-xr-x 726 root wheel 17920 Apr 10 12:08 ../
 2K drwxr-xr-x   2 root wheel   512 Aug  9  2008 CVS/
18K -rw-r--r--   1 root wheel 18200 Feb 20 04:35 Makefile
 2K -rw-r--r--   1 root wheel  1793 Feb 20 04:35 distinfo
 2K drwxr-xr-x   3 root wheel  1024 Feb 20 04:35 files/
 2K -rw-r--r--   1 root wheel   531 Nov 22  1999 pkg-descr
 2K drwxr-xr-x   3 root wheel   512 Feb 10 04:35 scripts/
[shell:~]  [v4.3.9]  zsh  1211 --> cd /usr/ports/mail/mutt-devel
[shell:/usr/ports/mail/mutt-devel]  [v4.3.9]  zsh  1212 --> make install clean
Makefile:120: *** missing separator.  Stop.
[shell:/usr/ports/mail/mutt-devel]  [v4.3.9]  zsh  1213 -->

The relevant part of Makefile looks like this (with line numbers):

116 PORTNAME=*..mutt-devel
117 PORTVERSION=*...1.5.19
118 PORTREVISION?=*.1
119 CATEGORIES+=*...mail ipv6
120 .if defined(WITH_MUTT_NNTP)
121 CATEGORIES+=*...news
122 .endif
123 MASTER_SITES=  [etc]

Line 120 is the first line in the file that begins with a dot.
Can / should line 120 be edited /modified /fixed?

Am I doing any of this correctly?



pgpFc1FxtdzPm.pgp
Description: PGP signature

Re: vcf attachment

2009-04-12 Thread Sean Escriva 
On Sat, Apr 11, 2009 at 06:37:50PM +0800, bill lam wrote:
> There are vcf attachments with mime type 
> text/x-vcard
> text/directory

make sure your .muttrc auto_view line doesn't have either of those.

if you .mailcap entry for those items doesn't have 'copiusoutput' it
shouldn't be displayed inline, regardless of your auto_view setting.

http://www.mutt.org/doc/manual/manual-5.html#auto_view

> 
> I don't want to look at them, how to configure the mailcap or
> otherwise so that vcf will not be shown inline?
> 
> -- 
> regards,
> 
> GPG key 1024D/4434BAB3 2008-08-24
> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
> ??118 ??  ?
> ???  ???  ???  ???
> ???  ???  ???  ???

Re: no list-id header for mutt-u...@mutt.org

2009-04-12 Thread J. Limon 
On Sat, Apr 11, 2009 at 11:25:34PM -0500, Zhengquan Zhang wrote:
> Dear mutt community,
> 
> I tried to use lisd-id to filter mutt mailing list in with procmail.
> But I did not find it in mutt mailing list emails.
> 
> So how do you filter out mutt mailing list emails?
> 
> Thanks and regards,
> 
> -- 
> Zhengquan

I just use the SENDER id like this.

* ^Sender: owner-mutt-us...@mutt.org
$HOME/Mail/Mutt-Users

Works perfectly so far. :)

-- 
"If a problem can be solved there is no use worrying about it. If it can't be 
solved, worrying will do no good."

Re: vcf attachment

2009-04-12 Thread bill lam 
On Sun, 12 Apr 2009, Sean Escriva wrote:
> On Sat, Apr 11, 2009 at 06:37:50PM +0800, bill lam wrote:
> > There are vcf attachments with mime type 
> > text/x-vcard
> > text/directory
> 
> make sure your .muttrc auto_view line doesn't have either of those.
> 
> if you .mailcap entry for those items doesn't have 'copiusoutput' it
> shouldn't be displayed inline, regardless of your auto_view setting.
> 

my .muttrc and .mailcap do not contain them. But system default
/etc/mailcap does contain lines for text/* 

-- 
regards,

GPG key 1024D/4434BAB3 2008-08-24
gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
唐詩015 王維  青谿
言入黃花川  每逐青谿水  隨山將萬轉  趣途無百里  聲喧亂石中  色靜深松裡
漾漾汎菱荇  澄澄映葭葦  我心素已閒  清川澹如此  請留盤石上  垂釣將已矣

compiling mutt 1.5.19 on Solaris 10: iconv errors

2009-04-12 Thread June Qiu 

Hi,
I can't figure out why I have the following errors when I am using 
libiconv 1.12. Pls help!
 
:
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
checking whether iconv.h defines iconv_t... yes
checking whether this iconv is good enough... no
configure: error: Try using libiconv instead

Re: compiling mutt 1.5.19 on Solaris 10: iconv errors

2009-04-12 Thread Kyle Wheeler 
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday, April 12 at 08:49 PM, quoth June Qiu:
>I can't figure out why I have the following errors when I am using 
>libiconv 1.12. Pls help!
> 
>:
>checking iconv.h usability... yes
>checking iconv.h presence... yes
>checking for iconv.h... yes
>checking whether iconv.h defines iconv_t... yes
>checking whether this iconv is good enough... no
>configure: error: Try using libiconv instead

The exact compilation details will be in your config.log file (you 
probably aren't actually *using* the libiconv you installed).

Essentially, that "is good enough" test is checking whether iconv will 
convert from UTF-8 to UTF-8 (which *SHOULD* be a no-brainer, but is 
broken in some iconv implementations).

~Kyle
- -- 
It has been my experience that folks who have no vices have very few 
virtues.
 -- Abraham Lincoln
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkniwFEACgkQBkIOoMqOI17VMgCfc2c8PcdybBrG1ixcYjtxr510
XH8An3+5q8gyw5T1Jl3CDQ6yXA5+RHXN
=zlNr
-END PGP SIGNATURE-

re-casting previous question

2009-04-12 Thread rj 
Maybe I should re-phrase my previous question to ask
what does the warning

"Makefile:120: *** missing separator.  Stop."

actually mean, how should I interpret it and what should I do about it?

Thanks for any pointers.



pgpyV5d3hiip6.pgp
Description: PGP signature

Re: re-casting previous question

2009-04-12 Thread rj 
Also just to add that I'm working on FreeBSD 7.1:

 --> uname -a

FreeBSD shell.vex.net 7.1-RELEASE FreeBSD 7.1-RELEASE #0:
Thu Jan 1 14:37:25 UTC 2009
r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386



pgpWGZufgklAq.pgp
Description: PGP signature

Re: re-casting previous question

2009-04-12 Thread George Davidovich 
On Mon, Apr 13, 2009 at 01:34:53AM -0400, rj wrote:
> Also just to add that I'm working on FreeBSD 7.1:
> 
>  --> uname -a
> 
> FreeBSD shell.vex.net 7.1-RELEASE FreeBSD 7.1-RELEASE #0:
> Thu Jan 1 14:37:25 UTC 2009
> r...@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

Your question is not a mutt question, and it certainly doesn't merit
being asked three times in relatively quick succession to a few thousand
people, most of whom I'd guess are using Linux.

That said, the fine Handbook should be your first source for
information.  Specifically:

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html

Hopefully, the multiple references to ports(7) won't escape your notice.

If you still don't understand things, or otherwise have additional
questions, the place to ask is freebsd-questi...@freebsd.org.

-- 
George

Re: re-casting previous question

2009-04-12 Thread rj 
On Sun 04/12/09 at 11:01 PM -0700,
George Davidovich  wrote:

> Your question is not a mutt question,

As it's the first time I've tried installing mutt (on any system),
I assumed it was a mutt question.

I know now that it's an OS issue, not a mutt issue.  You and the list have
my mea culpa.



pgpIe168MOANC.pgp
Description: PGP signature