All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] Diagnostic-Code: x-unix; internal software error / Command time limit exceeded: "/usr/lo
Date: Mon, 14 Mar 2016 02:35:04 +0000	[thread overview]
Message-ID: <56E62358.5010500@yahoo.com.au> (raw)
In-Reply-To: <266C729B-6A87-42DA-A5F3-AAB5827EE39E@wolfgarten.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="windows-1254", Size: 2263 bytes --]

I'm listening, I'm just a bit stumped.

I feel like if this was an Mlmmj bug, it would've manifested long ago. Nothing I 
know of has changed Mlmmj-wise, but this problem has just appeared in the last 
three months or so.

I wonder if something has changed recently in a relevant platform or MTA.

Could you confirm your Mlmmj, OS and MTA versions, and anything else you feel 
might be relevant about your environment?

It seems that something is enforcing a command time limit. Not sure if it's via 
the kernel or not, but I guess it's initiated if not enforced by the shell or MTA.

Ben



On 14/03/2016 6:45 am, sebastian@wolfgarten.com wrote:
> (Resending message to see whether there is anyone who has seen this issue before
> or can tell me how to troubleshoot this - thanks. And sorry for the double-posting.)
>
> Hi,
>
> I am running mlmmi 1.2.17.1 on FreeBSD 10 and I have come across a very strange
> issue similar to the one described by a guy in December last year (see
> http://mlmmj.org/archive/mlmmj/2015-12/0000000.html).
> Basically I have a mailing list (besides many others that are working fine!) for
> which some people receive emails, others are not getting any messages. The
> moderators are sometimes also getting no messages to approve or they do receive
> the following error:
> —
> This is the mail system at host waldfest.wolfgarten.com
> <http://waldfest.wolfgarten.com>.
>
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to postmaster.
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
>                     The mail system
>
> <elsaalumni.de--newsletter+moderate-7d4f69f9439871f4@localhost.mlmmj
> <mailto:elsaalumni.de--newsletter+moderate-7d4f69f9439871f4@localhost.mlmmj>>: Command
>      time limit exceeded: "/usr/local/bin/mlmmj-recieve"
>
> --
> Alternatively I have had situations, in which I am getting the „x-unix; internal
> software error" message - anyone seen the same?
> In the logs I cannot find anything which looks like an error - any ideas on how to
> best troubleshoot this?
> Thanks.
> Best regards
> Sebastian


  parent reply	other threads:[~2016-03-14  2:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 21:56 [mlmmj] Diagnostic-Code: x-unix; internal software error / Command time limit exceeded: "/usr/local/ Sebastian Wolfgarten
2016-03-13 19:45 ` sebastian
2016-03-14  2:35 ` Ben Schmidt [this message]
2016-03-16 20:22 ` [mlmmj] Diagnostic-Code: x-unix; internal software error / Command time limit exceeded: "/usr/lo Sebastian Wolfgarten
2016-03-20 22:52 ` Ben Schmidt
2016-03-21 21:07 ` Sebastian Wolfgarten

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56E62358.5010500@yahoo.com.au \
    --to=mail_ben_schmidt@yahoo.com.au \
    --cc=mlmmj@mlmmj.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.