Every 1 to 2 weeks, I get a single attempt to post a link spam. What is unusual is that it generates a double message from Mollom in the log file, one warning and one error.

The first log entry is always a warning that states:

Error 1000 from http://174.37.205.152: XMLRPC parse problem. The SAX parser returned: An invalid XML character (Unicode: 0x1f) was found in the element content of the document. - mollom.checkContent -

The message also includes the (very long) body content. This content is always the same.

Immediately after the warning is a second log entry. This one is an error that states:

Mollom was unavailable (error: 1000 - XMLRPC parse problem. The SAX parser returned: An invalid XML character (Unicode: 0x1f) was found in the element content of the document.)

From what I can tell, there is no actual problem with connecting to the Mollom servers. It's only this one attempted post. And other posts are being handled correctly at all times of the day. There is no consistent time for these attempted spam posts. It appears that the service doesn't like something being put into this particular message.

I don't want to post the actual message body until/unless requested. It's truly spam.

Please let me know if there is any other information I can provide to assist with troubleshooting this.

Comments

dries’s picture

dries commented

I did some investigating and this is due to Drupal sending invalid XML to Mollom, causing the Mollom XML parser to bail. This only seems to happen with CCK content types. I don't know what is causing this problem but could use some help debugging.

dries’s picture

dries commented

This issue is also related #277626: Checking CCK nodes with drop down lists lead to SAX 0x0 parsing error. Maybe we need to reopen that and mark this as duplicate?

scoutbaker’s picture

scoutbaker commented

Sorry for the delay in responding, I just noticed that I've received 0 e-mail notices about the issues in some of the queues where I've posted. Not all of them, just some.

I am more than willing to help troubleshoot. Is there something in particular that you need to get started?

I can say that these posts are attempted comments on forum postings. I haven't done anything to the forums with CCK. I do have CCK installed, but only recently started to work on a completely new content type. These errors have been appearing for longer than that.

Thanks, and please let me know what I can do to help.

dries’s picture

dries commented
Status: Active » Fixed

I believe this will be fixed in the next version of the Mollom module (what will be Mollom 6-1.11) as part of the big rewrite as how we deal with node content. I'm therefore going to mark this fixed.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.