Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Memnon Anon <gegendosenfleisch@googlemail.com>
To: info-gnus-english@gnu.org
Subject: Re: FAQ 5.2 still correct? [solved]
Date: Tue, 8 Jul 2008 18:51:20 -0700 (PDT)	[thread overview]
Message-ID: <1ead6e92-5591-4519-94fe-99d236e67a15@x35g2000hsb.googlegroups.com> (raw)
In-Reply-To: <a0e330db-bc05-48b2-af0f-2d2502e82a1c@c58g2000hsc.googlegroups.com>

Solved!

As I said, gnus per se did not add the message-id.
I confirmed this again by using
(setq message-generate-headers-first t).
No Message-Id was generated, but mail in ~/Mail/queued-mail/
had a Message-Id.
So I had a look at smtpmail.el. This file contains these lines:

	    ;; Insert a `Message-Id:' field if there isn't one yet.
	    (goto-char (point-min))
	    (unless (re-search-forward "^Message-Id:" delimline t)
	      (insert "Message-Id: " (message-make-message-id) "\n"))

I just
- copied the file to smtpmail-changed.el
- added ;; in front of each of those three lines
- changed the last line to (provide 'smtpmail-changed)
- changed my .gnus to (require 'smtpmail-changed)

Now, my Message-Id is set by the google smtp-server ;)

Great!
Thanks to the author of smtpmail.el for extensively documenting
each single step in there!

  reply	other threads:[~2008-07-09  1:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-23 21:27 FAQ 5.2 still correct? Memnon Anon
2008-07-05  0:18 ` Memnon Anon
2008-07-06 19:08   ` renaudr
2008-07-07  5:03     ` Memnon Anon
2008-07-09  1:51       ` Memnon Anon [this message]
2008-07-09 14:11         ` FAQ 5.2 still correct? [solved] Ted Zlatanov
2008-07-10 13:59           ` Option for sendmail.el WAS: " Memnon Anon
2008-07-10 14:53             ` Ted Zlatanov
2008-07-12  2:06               ` Memnon Anon
2008-07-14 14:16                 ` Ted Zlatanov
2008-07-14 17:56                   ` Option for sendmail.el Memnon Anon
2008-07-14 19:08                     ` Ted Zlatanov
2008-07-17 21:23                       ` Memnon Anon

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=1ead6e92-5591-4519-94fe-99d236e67a15@x35g2000hsb.googlegroups.com \
    --to=gegendosenfleisch@googlemail.com \
    --cc=info-gnus-english@gnu.org \
    /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).