Re: sending an email with a mutt one-line without being prompted

[Will Fiveash]

On Mon, Aug 02, 2010 at 04:26:47PM -0500, Nicolas Williams wrote:
> On Mon, Aug 02, 2010 at 04:13:16PM -0500, Will Fiveash wrote:
> > On Mon, Aug 02, 2010 at 03:49:47PM -0500, Nicolas Williams wrote:
> > > On Sun, Aug 01, 2010 at 10:52:01PM -0500, David Champion wrote:
> > > > Syntax has been changed: -a indicates a *list* of attachment files
> > > > ending with "--". I don't recall which version was first to boast this
> > > > new syntax, but it's the problem you're seeing right now even if it's
> > > > not related to the problem you saw earlier.
> > > > 
> > > > Try:
> > > > 
> > > > mutt -s test -a Bild.jpg -- m...@some.org  > > 
> > > I recommend against this use of '--'.  It makes it harder to write
> > > wrapper scripts that parse the same arguments using getopt/ getopts, for
> > > example.  Sadly, I don't have a counter-proposal, nor am I suggesting
> > > this get ripped out now.
> > 
> > On the other hand it makes:
> > 
> > mutt -a * -- j...@foo.bar
> 
> Really?  You do that?  It's kinda like rm *...

I haven't yet but I could see if one was in a dir with images like
foo.jpg bar.jpg etc... it could be useful.  I'm not saying one should
use it without caution.

> > easier which I would guess is why the change was made.  You do have a
> > point about -- being potentially problematic.  Maybe -a should work like
> > it used to (only one file per -a instance) and a new flag could take a
> > list of files to attach from a file given as a arg (or stdin).
> 
> Right.  There's no good convention for "end of list of arguments to an
> option".  There's only a good convention for "end of variable argument
> list" ('--'), and since this is the closest thing...
> 
> If -a was last then you could:
> 
> % mutt -s some-subject -t some-to:-addres ... -a * < body.txt
> 
> Oddly enough there's no -t argument.  The To: address(es) has(have) to
> be last.  You can't have two argument lists terminated by dint of being
> last.

Yeah, I hate positional CLI args.  I'd prefer:

% ls *.jpg > /tmp/files
% mutt -s some-subject -t to:-address1,to:address2 -q /tmp/files -c cc:-address 
< body.txt

-- 
Will Fiveash
Oracle
Austin, TX, USA
Internal Solaris Kerberos/GSS/SASL website: http://kerberos.sfbay.sun.com
http://opensolaris.org/os/project/kerberos/
Note my new work e-mail address: will.five...@oracle.com

Re: sending an email with a mutt one-line without being prompted

[Nicolas Williams]

On Mon, Aug 02, 2010 at 04:13:16PM -0500, Will Fiveash wrote:
> On Mon, Aug 02, 2010 at 03:49:47PM -0500, Nicolas Williams wrote:
> > On Sun, Aug 01, 2010 at 10:52:01PM -0500, David Champion wrote:
> > > Syntax has been changed: -a indicates a *list* of attachment files
> > > ending with "--". I don't recall which version was first to boast this
> > > new syntax, but it's the problem you're seeing right now even if it's
> > > not related to the problem you saw earlier.
> > > 
> > > Try:
> > > 
> > > mutt -s test -a Bild.jpg -- m...@some.org  > 
> > I recommend against this use of '--'.  It makes it harder to write
> > wrapper scripts that parse the same arguments using getopt/ getopts, for
> > example.  Sadly, I don't have a counter-proposal, nor am I suggesting
> > this get ripped out now.
> 
> On the other hand it makes:
> 
> mutt -a * -- j...@foo.bar

Really?  You do that?  It's kinda like rm *...

> easier which I would guess is why the change was made.  You do have a
> point about -- being potentially problematic.  Maybe -a should work like
> it used to (only one file per -a instance) and a new flag could take a
> list of files to attach from a file given as a arg (or stdin).

Right.  There's no good convention for "end of list of arguments to an
option".  There's only a good convention for "end of variable argument
list" ('--'), and since this is the closest thing...

If -a was last then you could:

% mutt -s some-subject -t some-to:-addres ... -a * < body.txt

Oddly enough there's no -t argument.  The To: address(es) has(have) to
be last.  You can't have two argument lists terminated by dint of being
last.

Nico
-- 

Re: sending an email with a mutt one-line without being prompted

[David Champion]

* On 02 Aug 2010, Nicolas Williams wrote: 
> On Sun, Aug 01, 2010 at 10:52:01PM -0500, David Champion wrote:
> > Syntax has been changed: -a indicates a *list* of attachment files
> > ending with "--". I don't recall which version was first to boast this
> > new syntax, but it's the problem you're seeing right now even if it's
> > not related to the problem you saw earlier.
> > 
> > Try:
> > 
> > mutt -s test -a Bild.jpg -- m...@some.org  
> I recommend against this use of '--'.  It makes it harder to write
> wrapper scripts that parse the same arguments using getopt/ getopts, for
> example.  Sadly, I don't have a counter-proposal, nor am I suggesting
> this get ripped out now.

