Gnus development mailing list
 help / color / mirror / Atom feed
From: Sebastian Luque <spluque@gmail.com>
Subject: sending messages outside Gnus
Date: Sun, 04 Sep 2005 13:43:11 -0500	[thread overview]
Message-ID: <87slwjwppn.fsf@mun.ca> (raw)

[-- Attachment #1: Type: text/plain, Size: 71 bytes --]

I'm resending the message below as it hasn't been posted after 24 h.



[-- Attachment #2.1: Type: text/plain, Size: 649 bytes --]

Hi,

I have mail-user-agent set to gnus-user-agent, but doing 'C-x m' before
starting Gnus (No Gnus v0.4) gives:

,-----
| Debugger entered--Lisp error: (void-function gnus-agent-possibly-save-gcc)
|   gnus-agent-possibly-save-gcc()
|   run-hooks(message-header-hook)
|   message-send-mail(nil)
|   message-send-via-mail(nil)
|   message-send(nil)
|   message-send-and-exit(nil)
|   call-interactively(message-send-and-exit)
`-----

although no problems occur if Gnus is running or was started once in the
session.

The issue came up in the past, and the best solution I found was:

--8<---------------cut here---------------start------------->8---

[-- Attachment #2.2: Type: application/emacs-lisp, Size: 1118 bytes --]

[-- Attachment #2.3: Type: text/plain, Size: 531 bytes --]


but this uses gnus-no-server, which obviously starts Gnus.  Is there a
more efficient way to accomplish sending mails outside of Gnus, such that
a) a copy of the message is sent to myself¹, or b) a Gcc header is used,
causing the message to be stored in gnus-message-archive-group?

Thanks in advance for any suggestions,

Sebastian


+---- *Footnotes* ----+
¹ Using e.g. Bcc, being careful to add my address if such a header already
exists with some entries, or the header is added with my address in it.

-- 
Sebastian P. Luque

                 reply	other threads:[~2005-09-04 18:43 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87slwjwppn.fsf@mun.ca \
    --to=spluque@gmail.com \
    /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).