ed a bit how
mutt_find_user_in_envelope [1] works. But as far as I see, there is no
easy way to make it also look into further headers, because the ENVELOPE
struct [2] does not provide those.
1: https://gitlab.com/muttmua/mutt/-/blob/master/alias.c#L692
2: https://gitlab.com/muttmua/mutt/-/blob/master/mutt.h#L739
A
On Tue, Sep 13, 2022 at 04:42:17PM +, Tim Chase wrote:
>
> While I wish I had a satisfactory answer, this is mostly to chime
> in that I too wish that reverse_name would consult the
> Envelope-To/Delivered-To. This includes this mutt list, where I
> have to manually change
From address when
> replying (setting realname).
>
> Would it be feasible to also let the alternates scan the mail headers
> and find the header 'To-Envelope'?
While I wish I had a satisfactory answer, this is mostly to chime
in that I too wish that reverse_name would consult t
On Mon, Sep 12, 2022 at 02:28:43PM +0200, Bastian wrote:
> On 12Sep22 14:24+0200, Bastian wrote:
> > Would it be feasible to also let the alternates scan the mail headers
> > and find the header 'To-Envelope'?
>
> Sorry, the header is labled Envelope-to:
I agree having
On 12Sep22 14:24+0200, Bastian wrote:
> Would it be feasible to also let the alternates scan the mail headers
> and find the header 'To-Envelope'?
Sorry, the header is labled Envelope-to:
--
Bastian
and find the header 'To-Envelope'? For me, this seems to always contain
the correct address to which the mail was delivered to me. Well, I do
not know where this header comes from; could be that my exim sets these
during delivery to maildir.
Cheers,
--
Bastian
On Mon, Sep 23, 2019, rand pie wrote:
> How to set the sendmail binary sender address
> base on different email addresses with mutt?
*-hook might work, e.g., something like:
folder-hook . "set sendmail=\"/usr/sbin/sendmail -i -oem -fUSER@B.C\""
send-hook ietf-smtp "set
Hello list.
How to set the sendmail binary sender address
base on different email addresses with mutt?
On 26Feb2016 15:17, Cameron Simpson wrote:
Failing that, you can fairly easily write scripts which emit mutt directives
based on header contents. I have a script "mhdrs" which can emit message
headers as shell settings, which you can then source in a shell script
file, which
On 25Feb2016 20:50, Tim Chase <m...@tim.thechases.com> wrote:
On 2016-02-25 21:34, Patrick Shanahan wrote:
> Is there some setting I've missed, or some way around this to have
> mutt extract my From: address using the Envelope-To: header?
send-hook 'my_hdr From: Your Addr <your
* Tim Chase <m...@tim.thechases.com> [02-25-16 21:59]:
> On 2016-02-25 21:34, Patrick Shanahan wrote:
> > > Is there some setting I've missed, or some way around this to have
> > > mutt extract my From: address using the Envelope-To: header?
> >
> > send-h
I'm in the To: field (and
> possibly the CC field), it correctly sets the From: based on the
> corresponding recipient in the message to which I'm replying.
>
> However, for certain mailing-lists, "my" address only appears in the
> Envelope-To: header of the message source. When I
e to which I'm replying.
However, for certain mailing-lists, "my" address only appears in the
Envelope-To: header of the message source. When I attempt to use the
above settings, it defaults to my usual From address, which suggests
it's not trying to compare the Envelope-To: headers again
Dear Nicolas,
Notice I don't set use_envelope_from.
*grummel* still doesn't work. I was just thinking: do have some official
dns-name on your mutt box? I'm behind a router in a private network and thought
that this might be the problem; somehow.
Thank you
Ben
In mutt I set my_hdr From: m...@email and in gmail I remove the envelope
rewriting (somewhere in the options).
thank you for your answer. Could you please be a bit more precise about the
'somewhere in the options'? I haven't found anything. It works with
thunderbird,
though
flow.
In mutt I set my_hdr From: m...@email and in gmail I remove the envelope
rewriting (somewhere in the options).
thank you for your answer. Could you please be a bit more precise about the
'somewhere in the options'? I haven't found anything. It works with
thunderbird,
though
remove the envelope
rewriting (somewhere in the options).
thank you for your answer. Could you please be a bit more precise about the
'somewhere in the options'? I haven't found anything. It works with thunderbird,
though.
@ Nathaniel
Yes, since set use_envelope_from=no is default, I have tried both
.
In mutt I set my_hdr From: m...@email and in gmail I remove the envelope
rewriting (somewhere in the options).
thank you for your answer. Could you please be a bit more precise about the
'somewhere in the options'? I haven't found anything. It works with
thunderbird,
though.
- settings
Dear Mutt-guru's,
I recently needed to create a gmail account 'username' and now I try to use
its smtp server as relay for my other mail addresses. The
'from: otheru...@yahoo.de' remains by using its webmail and thunderbird.
However,
it doesn't with mutt. If I send the mail with mutt the
flow.
In mutt I set my_hdr From: m...@email and in gmail I remove the envelope
rewriting (somewhere in the options).
--
Nicolas Sebrecht
I'm currently trying to set up a scoring policy for mail sent to
u...@example.com.
The problem is, I only get mass-mailings to this adress, with
u...@example.com usually residing in the BCC. But the header contains
envelope-to: u...@example.com, I just don't get how to access this
information.
I
On Wed, Mar 04, 2009 at 02:35:16PM +0100, ssiza...@gmail.com wrote:
I'm currently trying to set up a scoring policy for mail sent to
u...@example.com.
The problem is, I only get mass-mailings to this adress, with
u...@example.com usually residing in the BCC. But the header contains
envelope
...@example.com usually residing in the BCC. But the header contains
envelope-to: u...@example.com, I just don't get how to access this
information.
I tried ~L ~t ~C and whatnot.
~h '^Envelope-to: u...@example.com'
Adjustments may be necessary if your mailer adds something other than a bare
email
* ssiza...@gmail.com ssiza...@gmail.com [20090304 17:02]:
[snip]
~h '^Envelope-to: u...@example.com'
works when I'm limiting messages once inside the folder, but
score '~h '^Envelope-to: u...@example.com'' 41
in my .muttrc doesn't. Mutt complains about errors. I've tried
replacing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 05:01 PM, quoth ssiza...@gmail.com:
~h '^Envelope-to: u...@example.com'
works when I'm limiting messages once inside the folder, but
score '~h '^Envelope-to: u...@example.com'' 41
in my .muttrc doesn't.
Obviously
On Wed, Mar 4, 2009 at 17:18, Kyle Wheeler kyle-m...@memoryhole.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 05:01 PM, quoth ssiza...@gmail.com:
~h '^Envelope-to: u...@example.com'
works when I'm limiting messages once inside the folder, but
score '~h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 05:33 PM, quoth ssiza...@gmail.com:
Well it would make sense if any of your examples worked, but
unfortunately they don't.
I've tried mixing and ' myself, except for the
escaping-quotes-trick. That's new, but gives me
On Wed, Mar 4, 2009 at 18:18, Kyle Wheeler kyle-m...@memoryhole.net wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday, March 4 at 05:33 PM, quoth ssiza...@gmail.com:
Well it would make sense if any of your examples worked, but
unfortunately they don't.
I've tried mixing
Can mutt set the envelope to the user's choice *at the time of
message compose* to an address different from the message's
From: address?
How is it done? For starters, I'd probably want to:
unset envelope_from
and maybe comment-out this in my .muttrc:
my_hdr From: Mel [EMAIL
* Mel [EMAIL PROTECTED] [2002-08-03 08:28]:
Can mutt set the envelope to the user's choice
*at the time of message compose* to an address
different from the message's From: address?
you can only set or unset the envelope_from variable -
but not set what goes into the header. this is MTA
* Mel [EMAIL PROTECTED] [2002-08-03 04:28 -0400]:
Can mutt set the envelope to the user's choice *at the time of
message compose* to an address different from the message's
From: address?
Yes, of course!
How is it done? For starters, I'd probably want to:
unset envelope_from
then change
On Sat 08/03/02 at 11:50 AM +0200,
Sven Guckes [EMAIL PROTECTED] wrote:
* Mel [EMAIL PROTECTED] [2002-08-03 08:28]:
Can mutt set the envelope to the user's choice
*at the time of message compose* to an address
different from the message's From: address?
you can
of all the envelope is no header. It is createted by the MTA. No
MUA has controll over it. Second you can controll the envelope with
sendmails -f option which can easily be set in mutt.
HTH,
Michael
--
Running Windows on a Pentium is like having a brand new Porsche but only
be able to drive
* Melvin Q Watchpocket [EMAIL PROTECTED] [2002-08-03 08:20 -0400]:
On Sat 08/03/02 at 12:50 PM +0200,
Nicolas Rachinsky [EMAIL PROTECTED] wrote:
* Mel [EMAIL PROTECTED] [2002-08-03 04:28 -0400]:
Can mutt set the envelope to the user's choice *at
the time of message compose
mutt-users from themselves.
I mean, why not have the envelope be settable as
one of the headers visible with edit_headers set?
Is there *any* Mail User Agent that allows to do this
from within the MUA itself, without having to go into
Sendmail to do it (even if from the command-line
want to save mutt-users from themselves.
exactly! some mutt user should be using pine or outlook.
then they would not even *bother* about such problems.
I mean, why not have the envelope be settable as
one of the headers visible with edit_headers set?
users can and *will8 be confused, ask
Melvin Q Watchpocket ([EMAIL PROTECTED]) muttered:
I mean, why not have the envelope be settable as
one of the headers visible with edit_headers set?
Why should it? You are able to tweak the envelope by setting mutt's
$sendmail variable. What else do you want? This would be a feature
nobody
At 11:50 AM +0200 2002/08/03, Sven Guckes wrote:
you can only set or unset the envelope_from variable -
but not set what goes into the header. this is MTA stuff.
The MTA doesn't touch the headers (with the exception of adding
suitable Received: headers). So far as the MTA is
of adding
suitable Received: headers). So far as the MTA is concerned,
headers are part of the message body.
But if you use the MTA (sendmail in this case, and in many cases)
to create an envelope header that's gonna be different from a
message's From: header, (by doing 'sendmail -f
* Melvin Q Watchpocket [EMAIL PROTECTED] [2002-08-03 18:45 -0400]:
On Sat 08/03/02 at 09:30 PM +0200,
But if you use the MTA (sendmail in this case, and in many cases)
to create an envelope header that's gonna be different from a
message's From: header, (by doing 'sendmail -f
At 6:45 PM -0400 2002/08/03, Melvin Q Watchpocket wrote:
But if you use the MTA (sendmail in this case, and in many cases)
to create an envelope header that's gonna be different from a
message's From: header, (by doing 'sendmail -f'), then it (the
MTA) has to at least touch the envelope
On Sat, Aug 03, 2002 at 06:45:06PM -0400, Melvin Q Watchpocket wrote:
But if you use the MTA (sendmail in this case, and in many cases)
to create an envelope header that's gonna be different from a
message's From: header, (by doing 'sendmail -f'), then it (the
MTA) has to at least touch
how can I set the envelope-from independently from From: ?
~~/.muttrc:
folder-hook .*-List set sendmail=/usr/sbin/sendmail -oem -oi
-oem: unknown variable
which I can't make sense of. Can anyone enlighten me?
But the first folder-hooks work?
Why don't you set
On Sat, Apr 20, 2002 at 10:04:59AM +1200, Volker Kuhlmann wrote:
how can I set the envelope-from independently from From: ?
~~/.muttrc:
folder-hook .*-List set sendmail=/usr/sbin/sendmail -oem -oi
-oem: unknown variable
which I can't make sense of. Can anyone
how can I set the envelope-from independently from From: ? As is, mutt
AFAIK envelope_from does nothing but invokes sendmail with parameter
-f From:-Header
Correct
By setting sendmail directly you can call it with the -f paramater
set freely, i.e. to your real email adress
On 2002-04-19 Volker Kuhlmann wrote:
how can I set the envelope-from independently from From: ? As is, mutt
AFAIK envelope_from does nothing but invokes sendmail with parameter
-f From:-Header
Correct
By setting sendmail directly you can call it with the -f paramater
set freely
Hi all,
how can I set the envelope-from independently from From: ? As is, mutt
copies From: into envelope-from. I want to use a mangled From: as spam
protection, but list servers need to see a correct envelope-from
(unless it's lists like this, which seems to accept any 'ol stuff)?
Of course
On 2002-04-18 Volker Kuhlmann wrote:
Hi all,
how can I set the envelope-from independently from From: ? As is, mutt
copies From: into envelope-from. I want to use a mangled From: as spam
protection, but list servers need to see a correct envelope-from
(unless it's lists like this, which
Hi,
Some people mentioned that I should use the
envelope_from setting to help with mail delivery. It
worked.
What is the envelope_from setting and how is it
different from the From: field? Does anyone know where
I can learn how these function?
Thanks,
Todd
=
Todd Kokoszka
25, rue Richard
On Thu, Jan 10, 2002 at 11:01:29AM -0500, Todd Kokoszka wrote:
What is the envelope_from setting and how is it
different from the From: field? Does anyone know where
I can learn how these function?
It is documented in the manual (section 6.3.43 in the manual for Mutt 1.3.25).
--
Maciej
an envelope is or does and how that's
different from a From: field. The only thing I know is
that when I include envelope_from, more of mail gets
to where I want it to. I'm trying to figure out what
an envelope is and why it exists. Then I can figure
out what else I should know about mutt and mail
the entry for envelope_from, but that doesn't
tell me what an envelope is or does and how that's
different from a From: field. The only thing I know is
that when I include envelope_from, more of mail gets
to where I want it to. I'm trying to figure out what
an envelope is and why it exists. Then I can
* Todd Kokoszka [EMAIL PROTECTED] wrote:
I found the entry for envelope_from, but that doesn't
tell me what an envelope is or does and how that's
different from a From: field. The only thing I know is
that when I include envelope_from, more of mail gets
to where I want it to. I'm trying
There is a From: field in the email message and there is a from field
on the envelope wrapping the message. They are two different things.
When mutt passes off the message to your Mail Transport Agent, e.g.
Sendmail, Sendmail prepends certain information to it: specifically the
from field, date
Vincent Danen [EMAIL PROTECTED] wrote on Tue, 20 Jun 2000:
Someone mentioned an envelope header
string that can be defined but I think I lost that message...
Can someone re-post that info? I seem to have lost that message...
I guess you mean the message I posted yesterday. Here's a better
El día 02/May/2000, Claus Assmann escribía:
Uh, right now this is a SUSE box with sendmail. I fiddled with sendmail.cf
and filled in the correct masquerading stuff. Sendmail sucks. Big time.
Yeah, if you "fiddled with sendmail.cf"...
It requires two lines in your .mc file:
On Tue, May 02, 2000 at 11:28:26AM +0200, Ralf Hildebrandt wrote:
My problem: The envelope from is set to [EMAIL PROTECTED]
I already tried to
set hostname = "innominate.de"
but to no avail. How can I specify which envelope from mutt should use when
talking to my loca
On Wed, May 03, 2000 at 02:20:44AM +0200, cFischer wrote:
tweaked the "correct" config files. Anyway, right now I'm just too lazy to
throw away sendmail :)
that is, i tried smail. easy to configure and much leaner than sendmail.
IMHO you should forget sendmail and use qmail.
* Works *VERY
2000-05-03-10:50:35 cFischer:
On Wed 03.0500-08:18, Ralf Hildebrandt wrote:
You didn't try postfix.
no. did you? is it big 'n nasty?
Nope. Postfix is not big or nasty. It is, by design: simple to
install, configure, and maintain; fast; secure; and as compatible
with sendmail as needed to
On Tue, May 02, 2000 at 12:37:25PM +0200, Ralf Hildebrandt wrote:
my_hdr From: Lutz Jaenicke [EMAIL PROTECTED]
This is not the envelope from...
But it gets derived from that. Anyway, the reason why that didn't work was
because I set my_hdr From: from within a send-hook only...
Uh
On 2000-05-02 12:37:25 +0200, Ralf Hildebrandt wrote:
Uh, right now this is a SUSE box with sendmail. I
fiddled with sendmail.cf and filled in the correct
masquerading stuff. Sendmail sucks. Big time.
Hey, when fiddling with the sendmail.cf is an option,
switching to your favorite MTA may be
On 2000-05-02 11:28:26 +0200, Ralf Hildebrandt wrote:
set hostname = "innominate.de"
but to no avail. How can I specify which envelope from
mutt should use when talking to my local sendmail?
envelope_from
Type: boolean
Default: no
When set, mut
On Tue, May 02, 2000 at 11:28:26AM +0200, Ralf Hildebrandt wrote:
My problem: The envelope from is set to [EMAIL PROTECTED]
I already tried to
set hostname = "innominate.de"
but to no avail. How can I specify which envelope from mutt should use
when talking to my local sendmail
On Tue, May 02, 2000 at 11:28:26AM +0200, Ralf Hildebrandt wrote:
My problem: The envelope from is set to [EMAIL PROTECTED]
I already tried to
set hostname = "innominate.de"
but to no avail. How can I specify which envelope from mutt should use when
talking to my local sendm
My problem: The envelope from is set to [EMAIL PROTECTED]
I already tried to
set hostname = "innominate.de"
but to no avail. How can I specify which envelope from mutt should use when
talking to my local sendmail?
Transcript of session follows.
Out: 220 stahlw06.stahl.bau.tu-b
, at time T2
The copy of the message saved to file has the timestamp in the "From "
mailbox envelope header (not the "From:" RFC 822 header) set to T1 and
the "Date:" header set to T2. This can be a bit disconcerting if there
is a significant interval between T1 and T
On 1999-12-10 10:28:07 +0100, Thomas Roessler wrote:
It would be fairly easy to bloat up mutt_invoke_sendmail (in
sendlib.c) a bit - depending on a suitable option (say,
set_envelope_from), mutt could just pass "-faddress" to sendmail.
Note that at least sendmail and the sendmail emulation
On 1999-12-10 03:44:03 +0200, Mikko Hänninen wrote:
Sounds like something that could be done with a wrapper script,
invoked instead of the real sendmail command to first parse the
email, set the environment variable, and then call sendmail.
It would be fairly easy to bloat up
be something better.
Anyway, I'm not arguing for or against whether this should or shouldn't
added, I'm quite happy to have a single address as my envelope sender
for all my emails. :-)
Mikko
--
// Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/
// The Corrs list mainta
recall exim did understand -f, but since its extended address
support is broken somewhere else (or at the very least a RPITA to setup), I
changed to Postfix a while ago. I am not sure of the current state of exim.
Regardless, -f is the documented way to set the envelope sender for mutt's
method
I was trying to see if qmail's sendmail emulation script does, I think
so, but wasn't able to confirm it in documentation. (Yes, I know,
should be easy enough to test.)
Yes, not only does qmail's sendmail emulation work just fine, you can
actually set your sendmail variable to qmail-inject
Mike Bell [EMAIL PROTECTED] wrote on Thu, 09 Dec 1999:
Would it be possible to arrange for the contents of the from: header in sent
mail to be exported to the sendmail command, maybe as an environment
variable? I'd like to have my envelope-sender mirror the address I use in my
from: line
to have my envelope-sender mirror the address I use in my
from: line, since I send email from multiple accounts.
Sounds like something that could be done with a wrapper script, invoked
instead of the real sendmail command to first parse the email, set the
environment variable, and then call
73 matches
Mail list logo