waynej

Ah, this is discussed in several forums lately. Do a web search for "perl sa-learn Argument isn't numeric in numeric". It's some warning due to perl / spamassassin versions, I guess.

My old cgi script for spam assassin training has recently started reporting errors - the lines starting with "Argument" here in the output: Learning SPAM: Argument "0.70_01" isn't numeric in numeric ge (>=) at /usr/local/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm line 214. Argument "0.70_01" isn't numeric in numeric lt (<) at /usr/local/share/perl5/Mail/SpamAssassin/Dns.pm line 521. .......................................................................................................................................................................................................................................................................................................................................................................................................................... Learned tokens from 45 message(s) (410 message(s) examined) Learning HAM: Argument "0.70_01" isn't numeric in numeric ge (>=) at /usr/local/share/perl5/Mail/SpamAssassin/Plugin/AskDNS.pm line 214. Argument "0.70_01" isn't numeric in numeric lt (<) at /usr/local/share/perl5/Mail/SpamAssassin/Dns.pm line 521. .............................................................. Learned tokens from 4 message(s) (62 message(s) examined) Here is the (obfuscated) script - is there some updated example I should copy, or is there some newer way to train spam assassin? #!/usr/bin/perl my $salearn = "/usr/bin/sa-learn"; $|; print "Content-type: text/plain\n\n"; print "Learning SPAM:\n"; print `$salearn -p /home/cpanelusername/.spamassassin/user_prefs --spam --showdots /home/cpanelusername/mail/domainname/mailusername/.myspam/{cur,new} 2>&1`; print "\n\n"; print "Learning HAM:\n"; print `$salearn -p /home/cpanelusername/.spamassassin/user_prefs --ham --showdots /home/cpanelusername/mail/domainname/mailusername/.myham/{cur,new} 2>&1`; print "\n\n"; exit;

Thanks, TCH-Jesse, and everyone else! I now see why I never noticed this before. I recently upgraded from Thunderbird 1.0 to 2.0. The new version forwards an attachment like this: Content-Type: message/rfc822; name="Re: subject line.eml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="subject line.eml" whereas the old version would forward mail as an attachment like this: Content-Type: message/rfc822; name="subject line" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="subject line"

I've suddenly noticed that if I send an email with a .eml attachment (which is how Thunderbird forwards messages), TCH is apparently rejecting that incoming email. I believe this is new behavior. It even occurs sending to my login on server78. Why is this happening? Here's an example where I obfuscated my email address and some other things. I send email out (SMTP) via RoadRunner (therefore you see rr.com) but only emails which end up on a TCH server get rejected. Return-path: <> Envelope-to: MyEmailAddress Delivery-date: Fri, 07 Sep 2007 08:22:18 -0400 Received: from mailnull by server78.tchmachines.com with local (Exim 4.66) id 1ITcqo-0002P2-Iy for MyEmailAddress; Fri, 07 Sep 2007 08:22:18 -0400 X-Failed-Recipients: MyEmailAddress Auto-Submitted: auto-replied From: Mail Delivery System <Mailer-Daemon@server78.tchmachines.com> To: MyEmailAddress Subject: Mail delivery failed: returning message to sender Message-Id: <E1ITcqo-0002P2-Iy@server78.tchmachines.com> Date: Fri, 07 Sep 2007 08:22:18 -0400 This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: MyEmailAddress This message has been rejected because it has a potentially executable attachment "test message.eml" This form of attachment has been used by recent viruses or other malware. If you meant to send this file then please package it up as a zip file and resend it. ------ This is a copy of the message, including all the headers. ------ Return-path: <MyEmailAddress> Received: from cdptpa-omtalb.mail.rr.com ([75.180.132.120]) by server78.tchmachines.com with esmtp (Exim 4.66) (envelope-from <MyEmailAddress>) id 1ITcqg-0002OZ-DJ for MyEmailAddress; Fri, 07 Sep 2007 08:22:18 -0400 Received: from [192.168.1.101] (really [71.75.187.141]) by cdptpa-omta02.mail.rr.com with ESMTP id <20070907122214.OIPR3965.cdptpa-omta02.mail.rr.com@[192.168.1.101]> for <MyEmailAddress>; Fri, 7 Sep 2007 12:22:14 +0000 Message-ID: <46E14276.1090000@MyDomain> Date: Fri, 07 Sep 2007 08:22:14 -0400 From: me <MyEmailAddress> User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: me <MyEmailAddress> Subject: [Fwd: test message] Content-Type: multipart/mixed; boundary="------------090303080505080809010201" X-Spam-Status: No, score=-1.8 X-Spam-Score: -17 X-Spam-Bar: - X-Spam-Flag: NO This is a multi-part message in MIME format. --------------090303080505080809010201 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit --------------090303080505080809010201 Content-Type: message/rfc822; name="test message.eml" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="test message.eml" ...

