Re: EXITCODE==255

2011-06-22 Thread Athanasius 
On Tue, Jun 21, 2011 at 01:29:17PM -0500, David Champion wrote:
 * On 18 Jun 2011, Joseph wrote: 
  
  :0e
  EXITCODE=$?
 
 I think this is still going to write to a file named EXITCODE=255.
 IIRC the line after :0 is either a delivery rule (a folder) or an open
 brace.  If you want to set a variable as a result of the match, without
 delivering, you need:
 
 :0e
 {
   EXITCODE=$?
 }
 
 or more concisely,
 
 :0e
 { EXITCODE=$? }

  Ah, indeed my own recipes using EXITCODE are like:

##
## Things that aren't spam per se, but we don't seem to be able to
## unsubscribe from
##
:0
* ^FROM.*lists@meridianmagazine\.com
{
EXITCODE=67
:0
/dev/null
}

'67' is 'EX_NOUSER', i.e. it should go back up the procmailrc/MTA chain
to tell the sender User doesn't exist.

-- 
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
  Finger athan(at)fysh.org for PGP key
   And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence. Paula Cole - ME


signature.asc
Description: Digital signature

Re: EXITCODE==255

2011-06-22 Thread lee 
Athanasius m...@miggy.org writes:

 ##
 ## Things that aren't spam per se, but we don't seem to be able to
 ## unsubscribe from
 ##
 :0
 * ^FROM.*lists@meridianmagazine\.com
 {
 EXITCODE=67
 :0
 /dev/null
 }

 '67' is 'EX_NOUSER', i.e. it should go back up the procmailrc/MTA chain
 to tell the sender User doesn't exist.

Your MTA should deny such messages instead of receiving them.

Revisiting: application/pgp-signature is unsupported

2011-06-22 Thread Lars Hecking 

 There was a thread on this mailing list back in March,
 http://marc.info/?l=mutt-usersm=130016436305546w=2
 
 List:   mutt-users
 Subject:application/pgp-signature is unsupported
 From:   Joseph  xxx () gmail ! com
 Date:   2011-03-15 4:44:57

 which doesn't seem to have had a resolution.

 I am facing the same problem now, but may have a bit more information.

 The copy of mutt I'm using is fully supporting signed/encrypted emails.
 Point in case, the earlier, signed message to this list

 Date: Wed, 22 Jun 2011 04:10:36 -0400
 From: Athanasius m...@miggy.org
 To: Joseph syscon...@gmail.com, mutt-users@mutt.org mutt-users@mutt.org
 Subject: Re: EXITCODE==255

 presents no problems whatsoever. But there are some messages mutt fails to
 interpret correctly. I think this all started when $work moved to Exchange.
 Exchange seems to have the nice and friendly habit of rewriting all sorts of
 things on delivery, although in this case I have no proof without the original
 message (MIME info and attachments are scrubbed from the corresponding mailing
 list archive).

 The messages that fail have the following MIME structure:

 I 1 no description [text/plain, quoted, windows-1251, 1.6K]
 A 2 This is a digitally signed message part.[applica/pgp-signat, base64, 0
 A 3 ATT1.c   [text/plain, base64, us-ascii, 0.2K]

 Part two is the signature, encoded in base64, and part three is a mailing
 list footer, also in base64. Also note that the header Content-Type: is
 multipart/mixed rather than multipart/signed.