From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Any way to captuer smtp output when sending mail?
Date: Sat, 01 Nov 2014 20:46:15 -0400 [thread overview]
Message-ID: <87zjca8m5k.fsf@dv.local.lan> (raw)
In-Reply-To: <87h9yilp6d.fsf@motoko.kusanagi>
W. Greenhouse <wgreenhouse@riseup.net>
writes:
> Harry Putnam <reader@newsguy.com> writes:
>
> [...]
>
>> Thanks... I see that is not going to happen in my setup. DaveG has
>> pointed out that my sending setup probably is responsible.
>>
>> I use this in ~/.gnus
>> (setq mail-user-agent 'gnus-user-agent)
>> for roughly 1000 yrs or so.
>>
>> It ended up meaning sendmail for yrs... but now using exim4 on debian.
>
> Yeah, smtpmail-debug-info is only going to be relevant if you are using
> the all-elisp "smtpmail.el" smtp client to send outgoing mail; mail sent
> to sendmail/exim/postfix/etc. via their /usr/sbin/sendmail executables
> wouldn't cross that bridge.
[...] checking in to the snipped bit: `nessage-sendmail-extra-arguments'
Before getting too involved in the snipped suggestion... I think I
would like to ask at this point if users of smtpmail.el can offer any
arguments in favor of that method as apposed to others.
I know at one time, some years ago, it was about the only way to use
gnus on windows. But I'm not dealing with windows in this
discussion.
Perhaps there are good reasons to do it and I would be better off
spending my time getting setup for that.
Any speed or cpu differences of note?
Any other points infavor of all smtpmail.el?
next prev parent reply other threads:[~2014-11-02 0:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 16:13 Harry Putnam
2014-10-17 16:36 ` Filipp Gunbin
2014-10-17 21:37 ` Harry Putnam
2014-10-18 0:37 ` Filipp Gunbin
2014-10-18 11:56 ` Filipp Gunbin
2014-11-01 18:35 ` Harry Putnam
2014-11-01 19:02 ` W. Greenhouse
2014-11-02 0:46 ` Harry Putnam [this message]
2014-11-02 23:55 ` W. Greenhouse
2014-11-03 16:59 ` Harry Putnam
2014-10-18 14:10 ` Dave Goldberg
2014-11-01 18:24 ` Harry Putnam
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=87zjca8m5k.fsf@dv.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).