SEO

What's the command line to send an email and use the blind copy function ?

If I want to send a file to 50 people but all of them be included in the
bcc.

cat message.txt | mail bla bla bla bla bla

Is there an argument for this purpose ? like mail -bcc bla bla ble bli blo
blu,,,etc..

Regards,

EA

corrlens wrote:
> What's the command line to send an email and use the blind copy
> function ?
>
> If I want to send a file to 50 people but all of them be included in
> the bcc.
>
> cat message.txt | mail bla bla bla bla bla
>
> Is there an argument for this purpose ? like mail -bcc bla bla ble
> bli blo blu,,,etc..
>
> Regards,
>
> EA

The answer is you need to either generate the email file yourself and
include a bcc: header and feed the file to sendmail, or you need to install
and use some other mua besides /bin/mail, like mutt or pine which are both
available from skunkware.

"man mutt" shows it has the option and it is "-b user@host.com" however it
does not show how to specify the plain old regular recipient or how to send
a basic mail non-interactively. However, "mutt brian@aljex.com
</etc/profile" did in fact work, so although the man page doesn't say it,
it appears to be as easy to use as plain /bin/mail, just with extra options.

--
Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani

Brian K. White typed (on Tue, Apr 13, 2004 at 03:57:11PM -0400):
| corrlens wrote:
| > What's the command line to send an email and use the blind copy
| > function ?
| >
| > If I want to send a file to 50 people but all of them be included in
| > the bcc.
| >
| > cat message.txt | mail bla bla bla bla bla
| >
| > Is there an argument for this purpose ? like mail -bcc bla bla ble
| > bli blo blu,,,etc..
| >
| > Regards,
| >
| > EA
|
| The answer is you need to either generate the email file yourself and
| include a bcc: header and feed the file to sendmail, or you need to install
| and use some other mua besides /bin/mail, like mutt or pine which are both
| available from skunkware.
|
| "man mutt" shows it has the option and it is "-b user@host.com" however it
| does not show how to specify the plain old regular recipient or how to send
| a basic mail non-interactively. However, "mutt brian@aljex.com
| </etc/profile" did in fact work, so although the man page doesn't say it,
| it appears to be as easy to use as plain /bin/mail, just with extra options.

Huh? It says so plain as day in the second usage line under SYNOPSIS:

mutt [-nx] [-e cmd] [-a file] [-F file] [-H file] [-i file]
[-s subj] [-b addr] [-c addr] addr [...]


--
JP

Jean-Pierre Radley wrote:
> Brian K. White typed (on Tue, Apr 13, 2004 at 03:57:11PM -0400):
>> corrlens wrote:
>>> What's the command line to send an email and use the blind copy
>>> function ?
>>>
>>> If I want to send a file to 50 people but all of them be included in
>>> the bcc.
>>>
>>> cat message.txt | mail bla bla bla bla bla
>>>
>>> Is there an argument for this purpose ? like mail -bcc bla bla ble
>>> bli blo blu,,,etc..
>>>
>>> Regards,
>>>
>>> EA
>>
>> The answer is you need to either generate the email file yourself and
>> include a bcc: header and feed the file to sendmail, or you need to
>> install and use some other mua besides /bin/mail, like mutt or pine
>> which are both available from skunkware.
>>
>> "man mutt" shows it has the option and it is "-b user@host.com"
>> however it does not show how to specify the plain old regular
>> recipient or how to send a basic mail non-interactively. However,
>> "mutt brian@aljex.com </etc/profile" did in fact work, so although
>> the man page doesn't say it, it appears to be as easy to use as
>> plain /bin/mail, just with extra options.
>
> Huh? It says so plain as day in the second usage line under SYNOPSIS:
>
> mutt [-nx] [-e cmd] [-a file] [-F file] [-H file] [-i file]
> [-s subj] [-b addr] [-c addr] addr [...]

Mine says:

SYNOPSIS
mutt [-hnpRvxyzZ] [-a file] [-b address] [-c address] [-e
command] [-f mailbox] [-F muttrc] [-H draftfile] [-i
include] [-m type] [-s subject]


however, "mutt --help" does show it:

