From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/45738 Path: main.gmane.org!not-for-mail From: Nevin Kapur Newsgroups: gmane.emacs.gnus.general Subject: Re: nnimap, expiry-target, nnmail-fancy-expiry-targets Date: Fri, 19 Jul 2002 11:24:00 -0400 Organization: Mathematical Sciences, The Johns Hopkins University Sender: owner-ding@hpc.uh.edu Message-ID: References: <87sn2fiznh.fsf@hal.Olympus.INVALID> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1027092702 26907 127.0.0.1 (19 Jul 2002 15:31:42 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Fri, 19 Jul 2002 15:31:42 +0000 (UTC) Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17VZjI-0006zs-00 for ; Fri, 19 Jul 2002 17:31:41 +0200 Original-Received: from sina.hpc.uh.edu ([129.7.128.10] ident=lists) by malifon.math.uh.edu with esmtp (Exim 3.20 #1) id 17VZiM-0004Xc-00; Fri, 19 Jul 2002 10:30:42 -0500 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 19 Jul 2002 10:31:06 -0500 (CDT) Original-Received: from sclp3.sclp.com (qmailr@sclp3.sclp.com [209.196.61.66]) by sina.hpc.uh.edu (8.9.3/8.9.3) with SMTP id KAA13644 for ; Fri, 19 Jul 2002 10:30:51 -0500 (CDT) Original-Received: (qmail 245 invoked by alias); 19 Jul 2002 15:30:22 -0000 Original-Received: (qmail 240 invoked from network); 19 Jul 2002 15:30:22 -0000 Original-Received: from main.gmane.org (80.91.224.249) by gnus.org with SMTP; 19 Jul 2002 15:30:22 -0000 Original-Received: from root by main.gmane.org with local (Exim 3.33 #1 (Debian)) id 17VZhp-0006vd-00 for ; Fri, 19 Jul 2002 17:30:09 +0200 Original-To: ding@gnus.org X-Injected-Via-Gmane: http://gmane.org/ Original-Received: from news by main.gmane.org with local (Exim 3.33 #1 (Debian)) id 17VZbo-0006bA-00 for ; Fri, 19 Jul 2002 17:23:56 +0200 Original-Path: not-for-mail Original-Newsgroups: gmane.emacs.ding Original-Lines: 53 Original-NNTP-Posting-Host: fermat.mts.jhu.edu Original-X-Trace: main.gmane.org 1027092236 25347 128.220.17.18 (19 Jul 2002 15:23:56 GMT) Original-X-Complaints-To: usenet@main.gmane.org Original-NNTP-Posting-Date: Fri, 19 Jul 2002 15:23:56 +0000 (UTC) X-Face: #i!d%y+1tilG}1ua9z&9waMLqE>H+;pUwWFetZe]4uWiv;VE:GHLnT1\Gj]>l^(]R#}sD@E"(@?vMv,yb@`?32;i~D$6x6m*%!3gPyp-rb$}.%QpxZ!3Y+jESN5[s7SL_68Sc`Aek)A$M|h++b/2VjR.k+Tw4X+0a%:K-kcUeMZ(rs?}v\eG({5J&IPS Mail-Copies-To: never User-Agent: Gnus/5.090007 (Oort Gnus v0.07) XEmacs/21.4 (Honest Recruiter, i686-pc-linux) Cancel-Lock: sha1:O13iqdREGB/bwa/2vffXFNYKKlE= Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:45738 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:45738 "Davide G. M. Salvetti" writes: > I've a problem with the stuff in the subject line. > [...] > * nnmail-fancy-expiry-targets: > <======================================================================> > (setq nnmail-fancy-expiry-targets > '(("from" ".*" "nnimap+mail:Mail/Archive/%Y-%m"))) > <======================================================================> > > (note that here nnimap+mail is a well working backend). > > However, it doesn't work as I expected: when I press "C-c C-x" on the > group from the *Group* buffer I get the following backtrace: > > <======================================================================> > Debugger entered--Lisp error: (wrong-type-argument stringp nil) > string-match(".*" nil) ^^^ Bizarre. This implies that one of the articles that you were trying to expire did not have a From header. Is that true? [...] > 1737 UID FETCH 3 BODY.PEEK[] > 1737 OK UID FETCH completed > <======================================================================> > > (note 1737 here above). > > I'm afraid I don't know enough of the IMAP protocol to understand it any > further. :-( Unfortunately, me neither. When I wrote the fancy expiry stuff, I relied on message-fetch-field to find the header to match against. > Am I doing this thing properly, or is there an other way to reach my > archiving goal? If it's true that the message in question does not have a From header, then I guess we should decide on the right behavior. Certainly an error is not the right behavior! If the message does have a from header, could you run M-: (message-fetch-field "from") on it and see if you get something non-nil? -Nevin