Gnus development mailing list
 help / color / mirror / Atom feed
From: W. Greenhouse <wgreenhouse-sGOZH3hwPm2sTnJN9+BGXg@public.gmane.org>
To: ding-smP1P7uqpqc@public.gmane.org
Subject: Re: Any way to captuer smtp output when sending mail?
Date: Sat, 01 Nov 2014 19:02:34 +0000	[thread overview]
Message-ID: <87h9yilp6d.fsf@motoko.kusanagi> (raw)
In-Reply-To: <874muiahwq.fsf@reader.local.lan>

Harry Putnam <reader-kFrNdAxtuftBDgjK7y7TUQ@public.gmane.org> 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.

Perhaps you could customize `message-sendmail-extra-arguments' to a
value that would log more verbosely. something like "-D some-file.txt"
would send error reporting info there in sendmail's sendmail; perhaps
exim has a similar setting.

--
Good luck,
WGG




  reply	other threads:[~2014-11-01 19:02 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 [this message]
2014-11-02  0:46           ` Harry Putnam
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=87h9yilp6d.fsf@motoko.kusanagi \
    --to=wgreenhouse-sgozh3hwpm2stnjn9+bgxg@public.gmane.org \
    --cc=ding-smP1P7uqpqc@public.gmane.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).