Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

Excessive errors processing emails for

In the last few weeks I often get floated with Mail Fetcher errors from osticket:
Excessive errors processing emails for mail.example.org/post@example.org. Please manually check the inbox.


Most often some spam mails were still in the inbox on the server. After clearing the inbox, all went well again. However, since yesterday I am receiving these Mail Fetcher error mails but the inbox is empty! How can I stop them?

I already read
http://www.osticket.com/forum/discussion/8103/excessive-errors-processing-emails
http://osticket.com/forum/discussion/9826/excessive-errors-processing-emails
but the did not help. Also the discussion is closed so I had to open this new topic.



Comments

  • I get this Mail Fetcher email every two minutes. So my mailbox is floated. I have created a filter in my email client, however I want to get rid of the original issue. Osticket works so far. All emails seems to come in. How can I stop the Mail Fetcher errors / or how to find what issued this error mails?

    Thanks for your help!
  • sorry to once again post here. But unfortunately I run out of ideas where to troubleshoot. The system is running debian and the mailbox is empty. I still get this error everytime the cron job run the pop3 script. Any hint what I can do to stop this?
  • Please help us to help you by reading and following the posting guidelines in this thread: Please read before requesting assistance.

    That being said I'm not sure why your seeing errors but since you haven't really given us much information about your setup I wouldn't know where to being to help trying to troubleshoot.
  • edited February 2014
    I have recreated the mailbox from scratch. So the error was gone for some days. However, the "Excessive errors processing email for" error comes back with some emails. I guess this issue is caused due to unwellformed emails comming in. All emails I have seen associated with this error are spam emails.  If I delete the spam email directly in the mail box, the error is gone until a new email is causing this error.

    Here are details about the system:
    ostickt v1.7.3 with some mods.

    PHP Error log entries:  Mail Fetcher
    Excessive errors processing emails for mail.example.org/myeamil@example.org. Please manually check the inbox.

    Mail Sending: SMTP
    Mail Fetching/Receiving: POP
    Postfix 2.7.1
    PHP version: PHP 5.3.3-7+squeeze17 with Suhosin-Patch (cli) (built: Aug 26 2013 07:26:12)
    Operating System: Debian GNU/Linux 6.0
    Kernel: 2.6.32-042stab078.27
    Staff side: I see the error in osticket Dasboard -> System Logs and I also get notifications via email.

    A sample spam mail causing this error is:
    [quote]
    Return-Path: <spam mail address>
    X-Original-To: mymail@example.org
    Delivered-To: mymail@example.org
    Received: from mail9.netbeat.de (mail9.netbeat.de [83.243.58.174])
            by MYMAILSERVER (Postfix) with SMTP id 27D9xxxx
            for <mymail@example.org>; Fri, 14 Feb 2014 17:16:56 +0100 (CET)
    Received: (qmail 25606 invoked by uid 89); 14 Feb 2014 16:16:58 -0000
    Delivered-To: mydomain.org-info@mymail@example.org
    Received: (qmail 25604 invoked by uid 89); 14 Feb 2014 16:16:58 -0000
    Received: from host210-60-static.195-31-b.business.telecomitalia.it (31.195.60.210)
      by mail9.netbeat.de with SMTP; 14 Feb 2014 16:16:58 -0000

    <feff>Received: from 10.0.1.131 ([10.0.1.131])
    Message-ID: <F2CE492568CC4D2D8AEDFAC3716F68BF@home-jjkol10>
    From: "Ernst Smith" <mlakin@ensight.net>
    To: "Job Applicant" <mymail@example.org>
    Subject: Need
    Date: Fri, 14 Feb 2014 17:07:52 +0200 (EEST)
    MIME-Version: 1.0
    Content-Type: text/plain;
            format=flowed;
            charset="iso-8859-2";
            reply-type=original
    Content-Transfer-Encoding: 7bit
    X-Priority: 3
    X-MSMail-Priority: Normal
    X-Mailer: Microsoft Windows Mail 6.0.6001.18416
    X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6001.18645

    Dear Candidate!
    This is an offer of employment in one of the world leading companies our company. We believe that your knowledge, skills and experience will be among our most valuable assets. Our company is happy to offer a starting salary of $45,000 paid in weekly instalments.
    To participate in a competition for the current vacancy proceed to filling out a form [URL TO SPAMSITE REMOVED]
    Bye
    Bowmonk Company
    [/quote]

  • There are quite a few changes to mail in the last few versions.  You are running an older version at this point  I would recommend that you upgrade to at least 1.7.5, and preferably to 1.8.0.2.  You may want to setup a copy of your site and migrate the copy to 1.8.0.2 and see if you still get the same problem.  If you do not and are unwilling to upgrade your site you an at least take a look at the code difference from your version to current on github.  I've also pointed out this thread to the devs to take a look at. Since your running an old version and have modded it however I'm not sure that they will chime in.
  • Hello ntozier,

    thanks for your time and help. Since version update frequez raidly growed up the last few month, I decided to wait for next major relase with multilanguage support and plugin architecture. Our current osticket version is translated, so I have to translate the frontend each time I update osticket.

    I will take a look into a diff, maybe I can update the code manually.


  • @com_tom, You can get a patch to upgrade to 1.7.5 from here. On *nix, you can use patch -p1 < "patch file" to apply the patch. You may have trouble applying the patch, because you've translated the software. I'll help point you in the right direction to help get you upgraded.

    Concerning your posted email, was the <feff> really in the email? Was it literally <feff> or was it two bytes, 0xfeff (Unicode BOM)? That would be a very odd location for some characters like that.
  • @com_tom: your very welcome.  Sorry that I couldn't provide you a better solution. :)  Jared's post looks promising though.
Sign In or Register to comment.