I'm not fond of it either, but there was fairly extensive
discussion when it was committed in April 2007.  See mutt-users
<20070320122350.ga25...@giotto.argoss.nl> and mutt-dev
<20070321193650.gb2...@df7cb.de> for thread heads.

I think your specific concern may be exempted by the implementation
used.

-- 
 -D.d...@uchicago.eduIT ServicesUniversity of Chicago

Re: sending an email with a mutt one-line without being prompted

[Will Fiveash]

On Mon, Aug 02, 2010 at 03:49:47PM -0500, Nicolas Williams wrote:
> On Sun, Aug 01, 2010 at 10:52:01PM -0500, David Champion wrote:
> > Syntax has been changed: -a indicates a *list* of attachment files
> > ending with "--". I don't recall which version was first to boast this
> > new syntax, but it's the problem you're seeing right now even if it's
> > not related to the problem you saw earlier.
> > 
> > Try:
> > 
> > mutt -s test -a Bild.jpg -- m...@some.org  
> I recommend against this use of '--'.  It makes it harder to write
> wrapper scripts that parse the same arguments using getopt/ getopts, for
> example.  Sadly, I don't have a counter-proposal, nor am I suggesting
> this get ripped out now.

On the other hand it makes:

mutt -a * -- j...@foo.bar

easier which I would guess is why the change was made.  You do have a
point about -- being potentially problematic.  Maybe -a should work like
it used to (only one file per -a instance) and a new flag could take a
list of files to attach from a file given as a arg (or stdin).

-- 
Will Fiveash

Re: what does this "sender invalid" error mean?

[Michael Elkins]

On Mon, Aug 02, 2010 at 09:38:01PM +0100, Chris G wrote:

I'm trying to b[ounce] a message and I'm getting the following error
on the mutt status line:-

SMTP session failed: 550 Sender  invalid

So what is it saying?  Obviously "Chris@" id invalid but how is mutt
creating it and what is missing such that mutt can't create a valid
address?


It looks like Mutt is not able to automatically determine the FQDN for your 
host by inspecting /etc/resolv.conf.  The easiest solution is to manually set 
your $from or $hostname:


set from=u...@example.com
set hostname=example.com

me


pgpJ1ev22GyNC.pgp
Description: PGP signature

Re: sending an email with a mutt one-line without being prompted

[Nicolas Williams]

On Sun, Aug 01, 2010 at 10:52:01PM -0500, David Champion wrote:
> Syntax has been changed: -a indicates a *list* of attachment files
> ending with "--". I don't recall which version was first to boast this
> new syntax, but it's the problem you're seeing right now even if it's
> not related to the problem you saw earlier.
> 
> Try:
> 
> mutt -s test -a Bild.jpg -- m...@some.org 

what does this "sender invalid" error mean?

[Chris G]

I'm trying to b[ounce] a message and I'm getting the following error
on the mutt status line:-

 SMTP session failed: 550 Sender  invalid

So what is it saying?  Obviously "Chris@" id invalid but how is mutt
creating it and what is missing such that mutt can't create a valid
address? 

-- 
Chris Green

Re: sending an email with a mutt one-line without being prompted

[Will Fiveash]

On Mon, Aug 02, 2010 at 01:34:18PM -0700, Michael Elkins wrote:
> 
> At the end of the help output there is this:
> 
>   --  separate filename(s) and recipients,
>   when using -a, -- is mandatory
> 
> I agree it would make more sense to put that nearer to the text for
> the -a option.  Something like:
> 
>   -a  [...] --  attach file(s) to the message
>   the list of files must be terminated with the "--" sequence

+1
-- 
Will Fiveash
Oracle

Re: sending an email with a mutt one-line without being prompted

[Michael Elkins]

On Mon, Aug 02, 2010 at 12:12:27PM -0500, Will Fiveash wrote:

Yep, I struggled with this change recently.  It would be nice if mutt's
help output for -a was updated with this important usage tidbit.  Here's
what it looks like now:

Mutt 1.5.20 (2010-04-22)
usage: mutt [] [-z] [-f  | -yZ]
  mutt [] [-x] [-Hi ] [-s ] [-bc ] [-a  [...] 
--]  [...]
  mutt [] [-x] [-s ] [-bc ] [-a  [...] --]  
[...] < message
  mutt [] -p
  mutt [] -A  [...]
  mutt [] -Q  [...]
  mutt [] -D
  mutt -v[v]

options:
 -A expand the given alias
 -a  attach a file to the message
^^
This should be:
 -a  attach one or more files to the message, must be terminated with " 
--"

BTW, I do notice now that the terse usage does indicate -- termination
but I didn't look at that closely initially.


At the end of the help output there is this:

  --separate filename(s) and recipients,
when using -a, -- is mandatory

I agree it would make more sense to put that nearer to the text for the -a 
option.  Something like:


  -a  [...] --  attach file(s) to the message
the list of files must be terminated with the "--" sequence

me


pgpxw4bZlyAU4.pgp
Description: PGP signature

Re: sending an email with a mutt one-line without being prompted

