From: Phil Jackson <phil@shellarchive.co.uk>
To: Sebastian P.Luque <spluque@gmail.com>
Cc: ding@gnus.org, bbdb-info@lists.sourceforge.net
Subject: Re: "undisclosed recipients"
Date: Fri, 23 Mar 2007 00:57:07 +0000 [thread overview]
Message-ID: <877it84w0s.fsf@shellarchive.co.uk> (raw)
In-Reply-To: <87ps70iykr.fsf@patagonia.sebmags.homelinux.org> (Sebastian P. Luque's message of "Thu\, 22 Mar 2007 19\:38\:12 -0500")
Sebastian P.Luque <spluque@gmail.com> writes:
> On Fri, 23 Mar 2007 00:16:55 +0000,
> Phil Jackson <phil@shellarchive.co.uk> wrote:
>
> [...]
>
>> Erm... the bcc field, unless I'm mis-understanding what you are asking?
>
> What I'd like is some way to enter the addresses (in this case from
> expanding a mail-alias field from bbdb) in the To: *or* *Bcc* fields,
> and tell gnus to not to disclose the addresses. I remember I could
> just check a box to do this way back when I was on M$ Windows. It may
> have simply moved the addresses to the Bcc: field in that case, so you
> may be right.
I'm afraid that's impossible with bog standard SMTP. Exchange (an MS
"email" server) will allow same site aliases which is maybe what you
used.
Cheers,
Phil
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
bbdb-info@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bbdb-info
BBDB Home Page: http://bbdb.sourceforge.net/
next prev parent reply other threads:[~2007-03-23 0:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 18:28 Sebastian P. Luque
2007-03-23 0:16 ` Phil Jackson
2007-03-23 0:38 ` Sebastian P.Luque
2007-03-23 0:57 ` Phil Jackson [this message]
2007-03-23 3:35 ` Charles philip Chan
2007-03-26 20:02 ` Leo
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=877it84w0s.fsf@shellarchive.co.uk \
--to=phil@shellarchive.co.uk \
--cc=bbdb-info@lists.sourceforge.net \
--cc=ding@gnus.org \
--cc=spluque@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).