Mutt 1.2.5.1i (2000-07-28)
usage: mutt [ -nRzZ ] [ -e <cmd> ] [ -F <file> ] [ -m <type> ] [ -f <file> ]
mutt [ -nx ] [ -e <cmd> ] [ -a <file> ] [ -F <file> ] [ -H <file> ]
[ -i <file> ] [ -s <subj> ] [ -b <addr> ] [ -c <addr> ] <addr> [ ... ]
mutt [ -n ] [ -e <cmd> ] [ -F <file> ] -p
mutt -v[v]


This copy came from the skunkware vol package.

--
Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO Prosper/FACTS AutoCAD #callahans Satriani

"Brian K. White" <brian@aljex.com> wrote in message
news:wf6dnQCPsOzryOHdRVn-hQ@comcast.com...
> Jean-Pierre Radley wrote:
> > Brian K. White typed (on Tue, Apr 13, 2004 at 03:57:11PM -0400):
> >> corrlens wrote:
> >>> What's the command line to send an email and use the blind copy
> >>> function ?
> >>>
> >>> If I want to send a file to 50 people but all of them be included in
> >>> the bcc.
> >>>
> >>> cat message.txt | mail bla bla bla bla bla
> >>>
> >>> Is there an argument for this purpose ? like mail -bcc bla bla ble
> >>> bli blo blu,,,etc..
> >>>
> >>> Regards,
> >>>
> >>> EA
> >>
> >> The answer is you need to either generate the email file yourself and
> >> include a bcc: header and feed the file to sendmail, or you need to
> >> install and use some other mua besides /bin/mail, like mutt or pine
> >> which are both available from skunkware.
> >>
> >> "man mutt" shows it has the option and it is "-b user@host.com"
> >> however it does not show how to specify the plain old regular
> >> recipient or how to send a basic mail non-interactively. However,
> >> "mutt brian@aljex.com </etc/profile" did in fact work, so although
> >> the man page doesn't say it, it appears to be as easy to use as
> >> plain /bin/mail, just with extra options.
> >
> > Huh? It says so plain as day in the second usage line under SYNOPSIS:
> >
> > mutt [-nx] [-e cmd] [-a file] [-F file] [-H file] [-i file]
> > [-s subj] [-b addr] [-c addr] addr [...]
>
> Mine says:
>
> SYNOPSIS
> mutt [-hnpRvxyzZ] [-a file] [-b address] [-c address] [-e
> command] [-f mailbox] [-F muttrc] [-H draftfile] [-i
> include] [-m type] [-s subject]
>
>
> however, "mutt --help" does show it:
>
> Mutt 1.2.5.1i (2000-07-28)
> usage: mutt [ -nRzZ ] [ -e <cmd> ] [ -F <file> ] [ -m <type> ] [ -f
<file> ]
> mutt [ -nx ] [ -e <cmd> ] [ -a <file> ] [ -F <file> ] [ -H <file> ]
> [ -i <file> ] [ -s <subj> ] [ -b <addr> ] [ -c <addr> ] <addr> [ ... ]
> mutt [ -n ] [ -e <cmd> ] [ -F <file> ] -p
> mutt -v[v]
>
>
> This copy came from the skunkware vol package.
>
> --
> Brian K. White -- brian@aljex.com -- http://www.aljex.com/bkw/


I tried mutt and when I read it under unix mail it's showing the bcc:
bla@bla.com . Outhouse express is not showing it.

Should I have to add a filter on my mail settings to strip off the bcc: line
?

Thanks

