From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/52045 Path: main.gmane.org!not-for-mail From: kai.grossjohann@gmx.net (Kai =?iso-8859-1?q?Gro=DFjohann?=) Newsgroups: gmane.emacs.gnus.general Subject: Re: Gnus Agent and mail Date: Thu, 01 May 2003 12:57:16 +0200 Organization: University of Duisburg, Germany Sender: ding-owner@lists.math.uh.edu Message-ID: <84bryn7x4j.fsf@lucy.is.informatik.uni-duisburg.de> References: <6uiswfhrqs.fsf@zork.zork.net> <8465phob8k.fsf@lucy.is.informatik.uni-duisburg.de> <87d6jk1flj.fsf@cam.ac.uk> <84bryp9vbx.fsf@lucy.is.informatik.uni-duisburg.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: main.gmane.org 1051786773 6040 80.91.224.249 (1 May 2003 10:59:33 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Thu, 1 May 2003 10:59:33 +0000 (UTC) Original-X-From: ding-owner+M588@lists.math.uh.edu Thu May 01 12:59:30 2003 Return-path: Original-Received: from malifon.math.uh.edu ([129.7.128.13]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 19BBmk-0001ZB-00 for ; Thu, 01 May 2003 12:59:30 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19BBnH-0008G5-00; Thu, 01 May 2003 06:00:03 -0500 Original-Received: from sclp3.sclp.com ([64.157.176.121]) by malifon.math.uh.edu with smtp (Exim 3.20 #1) id 19BBn8-0008Fl-00 for ding@lists.math.uh.edu; Thu, 01 May 2003 05:59:54 -0500 Original-Received: (qmail 52169 invoked by alias); 1 May 2003 10:59:53 -0000 Original-Received: (qmail 52164 invoked from network); 1 May 2003 10:59:53 -0000 Original-Received: from quimby.gnus.org (80.91.224.244) by sclp3.sclp.com with SMTP; 1 May 2003 10:59:53 -0000 Original-Received: from news by quimby.gnus.org with local (Exim 3.12 #1 (Debian)) id 19BBvT-0003lb-00 for ; Thu, 01 May 2003 13:08:31 +0200 Original-To: ding@gnus.org Original-Path: not-for-mail Original-Newsgroups: gnus.ding Original-Lines: 73 Original-NNTP-Posting-Host: pd951fdcc.dip.t-dialin.net Original-X-Trace: quimby.gnus.org 1051787311 14392 217.81.253.204 (1 May 2003 11:08:31 GMT) Original-X-Complaints-To: usenet@quimby.gnus.org Original-NNTP-Posting-Date: 1 May 2003 11:08:31 GMT In-Reply-To: (Kevin Greiner's message of "Tue, 29 Apr 2003 21:12:20 -0500") Mail-Copies-To: never User-Agent: Gnus/5.09002 (Oort Gnus v0.20) Emacs/21.3.50 (gnu/linux) Cancel-Lock: sha1:eQdXI1T2GqrdgBnt53D8Y7cru0M= Precedence: bulk Xref: main.gmane.org gmane.emacs.gnus.general:52045 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:52045 Kevin Greiner writes: > kai.grossjohann@gmx.net (Kai Großjohann) writes: > >> Gaute's suggestion wasn't to frob the IMAP behavior. Just that >> message-send-mail-function be different. >> >> At least that's my understanding. > > Actually, Sean's original description was of setting a server > parameter to always plug his mail server. I'm not certain that that > works but he certainly expected it to. Okay, I know nothing about what Sean said -- that message seems inaccessible at the moment. I was responding to Gaute... > Gaute did ask specifically about mail. I checked and the agent > controls mail queuing/sending in the function gnus-agent-send-mail. > In that function gnus-plugged is the controlling variable. Well, message-send-mail-function could be set to message-send-mail-with-sendmail or the like, then the Agent wouldn't be involved in sending mail at all. > Now then, some unasked questions. > > First, if a mail backend is configured (by some as yet unspecified > mechanism) to post messages while unplugged. How does it handle > fetching? Should it act like it's unplugged or plugged? Well, posting appears to be different from sending mail. Hm. Anyhow, you can configure the unplugged behavior for each mail-sources entry -- see the :plugged keyword. So I think it's not necessary to configure this on a per-server basis. > Second, if I have multiple mail servers, should I be able to configure > each individually? For outgoing mail, such things seem to be difficult. AFAIK, there is no builtin functionality in Gnus that allows you to choose different outgoing mail servers. You'd have to kludge it somehow. And while you're at it (at kludging, I mean), you can also kludge the value of message-send-mail-function in the same manner. > My answers were such that individual mail servers could be configured > to act as if they were always plugged. At that point, I was one small > step from ANY server can be configured to be permanently plugged. Well, if a backend is not under Agent control, then it behaves like it is always plugged. Hm. So what would be the advantage of enrolling a server in the agent but at the same time configuring it to be always plugged? Hm. It would use the agent cache features. Yeah, that might actually make sense. Hm. I thought that most of the necessary functionality was there already, but it seems you have a point -- even more functionality may be desirable. *** It seems that we were talking cross-purposes a bit. I was talking about sending mail, whereas you seemed to have been talking about fetching mail. Also, you spoke of posting messages (to nnimap, I guess), which I didn't address at all. -- file-error; Data: (Opening input file no such file or directory ~/.signature)