From: gsf@fruct.us (Gabriel Sean Farrell)
Subject: [sup-talk] return-path
Date: Fri, 25 Jan 2008 02:50:12 -0500 [thread overview]
Message-ID: <1201246425-sup-9409@magnum> (raw)
In-Reply-To: <1201233750-sup-2616@south>
Excerpts from William Morgan's message of Thu Jan 24 23:03:58 -0500 2008:
> I don't think so... you can apply the patch below and see exactly what
> Sup is sending sendmail. In my case, that header is intact. So it must
> be getting overwritten somewhere else in the system.
>
> There's some crazy interaction between this header, the From: and
> Sender: headers, and the -f option of sendmail. Maybe you should use a
> -f with sendmail (in your ~/.sup/config.yaml file)? Did you have a
> particular way of calling sendmail with Mutt?
Right you are about the crazy interaction. It's not clear to me how
Mutt is calling sendmail, but now I'm guessing all that the "set
envelope_from=yes" does in mutt is add the -f flag followed by one's
"from" email to the call to sendmail.
If I do that in my ~/.sup/config.yaml, the return-path is set
correctly (at least, it was in my tests. How does this message
look?!). In fact, I believe it's set correctly even if I don't set
the return-path in ~/.sup/hooks/edit-before.rb or patch lib/mbox.rb.
In other words, all that needs to be done to fix my problem is the
addition of -f <email> to the sendmail call. Maybe it could be an
option in the initial account setup?
Oh, and thanks for all the work you're doing on sup, William. Really
great stuff.
next prev parent reply other threads:[~2008-01-25 7:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-23 21:13 Gabriel Sean Farrell
2008-01-23 22:12 ` William Morgan
2008-01-23 22:47 ` Gabriel Sean Farrell
2008-01-25 4:03 ` William Morgan
2008-01-25 7:50 ` Gabriel Sean Farrell [this message]
2008-01-27 20:03 ` Marcus Williams
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=1201246425-sup-9409@magnum \
--to=gsf@fruct.us \
/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