Bugs item #1535214, was opened at 2006-08-05 17:20 Message generated for change (Comment added) made by jljacobs You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1535214&group_id=61702
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: jljacobs (jljacobs) Assigned to: Nobody/Anonymous (nobody) Summary: Mail without a To: field not sent to Inbox Initial Comment: NOted that spamBayes classified mail as ***Ham*** AND it does show up properly as Ham in the review of database BUT is ***NOT*** passed on to the Inbox (OE) and therefore is totally missing as new mail, either spam, unsure or ham. Until today after using SB for more than a year I realized that a good part of my mail was missing but only readable in the reviews of SpamBayes mail. So far NO spam arrives without a To: field in the body so that this is not an unresolvable problem. (BTW, the biggest new spam problem is 'image based' spam, which is not easily dealt with by text based statistical methodology.) I can bypass this (and as of today, 8/6/06) have in OE by setting up an OI Microsoft "rule" which is executed prior to allowing SpamBayes inputs. This hack sends such erroneous mail to the Inbox despite SpamBayes proper classification as Ham but not processing proxying it properly to the Inbox. I can provide any file that the developer(s) might want but with considerable annotation as I personally know what is Ham vs. Spam. --- John ---------------------------------------------------------------------- >Comment By: jljacobs (jljacobs) Date: 2006-08-06 18:27 Message: Logged In: YES user_id=1569546 To: Tony Meyer Let me define the SMTP 'body' as all the text that is not entered by SMTP servers in transit. The 'To:', 'From:' and 'Subject:' fields have the same status as the rest of a msg and none are even necessary to send mail. Try it by connecting to any SMTP server and send a msg by entering the SMTP commands (by brute force). The 'Envelope' header is the part of a msg added by the sending server and all intermediaries (of which their should be none --- relays). Now, proceeding here, there is a mailer used by an associate (in France) which sends Bcc: mail without and 'body' To: header whatsoever. My guess is that when that mail arrives since there is no 'To:' body header there is no place for Spambayes to add the 'ham', 'spam' or 'unsure' literals. The lack of a 'To:' field results in the mail being in the 'Browse Messages' listing and can be read there but it is NOT passed on to OE. It stops at the proxy. Carrying this further, if I use the 'To":' header for Spambayes to add the 'ham', 'spam' or 'unsure' result and I get a msg that has no 'To:' header (whether you want to call this the 'body' or the 'envelope' not being relevant, then you tell me where Spambayes is to put the resultand literal string. It simply does not exist in msgs from this mailer. I am trying to get around this by using OE's 'rules' but that is unreliable and really a cludge/hack. It appears to me that Spambayes recognize the ^^^lack of the field***, in this case the 'To:' field, which is configured for the concatination of the 'ham', 'spam' or 'unsure' string. If that is the configuration as mine is, Spambayes does not know what to do and though the messages are readable from browsing they get droped at that point and asre not passed on. I hope this clarifies the issue. Regards, John ---------------------------------------------------------------------- Comment By: Tony Meyer (anadelonbrin) Date: 2006-08-06 14:45 Message: Logged In: YES user_id=552329 This isn't particularly clear, sorry. The POP3 proxy lets *all* mail through - either with an X-Spambayes-Classification header, or an X-Spambayes-Exception header if something went wrong. Messages don't generally have a "To" in the body - this is in the headers of the message. Perhaps that was what you meant? Certainly every mail client I have seen (which includes all of the major OS X ones) does include a "To" header (but none include it in the body). If you are able to fix this by using a rule in OE, then that means that the mail *is* being delivered to Outlook Express - or the rule would never see it. Could you explain further what you mean? ---------------------------------------------------------------------- Comment By: jljacobs (jljacobs) Date: 2006-08-06 13:13 Message: Logged In: YES user_id=1569546 John here again ---- I note that the lack of SB passing Ham onto OE's Inbox is for me exclusively related to mail from a Mac where the mailer totally fails to insert the "To:" in the msg body. I am at a loss to deal with this as it does not always occur but appears to happen randomly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1535214&group_id=61702 _______________________________________________ Spambayes-bugs mailing list [email protected] http://mail.python.org/mailman/listinfo/spambayes-bugs
