Hi Phil,
I started receiving lots of "MAILER-DAEMON"s since
yesterday (from the devl list), telling about message
loops. See one below.
Is there any relation to this gmane thing?
And more importantly is there any way to fix this?
Brgds,
Viktor
Begin forwarded message:
From: [EMAIL PROTECTED]
Date: 2008. június 10. 4:56:54 GMT+02:00
To: [EMAIL PROTECTED]
Subject: failure notice
Hi. This is the qmail-send program at taz5.fiberhosting.net.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[email protected]>:
This message is looping: it already has my Delivered-To line. (#5.4.6)
--- Below this line is a copy of the message.
Return-Path: <[EMAIL PROTECTED]>
Received: (qmail 19938 invoked from network); 9 Jun 2008 22:56:53
-0400
Received: from cable-83.217.158.241.static.coditel.net (HELO
mafact.be) (83.217.158.241)
by harbour-project.org with SMTP; 9 Jun 2008 22:56:53 -0400
Received-SPF: none (harbour-project.org: domain at syenar.hu does
not designate permitted sender hosts)
Received: (qmail 3816 invoked from network); 8 Jun 2008 10:02:32 -0400
Received: from localhost (HELO taz5.fiberhosting.net) (127.0.0.1)
by localhost with SMTP; 8 Jun 2008 10:02:31 -0400
Return-Path: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 3715 invoked from network); 8 Jun 2008 10:02:28 -0400
Received: from gv-out-0910.google.com (216.239.58.190)
by harbour-project.org with SMTP; 8 Jun 2008 10:02:28 -0400
Received-SPF: none (harbour-project.org: domain at syenar.hu does not
designate permitted sender hosts)
Received: by gv-out-0910.google.com with SMTP id r4so454476gve.0
for <[email protected]>; Sun, 08 Jun 2008 07:02:26 -0700
(PDT)
Received: by 10.103.17.10 with SMTP id u10mr1533842mui.
97.1212933745982;
Sun, 08 Jun 2008 07:02:25 -0700 (PDT)
Return-Path: <[EMAIL PROTECTED]>
Received: from ?192.168.3.5? ( [84.1.175.112])
by mx.google.com with ESMTPS id y2sm36077845mug.1.2008.06.08.07.02.24
(version=TLSv1/SSLv3 cipher=RC4-MD5);
Sun, 08 Jun 2008 07:02:25 -0700 (PDT)
Message-Id: <[EMAIL PROTECTED]>
From: =?ISO-8859-1?Q?Szak=E1ts_Viktor?= <[EMAIL PROTECTED]>
To: "Harbour Project Main Developer List." <[email protected]
>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v924)
Date: Sun, 8 Jun 2008 16:01:27 +0200
X-Mailer: Apple Mail (2.924)
Subject: [Harbour] Core constant cleanup
X-BeenThere: [email protected]
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: "Harbour Project Main Developer List." <[email protected]
>
List-Id: "Harbour Project Main Developer List." <harbour.harbour-
project.org>
List-Unsubscribe: <http://lists.harbour-project.org/mailman/listinfo/harbour
>,
<mailto:[EMAIL PROTECTED]>
List-Archive: <http://lists.harbour-project.org/pipermail/harbour>
List-Post: <mailto:[email protected]>
List-Help: <mailto:[EMAIL PROTECTED]>
List-Subscribe: <http://lists.harbour-project.org/mailman/listinfo/harbour
>,
<mailto:[EMAIL PROTECTED]>
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]
X-MDBadQueue-Reason: maximum hop count exceeded (possible message
loop)
Hi all,
I plan to clean constants as below:
OS_UNIX_COMPATIBLE -> HB_OS_UNIX_COMPATIBLE
OS_PATH_LIST_SEPARATOR -> HB_OS_PATH_LIST_SEP_CHR
OS_PATH_DELIMITER -> HB_OS_PATH_DELIM_CHR
OS_PATH_DELIMITER_STRING -> HB_OS_PATH_DELIM_STR
OS_PATH_DELIMITER_LIST -> HB_OS_PATH_DELIM_LIST
OS_FILE_MASK -> HB_OS_ALLFILE_MASK
OS_DRIVE_DELIMITER -> HB_OS_DRIVE_DELIM_CHR
OS_HAS_DRIVE_LETTER -> HB_OS_HAS_DRIVE_LETTER
OS_OPT_DELIMITER_LIST -> HB_OS_OPT_DELIM_LIST
OS_EOL_LEN -> HB_OS_EOL_LEN
HARBOUR_GCC_OS2 -> HB_OS_OS2_GCC
HARBOUR_START_PROCEDURE -> HB_START_PROCEDURE
HARBOUR_MAIN_STD -> HB_MAIN_STD
HARBOUR_MAIN_WIN -> HB_MAIN_WIN
HARBOUR_MAX_RDD_DRIVERNAME_LENGTH -> HB_RDD_MAX_DRIVERNAME_LEN
HARBOUR_MAX_RDD_ALIAS_LENGTH -> HB_RDD_MAX_ALIAS_LEN
HARBOUR_MAX_RDD_AREA_NUM -> HB_RDD_MAX_AREA_NUM
The main point here is usage if HB_ as standard
plus I've made some other cleanup to make names
more distinctive, better align with similar ones,
and possibly shorter.
Please comment. We can of course leave those ones
which may be used by 3rd parties to live for a while
with the old name too, to not break them.
Brgds,
Viktor
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
_______________________________________________
Harbour mailing list
[email protected]
http://lists.harbour-project.org/mailman/listinfo/harbour
