Return-Path: owner-postman Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.3/8.6.3) with SMTP id OAA05828 for postgres-dist; Tue, 2 Nov 1993 14:58:58 -0800 Resent-From: POSTGRES mailing list Resent-Message-Id: <199311022258.OAA05828@nobozo.CS.Berkeley.EDU> Sender: owner-postman@postgres.Berkeley.EDU X-Return-Path: owner-postman Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.3/8.6.3) with SMTP id OAA05819 for postgres@postgres.Berkeley.EDU; Tue, 2 Nov 1993 14:58:57 -0800 Message-Id: <199311022258.OAA05819@nobozo.CS.Berkeley.EDU> X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost didn't use HELO protocol From: aoki@postgres.Berkeley.EDU (Paul M. Aoki) To: postgres@postgres.Berkeley.EDU Subject: fun with mail Date: Tue, 02 Nov 93 14:58:57 -0800 X-Sender: aoki@postgres.Berkeley.EDU Resent-To: postgres-dist@postgres.Berkeley.EDU X-Mts: smtp Resent-Date: Tue, 02 Nov 93 14:58:58 -0800 Resent-XMts: smtp (ok, let's try this again..) well, the new mail server configuration seems to be pretty stable at this point. the swedish guys fixed their gateway software (we also added a filter to catch this kind of thing at our end). it was unfortunate that both of these events occurred in the same morning -- it was very difficult to *do* anything about it while the machines were going up and down -- but these things happen, and things seem to be ok now. if you are *still* undergoing, as one person colorfully put it, "the unrelenting torture of seeing past messages repeated incessantly" (where "incessantly" is defined as more than a dozen-odd duplicate messages of any kind over the last day, which is what i received) let me know (i.e., do not send mail to the postgres mailing list). as far as i can tell our mail queues are empty.. -- Paul M. Aoki | CS Div., Dept. of EECS, UCB | aoki@postgres.Berkeley.EDU | Berkeley, CA 94720 | ...!uunet!ucbvax!aoki