That did it, thanks!

Thanks Andy, but SpamAssassin doesn't like --maildir Unknown option: maildir Is there a later version of SpamAssassin I should be picking up? I'm getting SpamAssassin version 3.2.1

The script I ended up with was #!/usr/bin/perl my $salearn = "/usr/bin/sa-learn"; $|; print "Content-type: text/plain\n\n"; print "Learning SPAM:\n"; print `$salearn -p /home/mylogin/.spamassassin/user_prefs --mbox --spam --showdots /home/mylogin/mail/myspam 2>&1`; print "\n\n"; print "Learning HAM:\n"; print `$salearn -p /home/mylogin/.spamassassin/user_prefs --mbox --ham --showdots /home/mylogin/mail/myham 2>&1`; print "\n\n"; exit; But with the mail changes from a couple weeks ago, should /home/mylogin/mail/myspam be changed to something like /home/mylogin/mail/.myspam/cur (or the applicable per-user box) now? Nothing seems to work - tells me zero messages. Is there hope of it working with the one-file-per-message format in the 'cur' directory?

Good job in spotting that site. I found it also by a search. However, 'undergoing maintenance' blurb is visible on every page of http://www.aboutus.org and is not about dnscentral.com. And I am the one that posted the blurb about dnscentral.com being down since yesterday. I am just fishing for a place where people might post knowledgeable status or at least discuss it in comp.mail.misc. I was just hoping someone in the TCH family might be similarly affected like me or have advice.

dnscentral.com has been down for perhaps 24 hours now. Anyone know their status? I have a "forwarding account" with them for my email which then goes to an account with TCH. So no email to my regular email address is getting through. The numbers on their Google-cached web page say voice mailbox is full. Technical contact for whois has two phone numbers both of which say out of service. I started a thread in comp.mail.misc about this since I didn't know where else to get status.

Thanks for the advice. I didn't realize that the default mailing address isn't really needed for anything like for administrative stuff. As long as you have an email account for "Please update your contact information here.", I guess that's all TCH needs.

In cPanel you can Change Quota on email accounts but not the Main Account. What is the quota on the main account - whatever your disk quota will allow? And is it a good idea to not use this address for your personal email, reserving the main account for important things related to the domain?

No, I wasn't looking for more information. Maybe I am wrong for my whole premise, but when I have a problem, I might look in the forums. I thought others might do that too. That's why I started this thread. I was happy enough with my previous message being the last in the thread. A reader would gather that it's a problem that sometimes happens to some people and you need to open a ticket when it occurs.

I received the exact same error again on January 15. I didn't have time to enter a ticket until this morning. It got fixed very quickly. I then asked what caused the problem. Got answer of "There was a configuration issue with Front Page installation. We have fixed it. Please feel free to contact us, if you experience any such issues in future."

I don't have a line like that in my .htaccess but things work anyway.

Sorry I didn't open up a ticket right away. But tonight I tried it from the same computer and it worked. So someone fixed something!