LSTSRV-L Archives

LISTSERV Site Administrators' Forum

LSTSRV-L

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Fergal Suipeil <[log in to unmask]>
Fri, 17 Apr 1998 20:04:20 +0100
TEXT/PLAIN (109 lines)
Hi,

It looks as if the distribution jobs for IO-MUG which arrive at
listserv.hea.ie don't include [log in to unmask] in the list
of recipients. They do include other addresses in the .ie domain.
Also jt.thompson is subscribed to other lists which listserv.hea.ie
does deliver successfully, so I doubt there's a problem between
HEAnet and Indigo, or indeed with Indigo's MX hosts.

The distribution jobs for IO-MUG arrive at listserv.hea.ie from
segate.sunet.se. I'd suspect a problem at UTA or between UTA and
SEGATE.

One possibility is that UTA, SEGATE or something inbetween is routing
messages for indigo.ie somewhere other than listserv.hea.ie. This
would explain why the other .ie subscribers on IO-MUG still work.

By the way, I don't have responsibility for listserv.hea.ie (anymore).
I just happen to know where the logs are kept.
                                                     Fergal.



On Fri, 17 Apr 1998, Pete Weiss wrote:

> My guess is that subscribers in the INDIGO.IE domain receive
> distributions via the LISRTSERV backbone site LISTSERV.HEA.IE and won't
> show up in your SMTP logs per se.
>
> Also there are 4 mail exchangers for that hostname with at least 5 (and
> possibly more) Domain Name Services for those MX hosts.  This leaves some
> latitude for mis-configured, out-of-sync MX or DNS:
>
>
> Query:Mail Exchange (MX):indigo.ie
> indigo.ie       MX      10      una.indigo.ie
> indigo.ie       MX      50      smtpmail2.xensei.com
> indigo.ie       MX      5       mail.indigo.ie
> indigo.ie       MX      10      ann.indigo.ie
> indigo.ie       NS      nessa.indigo.ie
> indigo.ie       NS      owl.nstn.ca
> indigo.ie       NS      ann.indigo.ie
> indigo.ie       NS      una.indigo.ie
> indigo.ie       NS      ns2.xensei.com
> una.indigo.ie   A       194.125.133.11
> mail.indigo.ie  A       194.125.133.225
> mail.indigo.ie  A       194.125.133.226
> mail.indigo.ie  A       194.125.133.227
> ann.indigo.ie   A       194.125.133.10
> nessa.indigo.ie A       194.125.133.10
> owl.nstn.ca     A       137.186.128.11
> ns2.xensei.com  A       198.151.175.4
> Complete: indigo.ie
>
> Nevertheless, the highest precedence MX is available:
>
> 220 relay02.indigo.ie ESMTP
> help
> 214-qmail home page: http://pobox.com/~djb/qmail.html
> 214 send comments to [log in to unmask]
> expn postmaster
> 502 unimplemented (#5.5.1)
> vrfy postmaster
> 252 send some mail, i'll try my best
>
> --
>
>
> BTW, [log in to unmask] does seem to be working and able to process
> commands:
>
> Return-Path: <>
> Received: from PSUVM (NJE origin SMTP@PSUVM) by PSUVM.PSU.EDU (LMail
>           V1.2c/1.8c) with BSMTP id 4544; Fri, 17 Apr 1998 11:37:44 -0400
> Received: from listserv.hea.ie (193.1.198.5,2586) by PSUVM.PSU.EDU
>    (IBM VM SMTP V2R2) with TCP; Fri, 17 Apr 98 11:37:42 EST
> Received: from listserv.hea.ie (listserv.heanet.ie [193.1.198.5])
>         by listserv.hea.ie (8.8.5/8.8.5) with ESMTP id QAA26892
>         for <[log in to unmask]>; Fri, 17 Apr 1998 16:42:15 +0100 (BST)
> Message-Id: <[log in to unmask]>
> Date:         Fri, 17 Apr 1998 16:42:15 +0100
> From: "L-Soft list server at HEAnet (1.8c)" <[log in to unmask]>
> Subject:      Output of your job "PMW1"
> To: [log in to unmask]
>
> > thanks
> You're welcome!
> --
>
> Thus you should probably mailto:[log in to unmask] as well as
> the POSTMASTERs.
>
> /Pete
> --
>
> |Subscription options for Jt Thompson <[log in to unmask]>, list IOMUG:
> |
> |MAIL           You are sent individual postings as they are received
> |FULLHDR        Full (normal) mail headers (formerly "FULLBSMTP")
> |REPRO          You receive a copy of your own postings
> |NOACK          No acknowledgement of successfully processed postings
> |
> |I get the same response when I query subscribers who are getting postings.
> |At first, I thought there might be something screwy with the address that
> |prevented delivery, but the log does not show her as being one of the
> |recipients being sent mail when a post to the list is processed.  Does
> |anyone have any clues as to what might be the problem?
>

ATOM RSS1 RSS2