From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: No such function: nntp-request-accept-article solved
Date: Sat, 14 Sep 2002 17:33:24 -0400 [thread overview]
Message-ID: <2nofb045p7.fsf@zsh.cs.rochester.edu> (raw)
In-Reply-To: <sn0ccuk7.fsf@ID-23066.news.dfncis.de> (Clemens Fischer's message of "Sat, 14 Sep 2002 20:09:12 +0200")
Clemens Fischer <ino@despammed.com> writes:
> ShengHuo ZHU <zsh@cs.rochester.edu> writes:
>
>>> nnmail-expiry-target "nnfolder:EXPIRED" ; mit oder ohne??
>>> nnmail-expiry-wait-function
>>> (lambda (newsgroup)
>>> (cond
>>> ((string-match newsgroup "nnfolder:INBOX") 33)
>>> ((string-match newsgroup "nnfolder:abuse") 'never)
>>> ...))
>>>
>>
>> I think that the bug is related to nnmail-expiry-target, instead of
>> gnus-gcc-externalize-attachments. Are you sure you didn't
>> accidentally set your nnmail-expiry-target to nil or something else in
>> the previous setting?
>
> yes. i checked the settings in the group configuration ("G c") and
> remembered having changed the expiry target there, but that has been a
> while and should have effected other groups with similar settings
> there as well, no?
No.
> could you tell me how to achieve this behaviour? if sending
> attachments from my local disk, they are _not_ to be saved in my local
> copy of the outgoing message/article.
gnus-gcc-externalize-attachments is it. If the previous behavior
happens again, you'd better M-x toggle-debug-on-error RET, then post
the backtrace.
ShengHuo
next prev parent reply other threads:[~2002-09-14 21:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-14 0:33 clemens fischer
2002-09-14 1:36 ` ShengHuo ZHU
2002-09-14 18:09 ` Clemens Fischer
2002-09-14 21:33 ` ShengHuo ZHU [this message]
2002-09-16 15:15 ` Clemens Fischer
2002-09-27 22:49 ` Paul Jarc
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2nofb045p7.fsf@zsh.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).