unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 52205@debbugs.gnu.org
Subject: bug#52205: Allow configuring multiple mail accounts for smtpmail.el
Date: Sun, 19 Dec 2021 11:57:47 +0100	[thread overview]
Message-ID: <87bl1cyi8k.fsf@gnus.org> (raw)
In-Reply-To: <87bl1eqb5l.fsf@posteo.net> (Philip Kaludercic's message of "Sat,  18 Dec 2021 13:45:42 +0000")

Philip Kaludercic <philipk@posteo.net> writes:

>>>> Or we could add a command like `message-update-smtp-method-header' and
>>>> people could call that (or add it to their hooks) after altering their
>>>> From (or whatever) headers.
>>>
>>> So if the mechanism is supposed to be kept general (instead of just
>>> checking the From header), how would this differ from the already
>>> existing message-send-mail-hook?
>>
>> How a command would differ from a hook?  I'm not sure I understand the
>> question.
>
> Oh, sorry I misunderstood your suggestion.  So you are thinking of
> something that would be configured like:
>
> ;; `message-server-alist' would match the From header[0] if it is a string,
> ;; or call a function in the current message buffer if it is a function.
> (setq message-server-alist
>       '(("foo@mail.com" . "smtp.mail.com")
>         ("bar@post.de" . "post-spuep.de")))
>
> (add-hook 'message-send-mail-hook #'message-update-smtp-method-header)

No, I meant:

>>>> Or we could add a command like `message-update-smtp-method-header' and
>>>> people could call that

> If so, then couldn't the add-hook just be dropped, and message always
> checks message-server-alist before sending a message?

Yes.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-12-19 10:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-30 19:45 bug#52205: Allow configuring multiple mail accounts for smtpmail.el Philip Kaludercic
2021-12-01  4:08 ` Lars Ingebrigtsen
2021-12-01  9:01   ` Philip Kaludercic
2021-12-01 19:21     ` Lars Ingebrigtsen
2021-12-01 20:15       ` Philip Kaludercic
2021-12-01 20:24         ` Lars Ingebrigtsen
2021-12-02 23:06           ` Philip Kaludercic
2021-12-03 16:17             ` Lars Ingebrigtsen
2021-12-04  9:12               ` Philip Kaludercic
2021-12-04 19:01                 ` Lars Ingebrigtsen
2021-12-13 19:20                   ` Philip Kaludercic
2021-12-14 13:41                     ` Lars Ingebrigtsen
2021-12-18 13:45                       ` Philip Kaludercic
2021-12-19 10:57                         ` Lars Ingebrigtsen [this message]
2021-12-19 21:59                           ` Philip Kaludercic
2021-12-22 12:20                             ` Lars Ingebrigtsen
2022-09-09 17:53                               ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bl1cyi8k.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52205@debbugs.gnu.org \
    --cc=philipk@posteo.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).