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 PROT
* 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 M
* Ken Weingold <[EMAIL PROTECTED]> [2002-08-03 03:32]:
> Mozilla mail opens it fine. Apple Mail
> (formerly NeXTSTEP Mail I believe) opens it fine.
so?
> My guess is that it's encoded, but I'm not sure how.
> Is there Base64-encoded text?
you are asking *us*? hey - *you* got that message!
loo
* Gregory Seidman <[EMAIL PROTECTED]> [2002-08-03 02:32]:
> It's great if you want to forward an entire message (which,
> occasionally, I do), but it doesn't serve the more common case of
> wanting to forward everything in the message as parts of your
> message and adding a comment to the forwarde
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Champion <[EMAIL PROTECTED]> wrote:
> Jussi Ekholm" <[EMAIL PROTECTED]> wrote:
>> [I Cc'd this message to mutt-users, too - I think this belongs there
>> instead of mutt-dev]
>
> Maybe, but it's also a request for someone to further develop the
Sven --
...and then Sven Guckes said...
%
% * Gregory Seidman <[EMAIL PROTECTED]> [2002-08-03 02:32]:
...
% > wanting to forward everything in the message as parts of your
% > message and adding a comment to the forwarded message body.
%
% you want to bounce a message - but comment also?
Um, n
* 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
I have just joined the mailing list having installed Mutt with Fetchmail and Procmail
and I'm getting about 95% of the functionality I want having played with the
configuration for a few days.
I'm not sure if this problem I have is more MTA stuff but hopefully somebody can point
me in the righ
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?
>
Melvin Q Watchpocket ([EMAIL PROTECTED]) muttered:
> Then we can't *really* say that mutt gives
> us "total control over headers", can we?
> Is there *any* Mail User Agent that can do this from
> within the MUA itself, without having to invoke
> Sendmail to do it (if even from the command-line)?
Peter Andrijeczko ([EMAIL PROTECTED]) muttered:
> I have just joined the mailing list
Welcome. :)
> My home Linux network is on a non-Internet valid domain
> "penguins.home" and the hostname of the machine with Mutt is "gentoo".
> Although I (obviously) populate the "From:" address with my prope
* 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
* Vincent Lefevre writes:
> There are systems with multiple binaries.
* Chris Palmer <[EMAIL PROTECTED]> [2002-08-02 17:17]:
> It's up to the sysadmin to keep the man pages in the
> same directory prefix as the binaries. /usr/foo/man/man1
> should correspond to /usr/foo/bin, et c.
*sigh* Chris
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David T-G <[EMAIL PROTECTED]> wrote:
> ...and then Jussi Ekholm said...
>> Morning.
>
> Hiya!
Hello, David! :-)
> 1) mutt 1.4 and earlier required a patch (Aaron(?) wrote an early
> one and then Dale wrote the one that replaced it) to tweak
> $pgp_
On Sat 08/03/02 at 03:02 PM +0200,
Sven Guckes <[EMAIL PROTECTED]> wrote:
[that I wrote:]
> > Then we can't really say that mutt gives us
> > "total control over headers", can we?
>
> no. there are some which should not be touched.
> and that's good.
In mutt? But why? This sounds like you wa
* Melvin Q Watchpocket <[EMAIL PROTECTED]> [2002-08-03 15:33]:
> Sven Guckes <[EMAIL PROTECTED]> wrote:
> > > Then we can't really say that mutt gives us
> > > "total control over headers", can we?
> > no. there are some which should not be touched.
> > and that's good.
> In mutt? But why? This
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 e
* David Champion [[EMAIL PROTECTED]] [2002-08-02 11:18 -0500]:
> * "Calum Selkirk" <[EMAIL PROTECTED]> wrote:
>
> > > > if mutt could be ./configure'd --with-pcre (nondefault, of
> > > > course), there'd be virtually no problems with confusion between
> > > > regexps found in various published .m
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 c
Hello Jussi,
On Saturday, August 3, 2002 at 4:43:48 PM +0300, Jussi Ekholm wrote:
> Content-Type: text/plain; charset=utf-8; x-action=pgp-signed
>
> I send an email, which is traditionally signed, from Mutt 1.5.1i to a
> person who uses Mutt 1.4i. In this one particular case, scandinavian
> cha
On Sat 08/03/02 at 09:30 PM +0200,
Brad Knowles <[EMAIL PROTECTED]> wrote:
> 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 exc
* Peter Andrijeczko <[EMAIL PROTECTED]> [08-03-02 17:25]:
> I have just joined the mailing list having installed Mutt with
> Fetchmail and Procmail and I'm getting about 95% of the functionality
> I want having played with the configuration for a few days.
>
> I'm not sure if this problem I have
* 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'), then i
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 enve
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
On 09:14 02 Aug 2002, Chris Palmer <[EMAIL PROTECTED]> wrote:
| Vincent Lefevre writes:
| > > The installed manual should be preprocessed during the build to have
| > > the correct defaults.
| > But how can it have the correct defaults since there is only one
| > manual for several binaries?
Only
On 15:38 03 Aug 2002, Sven Guckes <[EMAIL PROTECTED]> wrote:
| * Vincent Lefevre writes:
| > There are systems with multiple binaries.
|
| * Chris Palmer <[EMAIL PROTECTED]> [2002-08-02 17:17]:
| > It's up to the sysadmin to keep the man pages in the
| > same directory prefix as the binaries. /us
Problem: I handed out loads of addresses of the form
[EMAIL PROTECTED] I'd like to automatically save
emails to this address to =SENDERSPECIFIC, where "automatically" means
that I don't want to put a save-hook line into my muttrc file.
I thought about using message-hook to somehow call save-hoo
* Chris Stork <[EMAIL PROTECTED]> [2002-08-04 01:46]:
> Problem: I handed out loads of addresses of the form
> [EMAIL PROTECTED] I'd like to automatically save
> emails to this address to =SENDERSPECIFIC, where "automatically" means
> that I don't want to put a save-hook line into my muttrc file
* Cameron Simpson <[EMAIL PROTECTED]> [2002-08-04 01:02]:
> On my systems I frequently have several mutts installed.
> Each has its own manual page because each has its own install tree.
> The /usr/local/bin/mutt is a symlink to the appropriate mutt
> binary in its respective tree, and so is the m
* Cameron Simpson <[EMAIL PROTECTED]> [2002-08-04 01:16]:
> Users wanting a specific mutt generally hack their PATH
> and MANPATH to put that mutt's bin/man dirs at the front.
and how do you maintain a huge system for users
who are not capable of adjusting the shell path?
do you take the time to
On Sun, Aug 04, 2002 at 04:11:49AM +0200, Sven Guckes wrote:
> * Chris Stork <[EMAIL PROTECTED]> [2002-08-04 01:46]:
> > Problem: I handed out loads of addresses of the form
> > [EMAIL PROTECTED] I'd like to automatically save
> > emails to this address to =SENDERSPECIFIC, where "automatically"
On 04:22 04 Aug 2002, Sven Guckes <[EMAIL PROTECTED]> wrote:
| let's see - i need a different shell setup for each
| of my mutt binaries,
No, JUST ONE that peers at $0. If you're doing the shell wrapper thing.
Just make links.
| and for each of the systems.
| now, if i follow this for every prog
On 04:28 04 Aug 2002, Sven Guckes <[EMAIL PROTECTED]> wrote:
| * Cameron Simpson <[EMAIL PROTECTED]> [2002-08-04 01:16]:
| > Users wanting a specific mutt generally hack their PATH
| > and MANPATH to put that mutt's bin/man dirs at the front.
|
| and how do you maintain a huge system for users
|
--ReaqsoxgOBHFXBhH
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Chris Stork spake thus:
> (I use procmail already to filter my mail. But the emails I'm talking
> about arrive rarely and I could miss them if they were pr
35 matches
Mail list logo
