Failed reports

I noticed this evening the below when running my spam reporter script
which reports to Razor, Pyzor, DCC and SpamCop,

[25180] warn: reporter: SpamCop report to vmx2.spamcop.net failed:
Net::SMTP error
[25180] warn: reporter: SpamCop report to vmx1.spamcop.net failed:
Net::SMTP error
[25180] info: reporter: could not report spam to SpamCop

There were 57 spam to be reported, 10 were as I received replies back
from the autoresponder, however 47 weren't. Not sure where the problem
may lie, my box, my ISP (Embarq), my Net::SMTP setup (though I doubt
that since 10 reports made it) or with SpamCop. I'm up for any
suggestions. I can run them all through the script again to see if
anything has changed.

Chris

Chris wrote:
> I noticed this evening the below when running my spam reporter script
> which reports to Razor, Pyzor, DCC and SpamCop,
>
> [25180] warn: reporter: SpamCop report to vmx2.spamcop.net failed:
> Net::SMTP error
> [25180] warn: reporter: SpamCop report to vmx1.spamcop.net failed:
> Net::SMTP error
> [25180] info: reporter: could not report spam to SpamCop
>
> There were 57 spam to be reported, 10 were as I received replies back
> from the autoresponder, however 47 weren't. Not sure where the problem
> may lie, my box, my ISP (Embarq), my Net::SMTP setup (though I doubt
> that since 10 reports made it) or with SpamCop. I'm up for any
> suggestions. I can run them all through the script again to see if
> anything has changed.

The/Your submit address is domainname spam.spamcop.net which MXes are
vmx2.spamcop.net  and  vmx1.spamcop.net

There is no A address for spam.spamcop.net;  that should not cause a
problem.  The vmx hostnames resolve quickly to 204.15.82.27 & .29

If there was some kind of problem engaging/transacting with the vmx
MXes, the problem is not currently apparent&1.  It would be useful to
see some server logs if you want to see a smtp transaction problem.

Initiating server query ...
Looking up IP address for domain: vmx2.spamcop.net
The IP address for the domain is: 204.15.82.29
Connecting to the server on remote port: 25
[Connected]  The server greeted our connection with this message:
220 vmx2.spamcop.net ESMTP
Query complete.

Initiating server query ...
Looking up IP address for domain: vmx1.spamcop.net
The IP address for the domain is: 204.15.82.27
Connecting to the server on remote port: 25
[Connected]  The server greeted our connection with this message:
220 vmx1.spamcop.net ESMTP
Query complete.


-- 
Mike Easter
kibitzer, not SC admin

Mike Easter wrote:
> Chris wrote:
>> I noticed this evening the below when running my spam reporter script
>> which reports to Razor, Pyzor, DCC and SpamCop,
>>
>> [25180] warn: reporter: SpamCop report to vmx2.spamcop.net failed:
>> Net::SMTP error
>> [25180] warn: reporter: SpamCop report to vmx1.spamcop.net failed:
>> Net::SMTP error
>> [25180] info: reporter: could not report spam to SpamCop
>>
>> There were 57 spam to be reported, 10 were as I received replies back
>> from the autoresponder, however 47 weren't. Not sure where the problem
>> may lie, my box, my ISP (Embarq), my Net::SMTP setup (though I doubt
>> that since 10 reports made it) or with SpamCop. I'm up for any
>> suggestions. I can run them all through the script again to see if
>> anything has changed.
> 
> The/Your submit address is domainname spam.spamcop.net which MXes are
> vmx2.spamcop.net  and  vmx1.spamcop.net
> 
> There is no A address for spam.spamcop.net;  that should not cause a
> problem.  The vmx hostnames resolve quickly to 204.15.82.27 & .29
> 
> If there was some kind of problem engaging/transacting with the vmx
> MXes, the problem is not currently apparent&1.  It would be useful to
> see some server logs if you want to see a smtp transaction problem.
> 
> Initiating server query ...
> Looking up IP address for domain: vmx2.spamcop.net
> The IP address for the domain is: 204.15.82.29
> Connecting to the server on remote port: 25
> [Connected]  The server greeted our connection with this message:
> 220 vmx2.spamcop.net ESMTP
> Query complete.
> 
> Initiating server query ...
> Looking up IP address for domain: vmx1.spamcop.net
> The IP address for the domain is: 204.15.82.27
> Connecting to the server on remote port: 25
> [Connected]  The server greeted our connection with this message:
> 220 vmx1.spamcop.net ESMTP
> Query complete.
> 
> 
Mike, I've no log information other than what I've shown above, my
submit address to SC is submit.xxxxxxxxxxxxx@spam.spamcop.net, as I
said, ten of the reports made it, 47 didn't because of the Net::SMTP

"Chris" <cpollock@embarqmail.com> wrote in message 
news:fhq3ec$ni8$1@news.spamcop.net...
<snip>
> Mike, I've no log information other than what I've shown above, my
> submit address to SC is submit.xxxxxxxxxxxxx@spam.spamcop.net, as I
> said, ten of the reports made it, 47 didn't because of the Net::SMTP
> error. Guess I'll just have to wait and see what tonights run brings.

Since I am not technically fluent, I don't know whether a discussion in the 
forum about a failed SPF record applies.  Apparently, some servers were 
changed and some things left out.  There is a trouble ticket about it.

If it continues, then you might look at some recent topics in the forum 
where the same thing seems to be happening - some getting thru and others 
not - see if they apply to your situation.

Miss Betsy