Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU |
On Fri, 21 Feb 1997, Robert Luoma wrote: > > Is the mailer broken on blue? Nope. This is one of the infamouse Microsoft Mail bugs. The address "jduksta at ltnpo1.xyplex.com" does not exist, and from what I see in the mail headers, this is a MSMAIL server. MSMAIL ignores the proper headers for sending errors, and just blindly assumes the FROM address is the place to send errors. Microsoft refuses to acknowledge the bug, claiming that each component of MSMAIL, when examined separately, complies with the RFCs. According to their interpretation, the headers that define the errors-to address are stripped out of the message by the MSMAIL server before being delivered to the end user mailbox, which they feel is OK; and when the end user replies, those headers are not there, and therefore the behavior is compliant. Unfortunately, there is no solution to this problem other than encouraging end users to throw away MSMAIL and use a real mail system. > ------- Forwarded Message > > Return-Path: MAILER-DAEMON at pioneer.ci.net > Return-Path: MAILER-DAEMON at pioneer.ci.net > Received: by smtpgate.xyplex.com with Microsoft Mail > id <330CE616 at smtpgate.xyplex.com>; Thu, 20 Feb 97 16:02:30 PST > From: POSTMASTER at xap.xyplex.com > Subject: Mail failure > Date: Thu, 20 Feb 97 15:53:00 PST > Message-ID: <330CE616 at smtpgate.xyplex.com> > Encoding: 55 TEXT > X-Mailer: Microsoft Mail V3.0 > > > [002] Mail was received for unknown addresses. > Message was not delivered to > LITTLETON1/LTNPO1/jduksta (LITTLETON1/LTNPO1/jduksta) > > - ------------------------------------------------------------------------------ > Return-Path: <owner-discuss at tarnhelm.blu.org> > Received: from xyplex.com by smtpgate.xyplex.com id > <330CE34A at smtpgate.xyplex.com>; Thu, 20 Feb 97 15:50:34 PST > Received: from clavin.xyplex.com (clavin.xyplex.com [140.179.254.150]) by > xyplex.com (8.8.5/8.7.3) with SMTP id PAA23307 for > <jduksta at ltnpo1.xyplex.com>; Thu, 20 Feb 1997 15:23:36 -0500 (EST) > Received: from by clavin.xyplex.com (4.1/pfc-1-Oct-1995) id AB04063; Thu, 20 > Feb 97 15:23:53 EST > Received: (from majordomo at localhost) by blu.org (8.7.6/8.7.3) id UAA22803 for > discuss-outgoing; Sat, 15 Feb 1997 20:06:15 -0500 > Received: from toto.pn.com (toto.pn.com [205.136.64.8]) by blu.org > (8.7.6/8.7.3) with ESMTP id UAA22797 for <linux-sig at tarnhelm.blu.org>; > Sat, 15 Feb 1997 20:06:13 -0500 > Received: from pioneer.ci.net (pioneer.ci.net [205.136.67.65]) by toto.pn.com > (8.7.5) with ESMTP id TAA09915 for <linux-sig at tarnhelm.blu.org>; Sat, 15 > Feb 1997 19:56:55 -0500 (EST) > Received: (from Ucapybara at localhost) by pioneer.ci.net (8.8.2/8.8.0) with UUCP > id TAA18534 for linux-sig at tarnhelm.blu.org; Sat, 15 Feb 1997 19:55:26 > -0500 > X-Authentication-Warning: pioneer.ci.net: Ucapybara set sender to > Received: from capybara.pn.com (localhost [127.0.0.1]) by capybara.pn.com > (8.7.6/8.7.3) with ESMTP id TAA01274; Sat, 15 Feb 1997 19:30:06 -0500 > Message-Id: <199702160030.TAA01274 at capybara.pn.com> > To: linux-sig at tarnhelm.blu.org > Subject: mgetty with fax HOWTO? > Date: Sat, 15 Feb 1997 19:30:06 -0500 > Sender: owner-discuss at tarnhelm.blu.org > Precedence: bulk > Reply-To: discuss at tarnhelm.blu.org > > > I cannot get mgetty to accept faxes, > even though "fax answer" works in its > place in /etc/inittab > > I get the dreaded FCON (sp?) errors... > > Has anyone gotten this program to work > while both data dial-in and FAX > > I am using the Practical Peripherals 28.8 FAX/modem > > (data dial-in works just fine) > > - -- > > ------- End of Forwarded Message > -- John Abreau :: Unix Systems Administrator :: jabr at necx.com NECX :: 4 Technology Drive :: Peabody, MA 01960 :: 508-538-8425 Executive Director, Boston Linux & Unix - jabr at blu.org - http://www.blu.org
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |