(sorry, I wasn't finished yet.)
You should also forward that attached e-mail to:
http://home.rica.net/alphae/419coal/
- mark
> --
> From: Andre Bonhote[SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 12, 2002 1:10 AM
> To: [EMAIL PROTECTED]
> Subject: [SAtalk] N
Also, you should submit that e-mail to:
> --
> From: Andre Bonhote[SMTP:[EMAIL PROTECTED]]
> Sent: Friday, July 12, 2002 1:10 AM
> To: [EMAIL PROTECTED]
> Subject: [SAtalk] Not caught: Luis Boma $30M
>
> <>
> Hi SA-folks!
>
> This just dropped in this morning and
I'm just forwarding this note from the dcc-mailing list because it has
relevance to the SpamAssassin list.
- Mark Rice
> --
...
> According to reports from other people, the SpamAssassin documentation
> does mention using `cdcc info` to see if the DCC client is working,
> but doesn't say
SA users that implement DCC need this info...
[Forwarded from the DCC mailing list.]
- Mark Rice
> --
> From: [EMAIL PROTECTED]:[EMAIL PROTECTED]
> Reply To: [EMAIL PROTECTED]
> Sent: Thursday, October 09, 2003 1:01 PM
> To: [EMAIL PROTECTED]
> Subject: DCC dige
[EMAIL PROTECTED]
> Subject: [SAtalk] Re: documenting DCC
>
> On Thursday 09 October 2003 20:29 CET Rice, MA Mark (6750) @ IS wrote:
> > I'm just forwarding this note from the dcc-mailing list because it has
> > relevance to the SpamAssassin list.
>
> Could
Yes, Larry, it's a firewall configuration issue. If you receive responses
from a few public DCC servers, your firewall is likely allowing DCC to do
its job.
- Mark Rice
> --
> From: Larry Gilson[SMTP:[EMAIL PROTECTED]
>
> > > According to reports from other people, the SpamAssas
