Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: howto have nnimap setup for smtp out
Date: Mon, 25 Jan 2021 18:37:48 -0500	[thread overview]
Message-ID: <87czxs610z.fsf@local.lan> (raw)
In-Reply-To: <87zh0w7j70.fsf@local.lan>

Harry Putnam <reader@newsguy.com> writes:

> Robert Pluim <rpluim@gmail.com> writes:
>
>>>>>>> On Wed, 20 Jan 2021 10:21:45 -0500, Harry Putnam <reader@newsguy.com> said:

[...]

>> Sending email from gnus using smtp is entirely separate from imap. Iʼd
>> recommend something like
>>
>> (setq send-mail-function smtpmail-send-it
>>       smtpmail-smtp-server "smtp.gmail.com"
>>       smtpmail-stream-type tls
>>       smtpmail-smtp-service 465
>>       user-mail-address "yourusername@gmail.com")
>>
>
> I tried that out with these changes:
>
> (setq send-mail-function smtpmail-send-it
>       smtpmail-smtp-server "smtp.gmail.com"
>       smtpmail-stream-type tls
>       smtpmail-smtp-service 465
>       user-mail-address "hputnam3@gmail.com")

Sorry, about half of my post got left out:

I discovered it would not work and so saved the backtrace to include
in this mail but then didn't do it.

('smtpmail-send-it) so tried it that way too, but still fails, again
saved a back trace

  Debugger entered--Lisp error: (void-variable smtpmail-send-it)
    (setq send-mail-function smtpmail-send-it)
    eval-region(380 578)  ; Reading at buffer position 578
    funcall-interactively(eval-region 380 578)
    call-interactively(eval-region record nil)
    command-execute(eval-region record)
    execute-extended-command(nil "eval-region" nil)
    funcall-interactively(execute-extended-command nil "eval-region" nil)
    call-interactively(execute-extended-command nil nil)
    command-execute(execute-extended-command)
  
But I got to looking at the code you sent and started thinking there
was a single quote missing right before smtpmail-send-it like
('smtpmail-send-it) so tried it that way too, but still fails, again
saved a back trace

  Debugger entered--Lisp error: (void-variable smtpmail-stream-type)
    eval-region(380 579)  ; Reading at buffer position 579
    funcall-interactively(eval-region 380 579)
    call-interactively(eval-region record nil)
    command-execute(eval-region record)
    execute-extended-command(nil "eval-region" nil)
    funcall-interactively(execute-extended-command nil "eval-region" nil)
    call-interactively(execute-extended-command nil nil)
    command-execute(execute-extended-command)

So wasn't really able to test it in mail



  parent reply	other threads:[~2021-01-25 23:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 15:21 Harry Putnam
2021-01-20 16:03 ` Robert Pluim
2021-01-25 22:20   ` Harry Putnam
2021-01-25 22:42     ` Clemens Schüller
2021-01-25 23:37       ` Malcolm Purvis
2021-01-25 23:47       ` Harry Putnam
2021-01-26 17:49         ` Clemens Schüller
2021-01-25 23:37     ` Harry Putnam [this message]
2021-01-26  2:53       ` Harry Putnam
2021-01-26 10:10         ` Robert Pluim
2021-01-20 16:04 ` Adam Sjøgren
2021-01-20 16:12 ` dick.r.chiang
2021-01-26 17:05   ` Harry Putnam
2021-01-26 17:48     ` Robert Pluim

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=87czxs610z.fsf@local.lan \
    --to=reader@newsguy.com \
    --cc=ding@gnus.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).