Spam Filter ISP Support - SpamfilterISP bounces with message Remote host said: neutral

SpamfilterISP bounces with message Remote host said: neutral

Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=4282
Printed Date: 02 April 2025 at 12:38am

Topic: SpamfilterISP bounces with message Remote host said: neutral

Posted By: Guests
Subject: SpamfilterISP bounces with message Remote host said: neutral
Date Posted: 16 September 2004 at 10:09am

One of our clients cannot receive mail because it bounces with the following message:

Remote host said: neutral

nslookup shows that reverse lookup does not match forward, is this what causes this?

Thanks

Ray

Replies:

Posted By: LogSat
Date Posted: 16 September 2004 at 11:51pm

Ray,

That error looks unusual, almost as is it's incomplete. Could you please post the entire bounce message, including the email headers please, so we can try to decipher it?

At first sight it looks like it may have to do something with the SPF filter, just because the word "neutral" can appear in the filter's results. What versin of SpamFilter are you using?

Roberto F.
LogSat Software

Posted By: Guests
Date Posted: 17 September 2004 at 12:51pm

Hi Roberto,

I checked the logs and found the following:

Here are some of the entries from the log:

09/15/04 17:11:27:187 -- (1072) Resolving 66.163.168.187 - smtp808.mail.sc5.yahoo.com
09/15/04 17:11:27:187 -- (1072) - SPF record found. analyzing: - v=spf1 ip4:38.113.1.0/24 ip4:38.113.20.0/24 ?all
09/15/04 17:11:27:187 -- (1072) - SPF analysis done: - neutral
09/15/04 17:11:27:187 -- (1072) 66.163.168.187 - Mail from: mailto:otke@otke-doucet.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:otke@otke-doucet.com’ - otke@otke-doucet.com To: mailto:cgraham@fclass.net" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:cgraham@fclass.net’ - cgraham@fclass.net will be quarantined

09/15/04 17:11:27:593 -- (3392) EMail from mailto:otke@otke-doucet.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:otke@otke-doucet.com’ - otke@otke-doucet.com to mailto:ray@FirstClassSolutions.net" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:ray@FirstClassSolutions.net’ - ray@FirstClassSolutions.net was queued. Size: 10 KB, 10240 bytes
09/15/04 17:11:27:609 -- (2484) Sending email from mailto:otke@otke-doucet.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:otke@otke-doucet.com’ - otke@otke-doucet.com to mailto:ray@FirstClassSolutions.net" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:ray@FirstClassSolutions.net’ - ray@FirstClassSolutions.net
09/15/04 17:11:27:625 -- (1072) EMail from mailto:otke@otke-doucet.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:otke@otke-doucet.com’ - otke@otke-doucet.com to mailto:cgraham@fclass.net" CLASS="ASPForums" TITLE="WARNING: URL created by poster. ‘mailto:cgraham@fclass.net’ - cgraham@fclass.net was received and quarantined. Size: 10 KB, 10240 bytes

I do not have headers on the returned mail, I received this from Lisa the party whose mail is being bounced

We are running release 2.1.1.367 . Chad claims the mail never gets into quarantine

Ray

From: Lisa Otke [ http://mailto:otke@otke-doucet.com" CLASS="ASPForums" TITLE="WARNING: URL created by poster. - http://mailto:otke@otke-doucet.com ]
Sent: Wednesday, September 15, 2004 5:13 PM
To: 'Chad Graham'; 'Ray Dunn'
Subject: RE: Correspondent keeps getting bounced...

I am hoping the email goes through to Ray since it probably won't got through to Chad. Per the email I received:

Message from yahoo.com.

Unable to deliver message to the following address(es).

<cgraham@fclass.net>:

206.114.196.32 failed after I sent the message.

Remote host said: neutral

Posted By: LogSat
Date Posted: 17 September 2004 at 10:04pm

Ray,

With the info you posted we were indeed able to reproduce the problem. It appears to be related to another bug that was fixed in a build released after 2.1.1.367. I've tested the latest pre-release build available, v2.1.1.380, and it is not affected by the issue. We will be releasing a new official build (2.1.1.384) this weekend (possibly even later tonite) that will also include the aove fix.

Roberto F. LogSat Software