CC question

[Stephe Campbell]

Ok, I'll look at the RFC. Thanks.

I still don't understand, though what's going on. The mail log indicates the
original "From" as being from "<>". The bounced message comes back from one
of the CC recipients with the original "To" recipient in the "From" field,
and our mail log never references the CC "To" anywhere, as though we aren't
sending it at all.

To make all of that simpler, the maillog indicates:

Mar 20 15:52:16 kanawha sendmail[21040]: h2KKqGM21040: from=<>, size=5333,
class=0
, nrcpts=1, msgid=<CrSrkIwPZ00016a00 at fpa-exchange.fpanz.org.nz>, proto=SMTP,
daemo
n=Daemon0, relay=mailgw.cnpapers.net [208.247.228.18]

Mar 20 15:52:16 kanawha sendmail[21040]: h2KKqGM21040:
to=<xxxxxxxx at yyyyyyy.com
>, delay=00:00:00, mailer=virtual, pri=35333, stat=queued

The bounced message has xxxxxxxx at yyyyyyy.com as the returned-path and one of
the CC recipients as the "to".

Does that sound like what may be going on? Is there anything common to set
up in MS, SA, or sendmail to stop this.

Sorry to be such a bother.

Steve Campbell
campbell at cnpapers.com


----- Original Message -----
From: "Julian Field" <mailscanner at ECS.SOTON.AC.UK>
To: <MAILSCANNER at JISCMAIL.AC.UK>
Sent: Thursday, March 20, 2003 3:54 PM
Subject: Re: CC question


> At 20:37 20/03/2003, you wrote:
> >How do I determine the envelop of the email. If I look at the message
> >source, with all the headers and everything, what part of that is the
> >envelop?
>
> It's not in the message. The sender and recipients will be in your mail
log.
>
> >Anyway, if I can delete the original message using MS & SA, does that
> >prevent the CC recipients from being sent also? Where in the process of
all
> >of this does the CC recipients get their email from.
>
> In the normal course of events, the recipients are the "To:" addresses +
> the "Cc:" addresses + the "Bcc:" addresses. The "To:" and "Cc:" addresses
> are put in the corresponding headers. Sounds like they are putting an
> address listed in the recipients in the sender address.
>
> Read the RFC on SMTP and RFC822 for more information.
>
> >  Somehow, with what
> >appears to be no "From" in the original message, the return-path is being
> >set to the original recipient, which makes all of the CC bounces come
back
> >here, as though they were sent from the original recipient..
> >
> >Steve Campbell
> >campbell at cnpapers.com
> >
> >
> >----- Original Message -----
> >From: "Julian Field" <mailscanner at ECS.SOTON.AC.UK>
> >To: <MAILSCANNER at JISCMAIL.AC.UK>
> >Sent: Thursday, March 20, 2003 2:54 PM
> >Subject: Re: CC question
> >
> >
> > > At 19:36 20/03/2003, you wrote:
> > > >To any that may know
> > > >
> > > >Man, am I getting hit hard by someone with an email that includes CC
> > > >(carbon copy). I'm not sure how they are doing this, but the original
> > > >header usually has a blank from field, and is being sent to an
expired
> > > >address (no longer valid).
> > > >
> > > >I can block the primary non-CC mail recipient with MS and SA ( I
think ),
> > > >but what happens to the email going to the CC recipients? If I delete
the
> > > >email based on a blacklisted "To" non CC address, will this also kill
the
> > > >CC email also? The returned mail messages are around 500 a day and a
> > > >bother to others, I'm sure!
> > >
> > > MailScanner works solely on the message's real recipients (in the
> > > envelope), regardless of what may happen to be in the headers. The
headers
> > > are not used to determine the delivery addresses, they are purely for
user
> > > consumption. The "To:" and "Cc:" headers are irrelevant to
MailScanner, as
> > > they are to the delivery process.
> > >
> > > If you want to block them, you need to see the real recipient
addresses in
> > > your mail log.
> > > --
> > > Julian Field
> > > www.MailScanner.info
> > > Professional Support Services at www.MailScanner.biz
> > > MailScanner thanks transtec Computers for their support
>
> --
> Julian Field
> www.MailScanner.info
> Professional Support Services at www.MailScanner.biz
> MailScanner thanks transtec Computers for their support