Skip to Content.
Sympa Menu

en - [sympa-users] [Fwd: Ihre Nachricht an heph03 abgelehnt]

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Adam Bernstein <address@concealed>
  • To: "address@concealed" <address@concealed>
  • Subject: [sympa-users] [Fwd: Ihre Nachricht an heph03 abgelehnt]
  • Date: Tue, 15 Apr 2008 17:22:39 -0700

Okay, I have to ask: why am I suddenly getting this whenever I post to sympa-users? Did somebody subscribe another sympa list in Germany to this one, or something?

ab
--- Begin Message ---
  • From: SYMPA <address@concealed>
  • To: address@concealed
  • Subject: Ihre Nachricht an heph03 abgelehnt
  • Date: Wed, 16 Apr 2008 02:18:51 +0200 (CEST)
Ihre Nachricht an die Liste heph03 wurde abgelehnt.
Sie wurde daher an Sie zurückgesendet.

Ihre Nachricht :
Return-Path: <address@concealed>
X-Original-To: address@concealed
Delivered-To: address@concealed
Received: from suncom4.cms.hu-berlin.de (suncom4.cms.hu-berlin.de
[141.20.1.74])
by sympa.cms.hu-berlin.de (Postfix) with ESMTP id 574A7650121
for <address@concealed>; Wed, 16 Apr 2008 02:18:48 +0200
(CEST)
Received: from ir2.cms.hu-berlin.de (ir2.cms.hu-berlin.de [141.20.1.148])
by suncom4.cms.hu-berlin.de (8.13.8/8.13.8) with ESMTP id
m3G0GO6M007561
for <address@concealed>; Wed, 16 Apr 2008 02:16:24 +0200 (CEST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result:
AqkAAFriBEjD3F6DnGdsb2JhbACRWgEBAQEBCAUJBxQymm2CJQ
X-IronPort-AV: E=Sophos;i="4.25,662,1199660400";
d="scan'208";a="6538761"
Received: from smtp1.cru.fr ([195.220.94.131])
by ir2.cms.hu-berlin.de with ESMTP; 16 Apr 2008 02:16:23 +0200
Received: from listes.cru.fr (listes.cru.fr [195.220.94.165])
by smtp1.cru.fr (8.13.1/8.13.1) with ESMTP id m3G0FW1n022975;
Wed, 16 Apr 2008 02:15:32 +0200
Received: (from sympa@localhost)
by listes.cru.fr (8.13.8/8.13.8/8.12-CW) id m3G0FVac021560;
Wed, 16 Apr 2008 02:15:31 +0200
X-Authentication-Warning: listes.cru.fr: Processed by sympa with -C
/etc/mail/sympa.cf
Received: from mx.cru.fr (mx.cru.fr [195.220.94.133])
by listes.cru.fr (8.13.8/8.13.8/8.12-CW) with ESMTP id m3G0FUgI021556
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
for <address@concealed>; Wed, 16 Apr 2008 02:15:30 +0200
Received: from internal.electricembers.net (internal.electricembers.net
[209.209.81.71])
by mx.cru.fr (8.13.1/8.13.1/8.12-CW) with ESMTP id m3G0FTOX030316
for <address@concealed>; Wed, 16 Apr 2008 02:15:29 +0200
Received: from [192.168.2.29] (adsl-68-123-141-57.dsl.pltn13.pacbell.net
[68.123.141.57])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: adam)
by internal.electricembers.net (Postfix) with ESMTP id 9AF121FFC75
for <address@concealed>; Tue, 15 Apr 2008 17:15:28 -0700 (PDT)
Message-ID: <address@concealed>
Date: Tue, 15 Apr 2008 17:15:27 -0700
From: Adam Bernstein <address@concealed>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: "address@concealed" <address@concealed>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [sympa-users] custom task models?
X-Loop: address@concealed
X-Sequence: 376
Errors-to: address@concealed
Precedence: list
Precedence: bulk
X-no-archive: yes
List-Id: <sympa-users.cru.fr>
List-Archive: <http://listes.cru.fr/sympa/arc/sympa-users>
List-Help: <mailto:address@concealed?subject=help>
List-Owner: <mailto:address@concealed>
List-Post: <mailto:address@concealed>
List-Subscribe: <mailto:address@concealed?subject=subscribe%20sympa-users>
List-Unsubscribe: <mailto:address@concealed?subject=unsubscribe%20sympa-users>

Sympa folks:

I've tried to create a custom version of the expire_bounce.daily.task, with
a bounce expiration time of 30 days instead of 10, and had some trouble. I
thought that I should copy it to etc/task_models and customize it there,
but that had no effect -- it still created the default task. Only by
editing the distribution file in bin/etc/global_task_models was I able to
change it, and I assume that customization will be overwritten the next
time I upgrade Sympa.

I also tried creating it in etc/task_models and giving it a different name,
and specifying that new name in sympa.conf with expire_bounce_task, but
that just resulted in an ERROR task file. Did I just make a syntax
mistake? The custom file was called expire_bounce.npo-daily.task, and
sympa.conf said:
expire_bounce_task npo-daily

What is the correct way to create a custom version of a default task model?

ab

--- End Message ---



Archive powered by MHonArc 2.6.19+.

Top of Page