From owner-ctm-users@FreeBSD.ORG Tue Jan 19 18:49:12 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0B1F106568B for ; Tue, 19 Jan 2010 18:49:12 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F90D8FC20 for ; Tue, 19 Jan 2010 18:49:11 +0000 (UTC) Received: from mail2.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0JInAlP025227 for ; Tue, 19 Jan 2010 19:49:10 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail2.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0JInAbQ028782 for ; Tue, 19 Jan 2010 19:49:10 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id o0JInAeR084589 for ctm-users@freebsd.org; Tue, 19 Jan 2010 19:49:10 +0100 (CET) Date: Tue, 19 Jan 2010 19:49:10 +0100 From: Andre Albsmeier To: ctm-users@freebsd.org Message-ID: <20100119184910.GA7415@curry.mchp.siemens.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.20 (2009-06-14) Subject: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2010 18:49:12 -0000 Apart from ports-cur I didn't receive any deltas via email the last couple of days. I am missing ctm-src-4-fast (OK, nothing happens here), ctm-src-7-fast and ctm-src-cur-fast. And the ports-cur deltas seem to be sent differently now (no more Sender: header in the email)... Anyone else experiencing this? -Andre From owner-ctm-users@FreeBSD.ORG Tue Jan 19 21:18:11 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7165A106566B for ; Tue, 19 Jan 2010 21:18:11 +0000 (UTC) (envelope-from utisoft@googlemail.com) Received: from mail-bw0-f209.google.com (mail-bw0-f209.google.com [209.85.218.209]) by mx1.freebsd.org (Postfix) with ESMTP id A70E88FC1D for ; Tue, 19 Jan 2010 21:18:09 +0000 (UTC) Received: by bwz1 with SMTP id 1so1979676bwz.13 for ; Tue, 19 Jan 2010 13:18:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=QSBD/zKkp4lPlLODoy3Y6/ROp6ceeTdQ8T1cWb1JVe4=; b=eNcEE/J1Pp+Sobr99BpLI1iKAt7Q/Wm2E+D9E0o3VH1Py/tRxIAyNHOX1SLcX2eQ0Z TkzlX7S/5ZE3I0ecDbgjBZzChYxiafWoEIlrVydiAyUGkOmGOMXxOEfecJIvWU3SjRGp 8/TAfk4mf5MVu5jMeg2j3PV1BIJWnl0mCVho4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:content-type; b=oLQAtQVCTJOUmOdf4lPyqfchymjVbjyHGu666gWktt2wVtBzjpAKRR+i5oJFNfFR5o 7ncr0DV3+Z+FLcMJvJJbH1a+qbLCGnkHMqAJbE0X91EokZJnKpWUlrHzwlOLF0VLlTDa OacjtRU3qVQhBI+cRRi0H2/CyCBvyY61xq9oI= MIME-Version: 1.0 Received: by 10.204.144.86 with SMTP id y22mr1752184bku.43.1263934173424; Tue, 19 Jan 2010 12:49:33 -0800 (PST) In-Reply-To: <20100119184910.GA7415@curry.mchp.siemens.de> References: <20100119184910.GA7415@curry.mchp.siemens.de> From: Chris Rees Date: Tue, 19 Jan 2010 20:49:13 +0000 Message-ID: To: Andre Albsmeier , ctm-users@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: utisoft@gmail.com List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2010 21:18:11 -0000 2010/1/19 Andre Albsmeier : > Apart from ports-cur I didn't receive any deltas via email > the last couple of days. I am missing ctm-src-4-fast (OK, > nothing happens here), ctm-src-7-fast and ctm-src-cur-fast. > > And the ports-cur deltas seem to be sent differently now > (no more Sender: header in the email)... > > Anyone else experiencing this? > Sorry, cvs-cur is coming in fine for me! Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? From owner-ctm-users@FreeBSD.ORG Tue Jan 19 21:51:44 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1DFFC1065672 for ; Tue, 19 Jan 2010 21:51:44 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id DCE738FC16 for ; Tue, 19 Jan 2010 21:51:43 +0000 (UTC) Received: from [128.206.184.213] (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id o0JLpgaw002428; Tue, 19 Jan 2010 15:51:42 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <4B56296E.1070905@missouri.edu> Date: Tue, 19 Jan 2010 15:51:42 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.1.7) Gecko/20100113 SeaMonkey/2.0.2 MIME-Version: 1.0 To: "utisoft@gmail.com" References: <20100119184910.GA7415@curry.mchp.siemens.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "ctm-users@freebsd.org" , Andre Albsmeier , Chris Rees Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jan 2010 21:51:44 -0000 Chris Rees wrote: > 2010/1/19 Andre Albsmeier: >> Apart from ports-cur I didn't receive any deltas via email >> the last couple of days. I am missing ctm-src-4-fast (OK, >> nothing happens here), ctm-src-7-fast and ctm-src-cur-fast. >> >> And the ports-cur deltas seem to be sent differently now >> (no more Sender: header in the email)... >> >> Anyone else experiencing this? >> > > Sorry, cvs-cur is coming in fine for me! > > Chris > The *-fast deltas are processed differently, so it is possible that they are not getting out, whereas the other ones are. The host that creates the deltas is part of the University of Missouri, and they keep changing their firewall etc stuff all the time, so for all I know, they have found a way to block them. It is the beginning of the semester at MU, and I start my first class tomorrow. So I might not get to it for a little while. In the mean time, if anyone else is not getting their emails, please post to this group so that I have some sense of how big the problem is. Thanks, Stephen From owner-ctm-users@FreeBSD.ORG Wed Jan 20 02:24:32 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 42600106568B for ; Wed, 20 Jan 2010 02:24:32 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id BD7778FC0A for ; Wed, 20 Jan 2010 02:24:30 +0000 (UTC) Received: from park.js.berklix.net (p549A3104.dip.t-dialin.net [84.154.49.4]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id o0K2ORLb025876; Wed, 20 Jan 2010 02:24:27 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id o0K2OGq8025754; Wed, 20 Jan 2010 03:24:16 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id o0K2NpSj019912; Wed, 20 Jan 2010 03:24:09 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201001200224.o0K2NpSj019912@fire.js.berklix.net> To: Andre Albsmeier , Stephen Montgomery-Smith From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Tue, 19 Jan 2010 19:49:10 +0100." <20100119184910.GA7415@curry.mchp.siemens.de> Date: Wed, 20 Jan 2010 03:23:51 +0100 Sender: jhs@berklix.com Cc: ctm-users@freebsd.org Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jan 2010 02:24:32 -0000 Andre Albsmeier wrote: > Apart from ports-cur I didn't receive any deltas via email > the last couple of days. I am missing ctm-src-4-fast (OK, > nothing happens here), ctm-src-7-fast and ctm-src-cur-fast. > > And the ports-cur deltas seem to be sent differently now > (no more Sender: header in the email)... > > Anyone else experiencing this? Summary: I dont see a problem receiving here at Wed Jan 20 03:20:36 CET 2010 Detail: I get all my deltas via -fast too. Here TZ=GMT+01:00 I just ran fetchmail, & my script http://berklix.com/~jhs/src/bsd/jhs/bin/local/ctms shows this: ------ /pub/FreeBSD/development/CTM/src-4 src-4.2350.gz /pub/FreeBSD/branches/4.0-stable/src src-4 2350 /pri/FreeBSD/branches/4.0-stable/src No .ctm_status /pri/FreeBSD/branches/4.0-stable/src No .ctm_status ctm -v /pub/FreeBSD/development/CTM/src-4/src-4.2[0-9][0-9][0-9].gz /pub/FreeBSD/development/CTM/src-5 src-5.0859.gz /pub/FreeBSD/branches/5.0-stable/src src-5 859 /pri/FreeBSD/branches/5.0-stable/src No .ctm_status /pri/FreeBSD/branches/5.0-stable/src No .ctm_status ctm -v /pub/FreeBSD/development/CTM/src-5/src-5.0[6-9][0-9][0-9].gz /pub/FreeBSD/development/CTM/src-6 src-6.1552.gz /pub/FreeBSD/branches/6.0-stable/src src-6 1552 /pri/FreeBSD/branches/6.0-stable/src No .ctm_status /pri/FreeBSD/branches/amd64/6.0-stable/src No .ctm_status /pri/FreeBSD/branches/i386/6.0-stable/src No .ctm_status ctm -v /pub/FreeBSD/development/CTM/src-6/src-6.1[0-9][0-9][0-9].gz /pub/FreeBSD/development/CTM/src-7 src-7.0895.gz /pub/FreeBSD/branches/7.0-stable/src src-7 895 /pri/FreeBSD/branches/7.0-stable/src No .ctm_status /pri/FreeBSD/branches/amd64/7.0-stable/src No .ctm_status /pri/FreeBSD/branches/i386/7.0-stable/src No .ctm_status ctm -v /pub/FreeBSD/development/CTM/src-7/src-7.[0-9][0-9][0-9][0-9].gz /pub/FreeBSD/development/CTM/src-8 src-8.0198.gz /pub/FreeBSD/branches/8.0-stable/src src-8 198 /pri/FreeBSD/branches/8.0-stable/src No .ctm_status /pri/FreeBSD/branches/amd64/8.0-stable/src No .ctm_status /pri/FreeBSD/branches/i386/8.0-stable/src No .ctm_status ctm -v /pub/FreeBSD/development/CTM/src-8/src-8.[0-9][0-9][0-9][0-9].gz /pub/FreeBSD/development/CTM/src-cur src-cur.9236.gz /pub/FreeBSD/branches/-current/src src-cur 9236 /pri/FreeBSD/branches/-current/src No .ctm_status /pri/FreeBSD/branches/amd64/-current/src No .ctm_status /pri/FreeBSD/branches/i386/-current/486/src No .ctm_status /pri/FreeBSD/branches/i386/-current/586/src No .ctm_status /pri/FreeBSD/branches/i386/-current/686/src No .ctm_status /pri/FreeBSD/branches/i386/-current/src No .ctm_status ctm -v /pub/FreeBSD/development/CTM/src-cur/src-*.8[5-9][0-9][0-9].gz /pub/FreeBSD/development/CTM/ports-cur ports-cur.8161.gz /pub/FreeBSD/branches/-current/ports ports-cur 8161 /pri/FreeBSD/branches/-current/ports ports-cur 8160 /pri/FreeBSD/branches/amd64/-current/ports ports-cur 8160 /pri/FreeBSD/branches/i386/-current/486/ports ports-cur 8160 /pri/FreeBSD/branches/i386/-current/586/ports No .ctm_status /pri/FreeBSD/branches/i386/-current/686/ports ports-cur 8160 /pri/FreeBSD/branches/i386/-current/ports ports-cur 8160 /usr/ports No .ctm_status ctm -v /pub/FreeBSD/development/CTM/ports-cur/ports-cur.8[0-4][0-9][0-9].gz /pub/FreeBSD/development/CTM/cvs-cur cvs-cur.16123.gz /pub/FreeBSD/development/FreeBSD-CVS cvs-cur 16123 /pri/FreeBSD/development/FreeBSD-CVS cvs-cur 16117 /usr/cvs cvs-cur 16117 ctm -v /pub/FreeBSD/development/CTM/cvs-cur/cvs-cur.16[0-9][0-9][0-9].gz rlogin -l mailnull-csh localhost unsetenv TMPDIR ------ To show timestamps i just typed in this: ------- #!/bin/csh foreach i ( /pub/FreeBSD/development/CTM/src-4 \ /pub/FreeBSD/development/CTM/src-5 \ /pub/FreeBSD/development/CTM/src-6 \ /pub/FreeBSD/development/CTM/src-7 \ /pub/FreeBSD/development/CTM/src-8 \ /pub/FreeBSD/development/CTM/src-cur \ /pub/FreeBSD/development/CTM/ports-cur \ /pub/FreeBSD/development/CTM/cvs-cur ) echo $i (cd $i ; ls -l | tail -1 ) echo end /pub/FreeBSD/development/CTM/src-4 -r--r--r-- 1 mailnull mailnull 528 Jun 24 2009 src-4.2350.gz /pub/FreeBSD/development/CTM/src-5 -r--r--r-- 1 mailnull mailnull 392 Jan 7 11:36 src-5.0859.gz /pub/FreeBSD/development/CTM/src-6 -r--r--r-- 1 mailnull mailnull 2746 Jan 18 16:35 src-6.1552.gz /pub/FreeBSD/development/CTM/src-7 -r--r--r-- 1 mailnull mailnull 3068 Jan 20 01:10 src-7.0895.gz /pub/FreeBSD/development/CTM/src-8 -r--r--r-- 1 mailnull mailnull 7460 Jan 20 00:10 src-8.0198.gz /pub/FreeBSD/development/CTM/src-cur -r--r--r-- 1 mailnull mailnull 4039 Jan 19 01:10 src-cur.9236.gz /pub/FreeBSD/development/CTM/ports-cur -r--r--r-- 1 mailnull mailnull 34220 Jan 19 01:10 ports-cur.8161.gz /pub/FreeBSD/development/CTM/cvs-cur -r--r--r-- 1 mailnull mailnull 53601 Jan 19 23:40 cvs-cur.16123.gz Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text not quoted-printable, HTML or Base64 http://www.asciiribbon.org From owner-ctm-users@FreeBSD.ORG Wed Jan 20 06:34:46 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA4B81065672 for ; Wed, 20 Jan 2010 06:34:46 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.freebsd.org (Postfix) with ESMTP id 3D94B8FC14 for ; Wed, 20 Jan 2010 06:34:45 +0000 (UTC) Received: from mail3.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0K6YiS1010132; Wed, 20 Jan 2010 07:34:44 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0K6YiUZ011654; Wed, 20 Jan 2010 07:34:44 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id o0K6YiTj087249; Date: Wed, 20 Jan 2010 07:34:43 +0100 From: Andre Albsmeier To: Stephen Montgomery-Smith Message-ID: <20100120063443.GA1303@curry.mchp.siemens.de> References: <20100119184910.GA7415@curry.mchp.siemens.de> <4B56296E.1070905@missouri.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B56296E.1070905@missouri.edu> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "ctm-users@freebsd.org" , "Albsmeier, Andre" , Chris Rees Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jan 2010 06:34:46 -0000 On Tue, 19-Jan-2010 at 22:51:42 +0100, Stephen Montgomery-Smith wrote: > Chris Rees wrote: > > 2010/1/19 Andre Albsmeier: > >> Apart from ports-cur I didn't receive any deltas via email > >> the last couple of days. I am missing ctm-src-4-fast (OK, > >> nothing happens here), ctm-src-7-fast and ctm-src-cur-fast. > >> > >> And the ports-cur deltas seem to be sent differently now > >> (no more Sender: header in the email)... > >> > >> Anyone else experiencing this? > >> > > > > Sorry, cvs-cur is coming in fine for me! > > > > Chris > > > > The *-fast deltas are processed differently, so it is possible that they > are not getting out, whereas the other ones are. The host that creates > the deltas is part of the University of Missouri, and they keep changing > their firewall etc stuff all the time, so for all I know, they have > found a way to block them. The problem seems to lie on my side ;-( From what I found out so far, those buggers who administer the mail servers here (if you can call the M$-crap a server at all) switched their Exchange- toys to a newer version which not only messes up the headers but also wraps lines at pos 75. Now the deltas arrive like this: CTM_MAIL BEGIN src-7.0895.gz 1 1 H4sIAGI5VksCA8VZ+28bNxL+2foreG5R2HnIfD8ctEASO70AqVs0PlyvdweBT3sRaVe3u0riHvq / 35ArPyT5IbcBzoZJaUkOZz4OZ75Zvz79YfLq+Pu3J4iOMepa/1whbQSimGBMiKFUGC5/RePR69M f 3rxHY9/PJl1v+0WHYAYfGsk50h4bE3RyRmEeXJSBGSqtY1GHEKlCSQdtVBJEU8yoEEQIzw1LQhj L Normally, they get automatically piped to ctm_rmail which can't work with this and throws them away. Now that I've switch off ctm_rmail, I can find the whole mess in my inbox... Sorry for the noise, I really didn't realise what's going here originally... Thanks, -Andre > > It is the beginning of the semester at MU, and I start my first class > tomorrow. So I might not get to it for a little while. > > In the mean time, if anyone else is not getting their emails, please > post to this group so that I have some sense of how big the problem is. > > Thanks, Stephen -- I am forced by company policy to use Micro$oft products. I am not responsible for this choice and decline any responsibility for any harm which may be caused by it. From owner-ctm-users@FreeBSD.ORG Wed Jan 20 12:04:15 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 95CC9106568F for ; Wed, 20 Jan 2010 12:04:15 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 011AC8FC17 for ; Wed, 20 Jan 2010 12:04:14 +0000 (UTC) Received: from park.js.berklix.net (p549A59BF.dip.t-dialin.net [84.154.89.191]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id o0KC4BTZ039681; Wed, 20 Jan 2010 12:04:12 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id o0KC436R029202; Wed, 20 Jan 2010 13:04:03 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id o0KC3r5E036646; Wed, 20 Jan 2010 13:03:58 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201001201203.o0KC3r5E036646@fire.js.berklix.net> To: Andre Albsmeier From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Wed, 20 Jan 2010 07:34:43 +0100." <20100120063443.GA1303@curry.mchp.siemens.de> Date: Wed, 20 Jan 2010 13:03:52 +0100 Sender: jhs@berklix.com Cc: "ctm-users@freebsd.org" Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jan 2010 12:04:15 -0000 Hi, > From: Andre Albsmeier > > The problem seems to lie on my side ;-( From what I found out so > far, those buggers who administer the mail servers here (if you > can call the M$-crap a server at all) switched their Exchange- > toys to a newer version which not only messes up the headers > but also wraps lines at pos 75. Now the deltas arrive like this: > > CTM_MAIL BEGIN src-7.0895.gz 1 1 > H4sIAGI5VksCA8VZ+28bNxL+2foreG5R2HnIfD8ctEASO70AqVs0PlyvdweBT3sRaVe3u0riHvq > / > 35ArPyT5IbcBzoZJaUkOZz4OZ75Zvz79YfLq+Pu3J4iOMepa/1whbQSimGBMiKFUGC5/RePR69M > f > 3rxHY9/PJl1v+0WHYAYfGsk50h4bE3RyRmEeXJSBGSqtY1GHEKlCSQdtVBJEU8yoEEQIzw1LQhj > L > > Normally, they get automatically piped to ctm_rmail which can't > work with this and throws them away. Now that I've switch off > ctm_rmail, I can find the whole mess in my inbox... > > Sorry for the noise, I really didn't realise what's going > here originally... > > Thanks, > > -Andre 75 seems low, considering MS addicts write extremely long lines at times (I suppose that's why - sigh). uuencode 61 fmt 65 MIME base64 72 punch cards 72 MSexchange 75 ctm_rmail 76 I guess there would be no objection if you wrote patches for: - ctm_rmail to also support receipt of smaller lines. - ctm_smail to optionally generate shorter lines. Then existing ctm recipients could first install a new ctm_rmail Then later senders could upgrade to a new ctm_smail. That would save others in future too. But good luck if you first try the quicker & more satisfying route of giving those Microsoft addicts a good berating ;-) Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text not quoted-printable, HTML or Base64 http://www.asciiribbon.org From owner-ctm-users@FreeBSD.ORG Wed Jan 20 12:22:52 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3431E106568B for ; Wed, 20 Jan 2010 12:22:52 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.freebsd.org (Postfix) with ESMTP id BE9C78FC1D for ; Wed, 20 Jan 2010 12:22:51 +0000 (UTC) Received: from mail3.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0KCMofd029250; Wed, 20 Jan 2010 13:22:50 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0KCMnvm024946; Wed, 20 Jan 2010 13:22:50 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id o0KCMnSE088945; Date: Wed, 20 Jan 2010 13:22:49 +0100 From: Andre Albsmeier To: "Julian H. Stacey" Message-ID: <20100120122249.GA10964@curry.mchp.siemens.de> References: <20100120063443.GA1303@curry.mchp.siemens.de> <201001201203.o0KC3r5E036646@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201001201203.o0KC3r5E036646@fire.js.berklix.net> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "ctm-users@freebsd.org" , "Albsmeier, Andre" Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jan 2010 12:22:52 -0000 On Wed, 20-Jan-2010 at 13:03:52 +0100, Julian H. Stacey wrote: > Hi, > > From: Andre Albsmeier > > > > The problem seems to lie on my side ;-( From what I found out so > > far, those buggers who administer the mail servers here (if you > > can call the M$-crap a server at all) switched their Exchange- > > toys to a newer version which not only messes up the headers > > but also wraps lines at pos 75. Now the deltas arrive like this: > > > > CTM_MAIL BEGIN src-7.0895.gz 1 1 > > H4sIAGI5VksCA8VZ+28bNxL+2foreG5R2HnIfD8ctEASO70AqVs0PlyvdweBT3sRaVe3u0riHvq > > / > > 35ArPyT5IbcBzoZJaUkOZz4OZ75Zvz79YfLq+Pu3J4iOMepa/1whbQSimGBMiKFUGC5/RePR69M > > f > > 3rxHY9/PJl1v+0WHYAYfGsk50h4bE3RyRmEeXJSBGSqtY1GHEKlCSQdtVBJEU8yoEEQIzw1LQhj > > L > > > > Normally, they get automatically piped to ctm_rmail which can't > > work with this and throws them away. Now that I've switch off > > ctm_rmail, I can find the whole mess in my inbox... > > > > Sorry for the noise, I really didn't realise what's going > > here originally... > > > > Thanks, > > > > -Andre > > 75 seems low, considering MS addicts write extremely long > lines at times (I suppose that's why - sigh). > > uuencode 61 > fmt 65 > MIME base64 72 > punch cards 72 > MSexchange 75 > ctm_rmail 76 As I found out now, they do not simply wrap it but convert the whole message into quoted-printable. That also adds the '=' character at the end of the line. Needless to say that they alter a signed message :-(. And they strip off the Sender: header as well... > > I guess there would be no objection if you wrote patches for: > - ctm_rmail to also support receipt of smaller lines. > - ctm_smail to optionally generate shorter lines. That would be an option. Let's see if time permits. However, I adhere to strongly to the opinion, that MTAs have no reason to touch message bodies that way. > Then existing ctm recipients could first install a new ctm_rmail > Then later senders could upgrade to a new ctm_smail. > That would save others in future too. > > But good luck if you first try the quicker & more satisfying > route of giving those Microsoft addicts a good berating ;-) I was able to find a person who at least knew what I am talking about. He even stated that he was working in the Unix world before and promised to forward the problem to the responsible staff. We'll see... -Andre > > Cheers, > Julian > -- > Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com > Mail plain text not quoted-printable, HTML or Base64 http://www.asciiribbon.org -- Amateurs like Linux, but professionals prefer FreeBSD. From owner-ctm-users@FreeBSD.ORG Thu Jan 21 00:07:37 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 697F01065672 for ; Thu, 21 Jan 2010 00:07:37 +0000 (UTC) (envelope-from smckay@internode.on.net) Received: from ipmail03.adl6.internode.on.net (ipmail03.adl6.internode.on.net [203.16.214.141]) by mx1.freebsd.org (Postfix) with ESMTP id E54598FC17 for ; Thu, 21 Jan 2010 00:07:36 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAGYmV0t20IpU/2dsb2JhbACBRtdUhDYE Received: from ppp118-208-138-84.lns20.bne1.internode.on.net (HELO dungeon.home) ([118.208.138.84]) by ipmail03.adl6.internode.on.net with ESMTP; 21 Jan 2010 10:22:16 +1030 Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.14.3/8.14.3) with ESMTP id o0KNpsh3006649; Thu, 21 Jan 2010 09:51:54 +1000 (EST) (envelope-from mckay) Message-Id: <201001202351.o0KNpsh3006649@dungeon.home> To: "Julian H. Stacey" References: <201001201203.o0KC3r5E036646@fire.js.berklix.net> In-Reply-To: <201001201203.o0KC3r5E036646@fire.js.berklix.net> from "Julian H. Stacey" at "Wed, 20 Jan 2010 13:03:52 +0100" Date: Thu, 21 Jan 2010 09:51:54 +1000 From: Stephen McKay Cc: ctm-users@freebsd.org, Andre Albsmeier , Stephen McKay Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 00:07:37 -0000 On Wednesday, 20th January 2010, "Julian H. Stacey" wrote: >75 seems low, considering MS addicts write extremely long >lines at times (I suppose that's why - sigh). > > uuencode 61 > fmt 65 > MIME base64 72 > punch cards 72 > MSexchange 75 > ctm_rmail 76 > >I guess there would be no objection if you wrote patches for: > - ctm_rmail to also support receipt of smaller lines. > - ctm_smail to optionally generate shorter lines. It would be trivial to change ctm_smail to send lines of 72 characters. It would reduce the encoding efficiency slightly, but not enough to worry about. It is not worth making it optional. I'll probably do this when I get a moment. Changing ctm_rmail to attempt to repair various mangling of the input is more difficult and unlikely to be worth the trouble. If ctm_smail is changed, only new shorter lines will show up in future messages and no mangling should occur then anyway. >> From: Andre Albsmeier >> Now the deltas arrive like this: >> >> CTM_MAIL BEGIN src-7.0895.gz 1 1 >> H4sIAGI5VksCA8VZ+28bNxL+2foreG5R2HnIfD8ctEASO70AqVs0PlyvdweBT3sRaVe3u0riHvq >> / >> 35ArPyT5IbcBzoZJaUkOZz4OZ75Zvz79YfLq+Pu3J4iOMepa/1whbQSimGBMiKFUGC5/RePR69M >> f >> 3rxHY9/PJl1v+0WHYAYfGsk50h4bE3RyRmEeXJSBGSqtY1GHEKlCSQdtVBJEU8yoEEQIzw1LQhj >> L Amusingly, this uncovered a 15 year old bug in ctm_rmail. Sorry about that. :-) The decode_line() routine has no way of reporting successful decoding with a 0 length output. The "illegal character" error is spurious. ctm_rmail: line 3: illegal character: '/' ctm_rmail: src-7.0895.gz 1/1 discarded The true error report should have been a checksum failure after the whole file had been read. However, since this is only a cosmetic error on corrupt input with no security implications (no array bounds exceeded, for example), we can leave this one. Alternatively, if people feel the need for more checking, I could add code to reject line lengths that are not a multiple of 4, and perhaps to skip blank lines. Yes? Stephen. (No, not the other Stephen!) From owner-ctm-users@FreeBSD.ORG Thu Jan 21 00:27:19 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 08F80106566C for ; Thu, 21 Jan 2010 00:27:19 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id CB0B28FC15 for ; Thu, 21 Jan 2010 00:27:18 +0000 (UTC) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id o0L0RAjg019951; Wed, 20 Jan 2010 18:27:10 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <4B579F5E.7070801@missouri.edu> Date: Wed, 20 Jan 2010 18:27:10 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100112 Firefox MIME-Version: 1.0 To: Stephen McKay References: <201001201203.o0KC3r5E036646@fire.js.berklix.net> <201001202351.o0KNpsh3006649@dungeon.home> In-Reply-To: <201001202351.o0KNpsh3006649@dungeon.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "ctm-users@freebsd.org" , "Julian H. Stacey" , Andre Albsmeier Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 00:27:19 -0000 Stephen McKay wrote: > It would be trivial to change ctm_smail to send lines of 72 characters. > It would reduce the encoding efficiency slightly, but not enough to > worry about. It is not worth making it optional. I'll probably do > this when I get a moment. This looks very easy to implement, namely change the line #define LINE_LENGTH 76 in /usr/src/usr.sbin/ctm/ctm_smail So, would there be a problem with making this start right now? (Remember I make the detlas, so I can make this happen anytime.) From owner-ctm-users@FreeBSD.ORG Thu Jan 21 00:45:47 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9E2961065695 for ; Thu, 21 Jan 2010 00:45:47 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 09E1E8FC16 for ; Thu, 21 Jan 2010 00:45:46 +0000 (UTC) Received: from park.js.berklix.net (p549A68F8.dip.t-dialin.net [84.154.104.248]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id o0L0jhpm046470; Thu, 21 Jan 2010 00:45:44 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id o0L0jZTq042689; Thu, 21 Jan 2010 01:45:36 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id o0L0jJSk038082; Thu, 21 Jan 2010 01:45:24 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201001210045.o0L0jJSk038082@fire.js.berklix.net> To: Stephen McKay From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Thu, 21 Jan 2010 09:51:54 +1000." <201001202351.o0KNpsh3006649@dungeon.home> Date: Thu, 21 Jan 2010 01:45:19 +0100 Sender: jhs@berklix.com Cc: ctm-users@freebsd.org, Andre Albsmeier Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 00:45:47 -0000 Hi, Stephen McKay wrote: > On Wednesday, 20th January 2010, "Julian H. Stacey" wrote: > > >75 seems low, considering MS addicts write extremely long > >lines at times (I suppose that's why - sigh). > > > > uuencode 61 > > fmt 65 > > MIME base64 72 > > punch cards 72 > > MSexchange 75 > > ctm_rmail 76 > > > >I guess there would be no objection if you wrote patches for: > > - ctm_rmail to also support receipt of smaller lines. > > - ctm_smail to optionally generate shorter lines. > > It would be trivial to change ctm_smail to send lines of 72 characters. > It would reduce the encoding efficiency slightly, but not enough to > worry about. It is not worth making it optional. I'll probably do > this when I get a moment. Reason I imagined it would bet better witha an option on send, & auto detect on receive: There's perhaps people out there running CTM to distribute stuff other than FreeBSD source (other *BSD src, other data, some binary systems may have limited or no access to upgrade binaries except at release upgrade. Such users might not be on this list, as this list is more for the FreeBSD patches than the programs as such. So ideally a CTM would have a format rev. no, & receivers would first be updated to dual capable auto detect of old & new format, then later senders would reduce length of CTM lines sent. > Changing ctm_rmail to attempt to repair various mangling of the input > is more difficult and unlikely to be worth the trouble. Yes. Quoted printable is evil. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text not quoted-printable, HTML or Base64 http://www.asciiribbon.org From owner-ctm-users@FreeBSD.ORG Thu Jan 21 01:09:19 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3BC64106568D for ; Thu, 21 Jan 2010 01:09:19 +0000 (UTC) (envelope-from smckay@internode.on.net) Received: from ipmail03.adl6.internode.on.net (ipmail03.adl6.internode.on.net [203.16.214.141]) by mx1.freebsd.org (Postfix) with ESMTP id B7EAA8FC08 for ; Thu, 21 Jan 2010 01:09:18 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAAY4V0t20IpU/2dsb2JhbACBRtdnhDYE Received: from ppp118-208-138-84.lns20.bne1.internode.on.net (HELO dungeon.home) ([118.208.138.84]) by ipmail03.adl6.internode.on.net with ESMTP; 21 Jan 2010 11:39:16 +1030 Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.14.3/8.14.3) with ESMTP id o0L19DpZ007399; Thu, 21 Jan 2010 11:09:13 +1000 (EST) (envelope-from mckay) Message-Id: <201001210109.o0L19DpZ007399@dungeon.home> To: "Julian H. Stacey" References: <201001210045.o0L0jJSk038082@fire.js.berklix.net> In-Reply-To: <201001210045.o0L0jJSk038082@fire.js.berklix.net> from "Julian H. Stacey" at "Thu, 21 Jan 2010 01:45:19 +0100" Date: Thu, 21 Jan 2010 11:09:13 +1000 From: Stephen McKay Cc: ctm-users@freebsd.org, Andre Albsmeier , Stephen McKay Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 01:09:19 -0000 On Thursday, 21st January 2010, "Julian H. Stacey" wrote: >Reason I imagined it would bet better with an option on send, >& auto detect on receive: > > There's perhaps people out there running CTM to distribute stuff > other than FreeBSD source (other *BSD src, other data, some binary > systems may have limited or no access to upgrade binaries except > at release upgrade. > > Such users might not be on this list, as this list is more for > the FreeBSD patches than the programs as such. So ideally a CTM > would have a format rev. no, & receivers would first be updated > to dual capable auto detect of old & new format, then later senders > would reduce length of CTM lines sent. ctm_rmail already works with any line length that is a multiple of 4. A change to 72 characters per line in ctm_smail does not require anyone to update ctm_rmail. We should just do it. It's safe. In principle a revision number is a good thing for every file and transport format, but at this late stage I doubt any benefit would be gained by adding one to the ctm email format. Stephen. From owner-ctm-users@FreeBSD.ORG Thu Jan 21 01:18:19 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4CF44106568F for ; Thu, 21 Jan 2010 01:18:18 +0000 (UTC) (envelope-from smckay@internode.on.net) Received: from ipmail03.adl6.internode.on.net (ipmail03.adl6.internode.on.net [203.16.214.141]) by mx1.freebsd.org (Postfix) with ESMTP id C705E8FC1B for ; Thu, 21 Jan 2010 01:18:17 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAAY4V0t20IpU/2dsb2JhbACBRtdnhDYEjVY Received: from ppp118-208-138-84.lns20.bne1.internode.on.net (HELO dungeon.home) ([118.208.138.84]) by ipmail03.adl6.internode.on.net with ESMTP; 21 Jan 2010 11:48:16 +1030 Received: from dungeon.home (localhost [127.0.0.1]) by dungeon.home (8.14.3/8.14.3) with ESMTP id o0L1IElB007517; Thu, 21 Jan 2010 11:18:14 +1000 (EST) (envelope-from mckay) Message-Id: <201001210118.o0L1IElB007517@dungeon.home> To: Stephen Montgomery-Smith References: <201001201203.o0KC3r5E036646@fire.js.berklix.net> <201001202351.o0KNpsh3006649@dungeon.home> <4B579F5E.7070801@missouri.edu> In-Reply-To: <4B579F5E.7070801@missouri.edu> from Stephen Montgomery-Smith at "Wed, 20 Jan 2010 18:27:10 -0600" Date: Thu, 21 Jan 2010 11:18:14 +1000 From: Stephen McKay Cc: ctm-users@freebsd.org, "Julian H. Stacey" , Andre Albsmeier , Stephen McKay Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 01:18:19 -0000 On Wednesday, 20th January 2010, Stephen Montgomery-Smith wrote: >Stephen McKay wrote: > >> It would be trivial to change ctm_smail to send lines of 72 characters. >> It would reduce the encoding efficiency slightly, but not enough to >> worry about. It is not worth making it optional. I'll probably do >> this when I get a moment. > >This looks very easy to implement, namely change the line >#define LINE_LENGTH 76 >in /usr/src/usr.sbin/ctm/ctm_smail Yes. Multiples of 4 only. >So, would there be a problem with making this start right now? >(Remember I make the deltas, so I can make this happen anytime.) Righto. I've changed my local copy from 76 to 72 and did a small test run. Works for me. I'll update the official source when I get a chance. A cautious person would do their own test run, of course. :-) Stephen. From owner-ctm-users@FreeBSD.ORG Thu Jan 21 01:32:04 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D12791065679 for ; Thu, 21 Jan 2010 01:32:04 +0000 (UTC) (envelope-from stephen@missouri.edu) Received: from cauchy.math.missouri.edu (cauchy.math.missouri.edu [128.206.184.213]) by mx1.freebsd.org (Postfix) with ESMTP id 9D9ED8FC1F for ; Thu, 21 Jan 2010 01:32:04 +0000 (UTC) Received: from laptop3.gateway.2wire.net (cauchy.math.missouri.edu [128.206.184.213]) by cauchy.math.missouri.edu (8.14.3/8.14.3) with ESMTP id o0L1VugI020575; Wed, 20 Jan 2010 19:31:57 -0600 (CST) (envelope-from stephen@missouri.edu) Message-ID: <4B57AE8C.4070003@missouri.edu> Date: Wed, 20 Jan 2010 19:31:56 -0600 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.7) Gecko/20100112 Firefox MIME-Version: 1.0 To: Stephen McKay References: <201001201203.o0KC3r5E036646@fire.js.berklix.net> <201001202351.o0KNpsh3006649@dungeon.home> <4B579F5E.7070801@missouri.edu> <201001210118.o0L1IElB007517@dungeon.home> In-Reply-To: <201001210118.o0L1IElB007517@dungeon.home> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "ctm-users@freebsd.org" , "Julian H. Stacey" , Andre Albsmeier Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 01:32:04 -0000 Stephen McKay wrote: > On Wednesday, 20th January 2010, Stephen Montgomery-Smith wrote: > >> Stephen McKay wrote: >> >>> It would be trivial to change ctm_smail to send lines of 72 characters. >>> It would reduce the encoding efficiency slightly, but not enough to >>> worry about. It is not worth making it optional. I'll probably do >>> this when I get a moment. >> >> This looks very easy to implement, namely change the line >> #define LINE_LENGTH 76 >> in /usr/src/usr.sbin/ctm/ctm_smail > > Yes. Multiples of 4 only. > >> So, would there be a problem with making this start right now? >> (Remember I make the deltas, so I can make this happen anytime.) > > Righto. I've changed my local copy from 76 to 72 and did a small test > run. Works for me. I'll update the official source when I get a chance. > > A cautious person would do their own test run, of course. :-) I have made the change. The next ctm generation starts 10pm CST. Can people tell me if there are problems? I must admit to not being cautious, but the worst that will happen is that people will need to download those deltas from the ftp sites. From owner-ctm-users@FreeBSD.ORG Thu Jan 21 01:55:34 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9F7DC106566B for ; Thu, 21 Jan 2010 01:55:34 +0000 (UTC) (envelope-from jhs@berklix.com) Received: from tower.berklix.org (tower.berklix.org [83.236.223.114]) by mx1.freebsd.org (Postfix) with ESMTP id 105AC8FC0A for ; Thu, 21 Jan 2010 01:55:33 +0000 (UTC) Received: from park.js.berklix.net (p549A68F8.dip.t-dialin.net [84.154.104.248]) (authenticated bits=0) by tower.berklix.org (8.14.2/8.14.2) with ESMTP id o0L1tVFK047001; Thu, 21 Jan 2010 01:55:32 GMT (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41]) by park.js.berklix.net (8.13.8/8.13.8) with ESMTP id o0L1tPbw043072; Thu, 21 Jan 2010 02:55:25 +0100 (CET) (envelope-from jhs@berklix.com) Received: from fire.js.berklix.net (localhost [127.0.0.1]) by fire.js.berklix.net (8.14.3/8.14.3) with ESMTP id o0L1t4eI098170; Thu, 21 Jan 2010 02:55:10 +0100 (CET) (envelope-from jhs@fire.js.berklix.net) Message-Id: <201001210155.o0L1t4eI098170@fire.js.berklix.net> To: Stephen McKay From: "Julian H. Stacey" Organization: http://www.berklix.com BSD Unix Linux Consultancy, Munich Germany User-agent: EXMH on FreeBSD http://www.berklix.com/free/ X-URL: http://www.berklix.com In-reply-to: Your message "Thu, 21 Jan 2010 11:09:13 +1000." <201001210109.o0L19DpZ007399@dungeon.home> Date: Thu, 21 Jan 2010 02:55:04 +0100 Sender: jhs@berklix.com Cc: ctm-users@freebsd.org, Andre Albsmeier Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 01:55:34 -0000 Stephen McKay wrote: > On Thursday, 21st January 2010, "Julian H. Stacey" wrote: > > >Reason I imagined it would bet better with an option on send, > >& auto detect on receive: > > > > There's perhaps people out there running CTM to distribute stuff > > other than FreeBSD source (other *BSD src, other data, some binary > > systems may have limited or no access to upgrade binaries except > > at release upgrade. > > > > Such users might not be on this list, as this list is more for > > the FreeBSD patches than the programs as such. So ideally a CTM > > would have a format rev. no, & receivers would first be updated > > to dual capable auto detect of old & new format, then later senders > > would reduce length of CTM lines sent. > > ctm_rmail already works with any line length that is a multiple of 4. > A change to 72 characters per line in ctm_smail does not require anyone > to update ctm_rmail. We should just do it. It's safe. Nice. > In principle a revision number is a good thing for every file and > transport format, but at this late stage I doubt any benefit would > be gained by adding one to the ctm email format. OK. Stephen Montgomery-Smith wrote: > This looks very easy to implement, namely change the line > #define LINE_LENGTH 76 > in /usr/src/usr.sbin/ctm/ctm_smail > > So, would there be a problem with making this start right now? > > (Remember I make the detlas, so I can make this happen anytime.) Sounds like you'd be safe to try it then :-) /usr/src/usr.sbin/ctm/ctm_smail/ctm_smail.c #define LINE_LENGTH 72 Should solve Andre's chopped sample he posted that folded after 75. [Speaking as one end consumer], I'd be happy if you tried. Andre may also need to get get his admins to turn off their conversion to "quoted printable... Or If he can't, I think there's a way in sendmail on local receive to convert "quoted printable" back to straight 8 bit ?, (I've been meaning to find time to look as I get "quoted printable" text mail from MS using friends that's a pain to edit with vi). Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail plain text not quoted-printable, HTML or Base64 http://www.asciiribbon.org From owner-ctm-users@FreeBSD.ORG Thu Jan 21 06:37:38 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 424D6106568F for ; Thu, 21 Jan 2010 06:37:38 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx1.freebsd.org (Postfix) with ESMTP id CAD8E8FC14 for ; Thu, 21 Jan 2010 06:37:37 +0000 (UTC) Received: from mail3.siemens.de (localhost [127.0.0.1]) by david.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0L6bZiU020949; Thu, 21 Jan 2010 07:37:35 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0L6bZ7f007983; Thu, 21 Jan 2010 07:37:35 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id o0L6bYk2093072; Date: Thu, 21 Jan 2010 07:37:34 +0100 From: Andre Albsmeier To: "Julian H. Stacey" Message-ID: <20100121063734.GA14765@curry.mchp.siemens.de> References: <201001210109.o0L19DpZ007399@dungeon.home> <201001210155.o0L1t4eI098170@fire.js.berklix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201001210155.o0L1t4eI098170@fire.js.berklix.net> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "ctm-users@freebsd.org" , "Albsmeier, Andre" , Stephen McKay Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 06:37:38 -0000 On Thu, 21-Jan-2010 at 02:55:04 +0100, Julian H. Stacey wrote: > Stephen McKay wrote: > > On Thursday, 21st January 2010, "Julian H. Stacey" wrote: > > > > >Reason I imagined it would bet better with an option on send, > > >& auto detect on receive: > > > > > > There's perhaps people out there running CTM to distribute stuff > > > other than FreeBSD source (other *BSD src, other data, some binary > > > systems may have limited or no access to upgrade binaries except > > > at release upgrade. > > > > > > Such users might not be on this list, as this list is more for > > > the FreeBSD patches than the programs as such. So ideally a CTM > > > would have a format rev. no, & receivers would first be updated > > > to dual capable auto detect of old & new format, then later senders > > > would reduce length of CTM lines sent. > > > > ctm_rmail already works with any line length that is a multiple of 4. > > A change to 72 characters per line in ctm_smail does not require anyone > > to update ctm_rmail. We should just do it. It's safe. > > Nice. > > > In principle a revision number is a good thing for every file and > > transport format, but at this late stage I doubt any benefit would > > be gained by adding one to the ctm email format. > > OK. > > > Stephen Montgomery-Smith wrote: > > > This looks very easy to implement, namely change the line > > #define LINE_LENGTH 76 > > in /usr/src/usr.sbin/ctm/ctm_smail > > > > So, would there be a problem with making this start right now? > > > > (Remember I make the detlas, so I can make this happen anytime.) > > Sounds like you'd be safe to try it then :-) > /usr/src/usr.sbin/ctm/ctm_smail/ctm_smail.c > #define LINE_LENGTH 72 > Should solve Andre's chopped sample he posted that folded after 75. > [Speaking as one end consumer], I'd be happy if you tried. I will come back with my results as soon as I get the first delta with 72 chars/line ;-). > > Andre may also need to get get his admins to turn off their conversion > to "quoted printable... Or The guy I was talking to about this problem confirmed that, at least in his opinion, there was absolutely no reason to change the body of the message. He promised me to talk to his people working currently on this Exchange server upgrade. However, you never know when some of those dressed up business babblers jump in here and insist on doing it "The Default Mickeysoft Way" since this is how it has always been... > If he can't, I think there's a way in sendmail on local receive to > convert "quoted printable" back to straight 8 bit ?, (I've been > meaning to find time to look as I get "quoted printable" text mail > from MS using friends that's a pain to edit with vi). Hmm, I think this would be generally a good idea, thanks for reminding me. I remember a time many years ago when sendmail did some type of similar conversion per default (I saw it in the log files). Thanks, -Andre > > Cheers, > Julian > -- > Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com > Mail plain text not quoted-printable, HTML or Base64 http://www.asciiribbon.org -- Note: No Micro$oft programs were used in the creation or distribution of this message. If you are using a Micro$oft program to view or forward this message, be forewarned that I am not responsible for any harm you may encounter as a result. From owner-ctm-users@FreeBSD.ORG Thu Jan 21 06:48:23 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 998D81065697 for ; Thu, 21 Jan 2010 06:48:23 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by mx1.freebsd.org (Postfix) with ESMTP id 2BD878FC28 for ; Thu, 21 Jan 2010 06:48:22 +0000 (UTC) Received: from mail1.siemens.de (localhost [127.0.0.1]) by david.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0L6mLh8025749; Thu, 21 Jan 2010 07:48:21 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail1.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0L6mLZW008056; Thu, 21 Jan 2010 07:48:21 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id o0L6mLTJ093105; Date: Thu, 21 Jan 2010 07:48:20 +0100 From: Andre Albsmeier To: Stephen Montgomery-Smith Message-ID: <20100121064820.GB14765@curry.mchp.siemens.de> References: <201001201203.o0KC3r5E036646@fire.js.berklix.net> <201001202351.o0KNpsh3006649@dungeon.home> <4B579F5E.7070801@missouri.edu> <201001210118.o0L1IElB007517@dungeon.home> <4B57AE8C.4070003@missouri.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B57AE8C.4070003@missouri.edu> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "ctm-users@freebsd.org" , "Julian H. Stacey" , "Albsmeier, Andre" , Stephen McKay Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 06:48:23 -0000 On Thu, 21-Jan-2010 at 02:31:56 +0100, Stephen Montgomery-Smith wrote: > Stephen McKay wrote: > > On Wednesday, 20th January 2010, Stephen Montgomery-Smith wrote: > > > >> Stephen McKay wrote: > >> > >>> It would be trivial to change ctm_smail to send lines of 72 characters. > >>> It would reduce the encoding efficiency slightly, but not enough to > >>> worry about. It is not worth making it optional. I'll probably do > >>> this when I get a moment. > >> > >> This looks very easy to implement, namely change the line > >> #define LINE_LENGTH 76 > >> in /usr/src/usr.sbin/ctm/ctm_smail > > > > Yes. Multiples of 4 only. > > > >> So, would there be a problem with making this start right now? > >> (Remember I make the deltas, so I can make this happen anytime.) > > > > Righto. I've changed my local copy from 76 to 72 and did a small test > > run. Works for me. I'll update the official source when I get a chance. > > > > A cautious person would do their own test run, of course. :-) > > I have made the change. The next ctm generation starts 10pm CST. Can > people tell me if there are problems? I must admit to not being > cautious, but the worst that will happen is that people will need to > download those deltas from the ftp sites. Thanks a lot for this, I'll report results as soon as I get the first delta. From my past experience, the 10 p.m. CST delta should arrive here at around 8 UTC... However, I wonder what comes next: Will we have to add CRs to the end of each line? Will we have to import each delta into Microshaft's Powerjoint first since this is the only thing Exchange 2012 will deliver? Thanks again, -Andre -- Division by zero error -- multiplying by zero to recover... From owner-ctm-users@FreeBSD.ORG Thu Jan 21 10:36:23 2010 Return-Path: Delivered-To: ctm-users@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04615106566B for ; Thu, 21 Jan 2010 10:36:23 +0000 (UTC) (envelope-from Andre.Albsmeier@siemens.com) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.freebsd.org (Postfix) with ESMTP id 8B9078FC20 for ; Thu, 21 Jan 2010 10:36:22 +0000 (UTC) Received: from mail3.siemens.de (localhost [127.0.0.1]) by goliath.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0LAaJ6e023688; Thu, 21 Jan 2010 11:36:19 +0100 Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.40.130]) by mail3.siemens.de (8.12.11.20060308/8.12.11) with ESMTP id o0LAaJM0001461; Thu, 21 Jan 2010 11:36:19 +0100 Received: (from localhost) by curry.mchp.siemens.de (8.14.3/8.14.3) id o0LAaJ17094230; Date: Thu, 21 Jan 2010 11:36:18 +0100 From: Andre Albsmeier To: Stephen Montgomery-Smith Message-ID: <20100121103618.GA25915@curry.mchp.siemens.de> References: <201001201203.o0KC3r5E036646@fire.js.berklix.net> <201001202351.o0KNpsh3006649@dungeon.home> <4B579F5E.7070801@missouri.edu> <201001210118.o0L1IElB007517@dungeon.home> <4B57AE8C.4070003@missouri.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B57AE8C.4070003@missouri.edu> X-Echelon: X-Advice: Drop that crappy M$-Outlook, I'm tired of your viruses! User-Agent: Mutt/1.5.20 (2009-06-14) Cc: "ctm-users@freebsd.org" , "Julian H. Stacey" , "Albsmeier, Andre" , Stephen McKay Subject: Re: No deltas via email anymore? X-BeenThere: ctm-users@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CTM User discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jan 2010 10:36:23 -0000 On Thu, 21-Jan-2010 at 02:31:56 +0100, Stephen Montgomery-Smith wrote: > Stephen McKay wrote: > > On Wednesday, 20th January 2010, Stephen Montgomery-Smith wrote: > > > >> Stephen McKay wrote: > >> > >>> It would be trivial to change ctm_smail to send lines of 72 characters. > >>> It would reduce the encoding efficiency slightly, but not enough to > >>> worry about. It is not worth making it optional. I'll probably do > >>> this when I get a moment. > >> > >> This looks very easy to implement, namely change the line > >> #define LINE_LENGTH 76 > >> in /usr/src/usr.sbin/ctm/ctm_smail > > > > Yes. Multiples of 4 only. > > > >> So, would there be a problem with making this start right now? > >> (Remember I make the deltas, so I can make this happen anytime.) > > > > Righto. I've changed my local copy from 76 to 72 and did a small test > > run. Works for me. I'll update the official source when I get a chance. > > > > A cautious person would do their own test run, of course. :-) > > I have made the change. The next ctm generation starts 10pm CST. Can > people tell me if there are problems? I must admit to not being > cautious, but the worst that will happen is that people will need to > download those deltas from the ftp sites. src-7.0897.gz came in here at 7:48 UTC. It was of course, according to the headers, still converted to quoted-printable but, since there were never any 8bit chars and the line length was 72, no conversion was actually done. I could directly feed it to ctm_rmail and all went fine ;-). Let's see how things develop with further deltas but, if those M$ morons don't play with there knobs again, things should be fine. Thanks a lot, -Andre