From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] return-path
Date: Sun, 27 Jan 2008 20:03:54 +0000 [thread overview]
Message-ID: <1201464123-sup-2970@tomsk> (raw)
In-Reply-To: <1201246425-sup-9409@magnum>
On 25.1.2008, Gabriel Sean Farrell wrote:
> 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?
Even better if this string could written with the to send email as a
variable so you could write something like
"sendmail -f #{m.from}"
... or somehting like that.
Marcus
prev parent reply other threads:[~2008-01-27 20:03 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
2008-01-27 20:03 ` Marcus Williams [this message]
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=1201464123-sup-2970@tomsk \
--to=marcus-sup@bar-coded.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