[Will Fiveash]

On Sun, Aug 01, 2010 at 10:52:01PM -0500, David Champion wrote:
> * On 01 Aug 2010, Christoph Kukulies wrote: 
> > >>
> > >>k...@post:~$ mutt  -s test k...@validaddress.de > >>Error sending message, child exited 1 ().
> > >>Segmentation fault
> > >>
> > >>
> > >>
> > >This should work. Maybe you could try to upgrade mutt to the most recent
> > >version 1.5.20?
> > >
> > I tried it on another machine (ubuntu) and there it says
> > 
> > k...@accms33:~$ mutt -s test -a Bild.jpg m...@some.org  > Keine Empf?nger angegeben.
> 
> Syntax has been changed: -a indicates a *list* of attachment files
> ending with "--". I don't recall which version was first to boast this
> new syntax, but it's the problem you're seeing right now even if it's
> not related to the problem you saw earlier.
> 
> Try:
> 
> mutt -s test -a Bild.jpg -- m...@some.org ] [-z] [-f  | -yZ]
   mutt [] [-x] [-Hi ] [-s ] [-bc ] [-a  
[...] --]  [...]
   mutt [] [-x] [-s ] [-bc ] [-a  [...] --] 
 [...] < message
   mutt [] -p
   mutt [] -A  [...]
   mutt [] -Q  [...]
   mutt [] -D
   mutt -v[v]

options:
  -A expand the given alias
  -a  attach a file to the message
 ^^
This should be:
  -a  attach one or more files to the message, must be terminated 
with " --"

BTW, I do notice now that the terse usage does indicate -- termination
but I didn't look at that closely initially.
-- 
Will Fiveash

Re: sending an email with a mutt one-line without being prompted

[Christoph Kukulies]

Am 02.08.2010 10:58, schrieb Simon Ruderich:

On Sun, Aug 01, 2010 at 07:31:28PM +0200, Christoph Kukulies wrote:
   

[snip]

I opened a can of worms obviously. On the target system (debian) the
stock  mutt-1.5.20.tgz doesn't compile because
it can't find libcurses. I have libncurses5 installed. Maybe patches
are required for debian?
 

On Debian the files necessary to compile a program are provided
in a separate package, called libncurses5-dev. You will need
those *-dev packages for all libraries mutt depends on.

But before doing this, try mutt 1.5.20 from backports.org.
   


Thanks. I lifted my system this morning from debian 4 to debian 5 and 
the stock 1.3.18 (or sth.)

mutt didn't show the segfault.

I then installed 1.5.20 from a backport site and it was working fine.


   

A newer package for debian (unless I compile from sources) doesn't
seem to exist.

Any debian experts here?  I'm getting error 404 when trying to
install further packages (e.g. strace) . Maybe I got to extend
/etc/apt/sources.list?
 

The only thing you need in there should be something like this
(if you use Debian Lenny):

 deb http://ftp.de.debian.org/debian/ lenny main
   


As mentioned above, I was still having edge and moved to lenny this morning.

   


--
Christoph

Re: sending email to txt

[Tim Gray]

On Aug 02, 2010 at 08:27 AM -0400, Tim Gray wrote:

On Aug 01, 2010 at 10:26 PM -0800, rog...@sdf.org wrote:

Nope.  Doesn't work here.


I don't know.  It worked the other day for me.  Here's the complete list 
from wiki:




To follow up on this, I sent two emails this morning to my phone, one to 
each of the addresses.  The mms message came through about 5 mins after I 
sent it.  The txt address message came through about an hour and 15 mins 
after I sent it.  But both did come through.

Re: sending email to txt

[Tim Gray]

On Aug 01, 2010 at 10:26 PM -0800, rog...@sdf.org wrote:

Nope.  Doesn't work here.


I don't know.  It worked the other day for me.  Here's the complete list 
from wiki:

Re: sending an email with a mutt one-line without being prompted

[Simon Ruderich]

On Sun, Aug 01, 2010 at 07:31:28PM +0200, Christoph Kukulies wrote:
> [snip]
>
> I opened a can of worms obviously. On the target system (debian) the
> stock  mutt-1.5.20.tgz doesn't compile because
> it can't find libcurses. I have libncurses5 installed. Maybe patches
> are required for debian?

On Debian the files necessary to compile a program are provided
in a separate package, called libncurses5-dev. You will need
those *-dev packages for all libraries mutt depends on.

But before doing this, try mutt 1.5.20 from backports.org.

> A newer package for debian (unless I compile from sources) doesn't
> seem to exist.
>
> Any debian experts here?  I'm getting error 404 when trying to
> install further packages (e.g. strace) . Maybe I got to extend
> /etc/apt/sources.list?

The only thing you need in there should be something like this
(if you use Debian Lenny):

deb http://ftp.de.debian.org/debian/ lenny main

> Christoph

Hope this helps,
Simon
-- 
+ privacy is necessary
+ using gnupg http://gnupg.org
+ public key id: 0x92FEFDB7E44C32F9


pgppmdctTW30h.pgp
Description: PGP signature