From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] return-path
Date: Wed, 23 Jan 2008 14:12:07 -0800 [thread overview]
Message-ID: <1201125726-sup-1297@south> (raw)
In-Reply-To: <20080123211318.GB31529@manheim.library.drexel.edu>
Reformatted excerpts from Gabriel Sean Farrell's message of 2008-01-23:
> I'm writing this message in mutt instead of sup because I send my
> email via a postfix relay-host and mutt allows me to set my
> Return-Path equal to my "From:" address with "set envelope_from=yes".
> If I don't do this, my email is often rejected from mailing lists.
>
> I believe other email clients default to this behavior (see
> http://www.mail-archive.com/mutt-users at mutt.org/msg26743.html for the
> post I'm basing my assumption on). Could sup follow that, or at least
> allow the option?
The Sup way to do this is to have the following line in your
~/.sup/hooks/before-edit.rb:
header["Return-Path"] = header["From"]
Unfortunately, you have to apply the following patch or Sup simply
discards that header. There's a better solution, which is to make Sup
not discard any headers set by the user when composing email, and I will
take it as a bugfix task to implement that for the next release.
diff --git a/lib/sup/mbox.rb b/lib/sup/mbox.rb
index 0ce52fe..55dd44f 100644
--- a/lib/sup/mbox.rb
+++ b/lib/sup/mbox.rb
@@ -32,6 +32,7 @@ module MBox
/^(List-Post):\s+(.*?)\s*$/i,
/^(List-Subscribe):\s+(.*?)\s*$/i,
/^(List-Unsubscribe):\s+(.*?)\s*$/i,
+ /^(Return-Path):\s+(.*?)\s*$/i,
/^(Status):\s+(.*?)\s*$/i: header[last = $1] = $2
when /^(Message-Id):\s+(.*?)\s*$/i: header[mid_field = last = $1] = $2
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-01-23 22:12 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 [this message]
2008-01-23 22:47 ` Gabriel Sean Farrell
2008-01-25 4:03 ` William Morgan
2008-01-25 7:50 ` Gabriel Sean Farrell
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=1201125726-sup-1297@south \
--to=wmorgan-sup@masanjin.net \
/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