Brian K. White typed (on Tue, Apr 13, 2004 at 05:02:43PM -0400):
| Jean-Pierre Radley wrote:
| >> "man mutt" shows it has the option and it is "-b user@host.com"
| >> however it does not show how to specify the plain old regular
| >> recipient or how to send a basic mail non-interactively. However,
| >> "mutt brian@aljex.com </etc/profile" did in fact work, so although
| >> the man page doesn't say it, it appears to be as easy to use as
| >> plain /bin/mail, just with extra options.
| >
| > Huh? It says so plain as day in the second usage line under SYNOPSIS:
| >
| > mutt [-nx] [-e cmd] [-a file] [-F file] [-H file] [-i file]
| > [-s subj] [-b addr] [-c addr] addr [...]
|
| Mine says:
|
| SYNOPSIS
| mutt [-hnpRvxyzZ] [-a file] [-b address] [-c address] [-e
| command] [-f mailbox] [-F muttrc] [-H draftfile] [-i
| include] [-m type] [-s subject]
|
|
| however, "mutt --help" does show it:
|
| Mutt 1.2.5.1i (2000-07-28)
| usage: mutt [ -nRzZ ] [ -e <cmd> ] [ -F <file> ] [ -m <type> ] [ -f <file> ]
| mutt [ -nx ] [ -e <cmd> ] [ -a <file> ] [ -F <file> ] [ -H <file> ]
| [ -i <file> ] [ -s <subj> ] [ -b <addr> ] [ -c <addr> ] <addr> [ ... ]
| mutt [ -n ] [ -e <cmd> ] [ -F <file> ] -p
| mutt -v[v]
|
|
| This copy came from the skunkware vol package.

That's a real antique, and a bloated silly user of ncurses besides.
Compile current source, Brian...

Does that copy even use <F1> while in mutt to bring up help?

--
JP

corrlens typed (on Tue, Apr 13, 2004 at 09:23:56PM +0000):
|
| I tried mutt and when I read it under unix mail it's showing the bcc:
| bla@bla.com . Outhouse express is not showing it.

It's your MTA, not mutt.

I have used mutt as my MUA for years, but smail as my MTA and smail does
NOT transmit a Bcc: header nor its contents. I can't speak for sendmail
or mmdf or whichever other MTA you might be are using...

Does Outhouse Express show you ANY mail headers at all? Cc: or Reply-to:
Message-ID: or any other?

--
JP

In article <20040413214104.GA9653@jpradley.jpr.com>,
Jean-Pierre Radley <jpr@jpr.com> wrote:
>corrlens typed (on Tue, Apr 13, 2004 at 09:23:56PM +0000):
>|
>| I tried mutt and when I read it under unix mail it's showing the bcc:
>| bla@bla.com . Outhouse express is not showing it.
>
>It's your MTA, not mutt.
>
>I have used mutt as my MUA for years, but smail as my MTA and smail does
>NOT transmit a Bcc: header nor its contents. I can't speak for sendmail
>or mmdf or whichever other MTA you might be are using...

The only case in which an MTA might legitimately remove a Bcc: line is when a
message is being submitted in a mode where the recipients are taken from the
headers of the message itself. But this is an inferior mode; the normal method
is for the MUA to specify the recipient list out of band (separately from the
content of the message). In this case, the MTA shouldn't remove any headers,
although enough do that you shouldn't expect a Bcc: line to propagate
successfully if for some reason you *did* want it to appear.

With the normal (out of band) submission method, it is the job of the MUA to
not disclose the blind-copied recipients in the message headers. My
recollection is that an earlier version of mutt did have a bug that caused it
to include a Bcc: line in this case. Current mutt does the right thing.

John
--
John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/

John DuBois wrote:

> In article <20040413214104.GA9653@jpradley.jpr.com>,
> Jean-Pierre Radley <jpr@jpr.com> wrote:
> >corrlens typed (on Tue, Apr 13, 2004 at 09:23:56PM +0000):
> >|
> >| I tried mutt and when I read it under unix mail it's showing the bcc:
> >| bla@bla.com . Outhouse express is not showing it.
> >
> >It's your MTA, not mutt.
> >
> >I have used mutt as my MUA for years, but smail as my MTA and smail does
> >NOT transmit a Bcc: header nor its contents. I can't speak for sendmail
> >or mmdf or whichever other MTA you might be are using...
>
> The only case in which an MTA might legitimately remove a Bcc: line is when a
> message is being submitted in a mode where the recipients are taken from the
> headers of the message itself. But this is an inferior mode; the normal method
> is for the MUA to specify the recipient list out of band (separately from the
> content of the message). In this case, the MTA shouldn't remove any headers,
> although enough do that you shouldn't expect a Bcc: line to propagate
> successfully if for some reason you *did* want it to appear.
>
> With the normal (out of band) submission method, it is the job of the MUA to
> not disclose the blind-copied recipients in the message headers. My
> recollection is that an earlier version of mutt did have a bug that caused it
> to include a Bcc: line in this case. Current mutt does the right thing.

