[req] Honour 'CC', 'BCC' on email thru "click here to s

[rdigqd]

[req] Honour 'CC', 'BCC' on email sent using email
address generated by the "[i]click here to send[/i]
[i]a message from this address[/i]" facility

Sure would be nice if the situation mentioned was
operational ... or it is so and I just haven't figgered
out how to do it properly??
(I want to be able to receive back a copy for
my local record of msgs I send out.)

j.

----------------------------------

[josh]

The "send a message" feature only gives you an address to send to (a "redirection address") -- it's still up to you and your mail server to get the message out. Whatever methods for BCC'ing automatically that are available with your mail software should work for those redirection addresses.

[Guest]

Thanxc for the comeback, josh.

I would have assumed something along those lines,
however ... I sent a msg this a.m. addressed as follows:

Date: Tue, 12 Apr 2005 08:57:30 -0400
To: "MATTHIAS BRAND" <+<snip>@spamgourmet.com>
From: jes <my-email-id>
Subject: RE: Request for information on diesel engi ne conversion Umr?stung auf Pflanzen?l)
Bcc: <snip>@xoxy.net
.
.msg text ...
.

and I rec'd _nada_ back

So, I resent a series of the same sort of msgs
using a "generated" email addr (against that same
boker@xoxy.net SG identity) that comes to one of
_my_ 'real' addresses so as to avoid sending lotsa
repeat msgs to the non-me person named in
the "generated" addr shown above, along with the direct
SG addr <snip>
as follows:
1) as second item on the BCC line (one of my
real email ids was the 1st item)
2) as a CC item
3) as the second addr on the TO line

In all cases, NADA came back to me from SG
[i.e.: via the <snip> addr].

.Any further thoughts/suggestions

j.

[SysKoll]

Josh, I believe this is the bug where the same message to two sg destinations is delivered only once. Can you please confirm?

[josh]

I think we've got this problem (and many other related ones) resolved in our test environment. We've still got a bunch of testing to do, but we should be able to roll it out soon.

[josh]

OK, we went "beta" with the version that addresses this problem. You can try it if you like -- just use one of these domains for a disposable address:

beta.spamgourmet.net
beta.xoxy.net
beta.recursor.net
beta.antichef.net

and the new code will be invoked. Don't use them for anything permanent, as we'll probably retire these domains when we move the new code into "production"