T.R | Title | User | Personal Name | Date | Lines |
---|
3119.1 | Possibly misled by event's text? | ZUR01::ASHG | Grahame Ash @RLE | Mon Jan 27 1997 12:17 | 14 |
| The AltaVista Notes search utility found 2 more notes with this event in -
2524, 2663. In both cases it was associated with problems with peer MTAs i.e.
the MTA had tried to send the message, and failed.
I think I was confused by the use of the word "Routing" in the event. I've
always associated this with the MTA attempting to determine the eventual
route from the MTS info - following redirections etc. It seems that the
redirection here may well be irrelevant to the problem. It may have been
clearer if the events said "Sending" or "Relaying" instead. Just an opinion.
Meanwhile, I'll ask the customer to check for other events previous to this
one.
grahame
|
3119.2 | Doesn't appear to be the network | ZUR01::ASHG | Grahame Ash @RLE | Mon Jan 27 1997 15:05 | 12 |
| Having looked through a few recent event files, it seems that:
- this event occurs every day, several times, for different recipients and
domains
- it is not generally preceded by evidence of a network problem.
Any other theory?
Thanks,
grahame
|
3119.3 | More info, no closer | ZUR01::ASHG | Grahame Ash @RLE | Tue Jan 28 1997 11:51 | 22 |
| I've now looked at a whole day's event file and gathered some more info -
which doen't help me at all!
There are 3 similar Invalid MPDU events:
- Transfer Attempts limit reached
This occurred after peer mta events showed connection problems
- Delivery Attempts limit reached
This occurred after the SMTP Gateway had failed on 4 attempts
(Internal Error) at fetching a message
- Routing attempts limit reached
This is the problem one, and it appears out of the blue. I've also now
discovered that it can happen for addresses which are not redirected.
I'd appreciate any explanation of why the MTA would issue this particular
event.
Thanks,
grahame
|
3119.4 | | ZUR01::ASHG | Grahame Ash @RLE | Tue Feb 04 1997 13:18 | 12 |
| > - Routing attempts limit reached
> This is the problem one, and it appears out of the blue. I've also now
>discovered that it can happen for addresses which are not redirected.
>
>I'd appreciate any explanation of why the MTA would issue this particular
>event.
Anyone had a few minutes to look into this for me?
Thanks,
grahame
|
3119.5 | IPMT ZUO101103 CFS.48825,Sev: 2 | ZUR01::ASHG | Grahame Ash @RLE | Fri Feb 14 1997 08:13 | 0
|