It's not a matter of Mutt versions or bugs, just default configuration.
You probably fixed your .muttrc a few years ago and no longer remember.

To fix, put:

unset write_bcc

in your .muttrc. It controls whether a Bcc: line is written into the
headers being sent to the MTA. This needs to be set by individual users
(or at least sysadmins) to exactly correspond with the behavior of the
local MTA _and_ the injection method being used by Mutt. For instance,
if you're using MMDF and injecting via `submit` then you probably want
write_bcc turned off. If you're using sendmail with `/usr/lib/sendmail
-t` (get recipients out of headers in message body), you want it turned
on. Many MTAs can be used in different ways which correspond to the two
settings, so there's no easy recipe.

Except, of course, that Mutt _knows_ whether it's passing addresses
out-of-band, so this setting shouldn't really exist at all. Or at least
it should have a third value that means "do the right thing you idiot",
which should be the default...

>Bela<

In article <20040413211547.GS21316@jpradley.jpr.com>,
Jean-Pierre Radley <jpr@jpr.com> wrote:
>Brian K. White typed (on Tue, Apr 13, 2004 at 05:02:43PM -0400):
>| Jean-Pierre Radley wrote:
>| >> "man mutt" shows it has the option and it is "-b user@host.com"
>| >> however it does not show how to specify the plain old regular
>| >> recipient or how to send a basic mail non-interactively. However,
>| >> "mutt brian@aljex.com </etc/profile" did in fact work, so although
>| >> the man page doesn't say it, it appears to be as easy to use as
>| >> plain /bin/mail, just with extra options.
>| >
>| > Huh? It says so plain as day in the second usage line under SYNOPSIS:
>| >
>| > mutt [-nx] [-e cmd] [-a file] [-F file] [-H file] [-i file]
>| > [-s subj] [-b addr] [-c addr] addr [...]
>|
>| Mine says:
>|
>| SYNOPSIS
>| mutt [-hnpRvxyzZ] [-a file] [-b address] [-c address] [-e
>| command] [-f mailbox] [-F muttrc] [-H draftfile] [-i
>| include] [-m type] [-s subject]
>|
>|
>| however, "mutt --help" does show it:
>|
>| Mutt 1.2.5.1i (2000-07-28)
>| usage: mutt [ -nRzZ ] [ -e <cmd> ] [ -F <file> ] [ -m <type> ] [ -f <file> ]
>| mutt [ -nx ] [ -e <cmd> ] [ -a <file> ] [ -F <file> ] [ -H <file> ]
>| [ -i <file> ] [ -s <subj> ] [ -b <addr> ] [ -c <addr> ] <addr> [ ... ]
>| mutt [ -n ] [ -e <cmd> ] [ -F <file> ] -p
>| mutt -v[v]
>|
>|
>| This copy came from the skunkware vol package.

>That's a real antique, and a bloated silly user of ncurses besides.
>Compile current source, Brian...

Hm. OYAP - On Yet Another Platform:

Mutt 1.5.6i (2004-02-01)

usage: mutt [ -nRyzZ ] [ -e <cmd> ] [ -F <file> ] [ -m <type> ] [ -f <file> ]
mutt [ -nR ] [ -e <cmd> ] [ -F <file> ] -Q <query> [ -Q <query> ] [...]
mutt [ -nR ] [ -e <cmd> ] [ -F <file> ] -A <alias> [ -A <alias> ] [...]
mutt [ -nx ] [ -e <cmd> ] [ -a <file> ] [ -F <file> ] [ -H <file> ] [ -i <file> ] [ -s <subj> ] [ -b <addr> ] [ -c <addr> ] <addr> [ ... ]
mutt [ -n ] [ -e <cmd> ] [ -F <file> ] -p
mutt -v[v]

[option descrpitions deleted]

Bill
--
Bill Vermillion - bv @ wjv . com