Linux what is dead letter

unixforum.org

Форум для пользователей UNIX-подобных систем

• Темы без ответов
• Активные темы
• Поиск
• Статус форума

Dead.letter (Что это и чего оно хочет?)

Модератор: SLEDopit

Dead.letter

Сообщение SODIX » 27.02.2007 17:20

Пересмотрел матрицу и все встало на свои места. There is no spoon.

Re: Dead.letter

Сообщение serzh-z » 27.02.2007 17:39

Re: Dead.letter

Сообщение SODIX » 27.02.2007 17:43

Пересмотрел матрицу и все встало на свои места. There is no spoon.

Re: Dead.letter

Сообщение serzh-z » 27.02.2007 17:48

Если есть желание, то можно полазить по Mandriva Control Center и найти что-то подобное Security Manager/test/checker или прочее и отключить. У кого есть Мандрива — думаю, что точнее укажут, где именно.

Либо же разобрать с тем почему сообщение не дошло жо адресата. Т.е. проверить псевдонимы в /etc/*/alias, проверить настройки SMTP-сервера, который рассылает локальную почту. Установить его, если он не установлен.

Re: Dead.letter

Сообщение SODIX » 27.02.2007 17:51

Пересмотрел матрицу и все встало на свои места. There is no spoon.

Re: Dead.letter

Сообщение SODIX » 27.02.2007 18:09

Ага,спасиб

А,на безопасности системы это может отразиться?

Пересмотрел матрицу и все встало на свои места. There is no spoon.

Re: Dead.letter

Сообщение xnu!l » 27.02.2007 20:31

Эта утилита , если мне не изменяет память называется msec. Она прогоняется по крону раз в день и проверяет изменения в состоянии открытых портов, установленных суид-битов и т.д.
Отчеты должны быть в /var/log/security и /var/log/security.log
Копия отчетов отправляется ввиде email , оттуда у вас и появлялся dead.letter

Re: Dead.letter

Сообщение SODIX » 27.02.2007 20:57

А вообще это нормально,или стоит ченить подправить?

Пересмотрел матрицу и все встало на свои места. There is no spoon.

Источник

IBM WAS/MQ/MB/DATAPOWER Administration Training

Become An Expert Here

Wednesday, 3 April 2013

What Is Dead Letter Queue & Dead Letter Handler

Dead Letter Queue (DLQ)

— When messages can not be delivered to the intended queue, the messages may be delivered to a Dead Letter Queue (DLQ) if the queue manager has one defined.

— By default a queue manager does not have a Dead Letter Queue but you should define one for every queue manager.

— In every Queue Manager default dead letter queue is SYSTEM.DEAD.LETTER.QUEUE.

Dead Letter Messages

1) Messages can be placed on the DLQ by the queue manager, the channels (MCA) or by applications
2) When the messages are put onto DLQ, they should have a Dead Letter Header (DLH). DLH will be generated by Queue manager and MCA.
3) If application are putting the messages onto DLQ, applications must create the Dead Letter Header (DLH) to message.

Dead Letter Queue Handler

Once a message arrives on the DLQ you can automate the handling of that message using the DLQ handler program. You can have the handler running and waiting for messages to arrive on the DLQ or you can set up the DLQ to trigger the start of the handler program

Starting the DLQ Handler
You can start the DLQ handler using the RUNMQDLQ command.
Example: RUNMQDLQ -Q -M Sample Program

Websphere MQ supplies a sample program called amqsdlq which provides similar function as runmqdlq. This allows users to customize the way messages are handled from the DLQ, especially useful if you have applications placing messages directly onto DLQ.

How to write Rules in rule table explained
Rule table is looks something like: Pattern/Keyword Action. ( simillat to find a particular keyword and the do the action specified)

Pattern Keywords – allow you to match only certain messages on the DLQ
Ex: REASON – match only messages with a specified reason code

Action Keywords describe how a matching message is processed
ACTION(DISCARD|IGNORE|RETRY|FWD)
FWDQ – name of queue where message is forwarded
FWDQM – name of qmgr where message is forwarded
HEADER(YES|NO) – do messages have DLH header
PUTAUT(DEF|CTX) – userid of runmqdlq program or userid from the MD of the message on the DLQ
RETRY – number of times to retry each matching rule

More about Rule Table
1) A rules table must contain at least one rule.
2) Keywords can occur in any order.
3) A keyword can be included only once in any rule.
4) Keywords are not case-sensitive.
5) A keyword and its parameter value must be separated from other keywords by at least one blank space or comma.
6) There can be any number of blanks at the beginning or end of a rule, and between keywords, punctuation, and values.
7) Each rule must begin on a new line.
8) For reasons of portability, the significant length of a line must not be greater than 72 characters.

Sample Rule Table
***************************************************
* An example rules table for the runmqdlq command *
***************************************************
* Control data entry
* ——————
* If parameters are not supplied on the runmqdlq command use
* SYSTEM.DEAD.LETTER.QUEUE as the input queue, use QM1_TEST as the
* queue manager and set retry interval to 20 seconds
inputq(‘SYSTEM.DEAD.LETTER.QUEUE’) inputqm(‘QM1_TEST’) retryint(20)

* Rules entries
* ——
* Include a rule with ACTION (RETRY) first to try to deliver the
* message to the intended destination. If a message is placed on the
* DLQ because its destination queue is full, attempt to forward the
* message to its destination queue. Make 5 attempts at approximately
* 20 second intervals (the default value for RETRYINT). Also include
* the «+» just to show how to wrap a command over to the next line.
REASON(MQRC_Q_FULL) ACTION(RETRY) RETRY(5)
* If a message is placed on the DLQ due to put inhibited, attempt to
* forward the message to its destination queue. Make 5 attempts at
* approximately 20 second intervals (the default value for RETRYINT).
REASON(MQRC_PUT_INHIBITED) ACTION(RETRY) RETRY(5)
* Include a rule to handle messages which do not match any of the
* patterns specified above. Send the messages to another queue named
* DEADQ where they can be handled later.
ACTION(FWD) FWDQ(‘DEADQ’)

Runmqdlq examples
If you use the DLQ handler without redirecting stdin from a file (the rules table), the DLQ handler reads its input from the keyboard.
In WebSphere MQ for AIX, Solaris, HP-UX, and Linux, the DLQ handler does not start to process the named queue until it receives an end_of_file (Ctrl+D) character.
In WebSphere MQ for Windows it does not start to process the named queue until you press the following sequence of keys: Ctrl+Z, Enter, Ctrl+Z, Enter

Источник

Emergency UNIX and Linux Support

Send mail from dead.letter

Hi,
Can someone pls tell me how do i mail the contents of my dead.letter to my mail id. The problem is that the content is a multi-part message in MIME format. How do i get the original message mailed to me.

i used uuencode, but that does not work, says «uuencode not found»

Any help is greately appriciated..

is it not already encoded?
have you tried sending as is?

What Operating System and version do you have?

Where physically is the mailbox for «my mail id»? Is it on the server where you see «dead.letter» or somewhere else?

Can your normal mail reading software read the mailbox on the unix server directly and process the attachments? If so it is just a case of copying «dead.letter» to a mailbox which your mail reader can see.

If not, the issue is how to forward the message from a unix mailbox to the final destination mailbox. I’ve not been successful in reading attachments after manually forwarding a mail with the «mailx» «

F» command. Others may know better techniques.

Sorry to throw a pile of ripe lemons into the debate.

The format of unix delivered mail in a unix mailbox is suitable for reading by a unix-compatible mail reader. Forwarding the raw file to a Microsoft email reader does not seem to work (I’ve tried it) and extracting the encoded attachment and trying to decode it with «uudecode» also does not seem to work (I’ve tried it).

I believe that an email which ends up in «dead.letter» originates from that computer but has been sent to an incorrect local email address (or a mistyped external email address which has been interpreted as a local email address). Perhaps the O/P can re-send the email?

As the O/P is keeping quiet about the O/S environment we really cannot explore this further.

Источник

Collect IBM MQ MustGather data to solve dead letter queue problems on Linux, UNIX, Windows and IBM i

Troubleshooting

Problem

Environment

These instructions apply only to IBM MQ V9.2, V9.1, V9.0 and V8.0, and IBM WebSphere MQ V7.5, V7.1, V7.0 AIX, HP-UX, Linux, Solaris and Windows, and to IBM MQ V9.2, V9.1, V9.0 and V8.0, IBM WebSphere MQ V7.1, V7.0 and V6.0 on IBM i. Refer to the IBM MQ Read First page for instructions on other operating systems:

Resolving The Problem

Please answer these questions about the problem and then follow the steps below

• What dead-letter queue problem did you observe on the system?
• What time did the dead-letter queue problem start and when did it stop?
• Where are the dead-letter messages coming from, and what is their intended route?

Step 1: Generate Data

If messages are going to the dead letter queue right now, or if you can reproduce the problem which cases messages to go there, generate data to provide more information about the problem:

Step 2: Collect Data

Collecting Data Automatically

If you are running IBM MQ V9.2, V9.1, V9.0 or V8.0, IBM WebSphere MQ V7.5, V7.1.0.1 or later, or V7.0.1.8 or later collect data automatically with the runmqras command on both sides of the channel. Be sure to collect the runmqras defs , cluster and trace sections, and to specify your case number:

runmqras -section defs,cluster,trace -qmlist QMA -caseno TS001234567

Collecting IBM MQ Data Manually

If your system has more than one IBM MQ installation, use the setmqenv command to choose the one with the problem before proceeding:

Linux and UNIX

Windows

Record the IBM MQ version and maintenance level on both sides of the channel. Alternatively, collect the IBM MQ data manually on both sides of the channel.

Record the IP addresses and hostnames of the systems on both sides of the channel.

Save the IBM MQ configuration information, for example, registry keys and .ini files.

If your system has more than one IBM MQ installation, record your IBM MQ installation details:

Linux and UNIX

sh> dspmqinst > /tmp/dspmqinst.txt

Windows

Record the status of your queue managers:

Linux and UNIX

sh> dspmq -a > /tmp/dspmq.txt

Windows

C:\> dspmq -a > %TEMP%/dspmq.txt

IBM i command line

IBM i Qshell

===> /QSYS.LIB/QMQM.LIB/DSPMQ.PGM -a > /tmp/dspmq.txt

Record the IBM MQ processes active on your system:

Linux and UNIX

sh> ps -ef | grep mq > /tmp/ps.txt

Windows

C:\> TASKLIST /V > %TEMP%/tasklist.txt

IBM i command line

IBM i Qshell

===> ps -ef | grep mq > /tmp/ps.txt

On IBM WebSphere MQ V7.1 and later installations, use dmpmqcfg command to record the queue manager configuration:

Linux and UNIX

sh> dmpmqcfg -m QMA >/tmp/QMA.config.txt

Windows

IBM i Qshell

===> /QSYS.LIB/QMQM.LIB/DMPMQCFG.PGM -mQMA > /tmp/QMA.config.txt

Otherwise, on IBM WebSphere MQ V7.0 and earlier installations, use runmqsc to record the queue manager configuration. If any command returns an error, carry on with the others:

DISPLAY QMGR ALL
DISPLAY Q(*) ALL
DISPLAY SUB(*) ALL
DISPLAY TOPIC(*) ALL
DISPLAY CHANNEL(*) ALL
DISPLAY SERVICE(*) ALL
DISPLAY PROCESS(*) ALL
DISPLAY LISTENER(*) ALL
DISPLAY NAMELIST(*) ALL

On all IBM MQ server installations, use runmqsc to record status information from the queue manager . If any command returns an error, carry on with the others:

DISPLAY PUBSUB ALL
DISPLAY QMSTATUS ALL
DISPLAY CHSTATUS(*) ALL
DISPLAY LSSTATUS(*) ALL
DISPLAY SVSTATUS(*) ALL
DISPLAY SBSTATUS(*) ALL
DISPLAY CONN(*) TYPE(*) ALL
DISPLAY QSTATUS(*) TYPE(QUEUE) ALL
DISPLAY QSTATUS(*) TYPE(HANDLE) ALL
DISPLAY TPSTATUS('#') TYPE(PUB) ALL
DISPLAY TPSTATUS('#') TYPE(SUB) ALL
DISPLAY TPSTATUS('#') TYPE(TOPIC) ALL

If your channel is having difficulty connecting, use your Operating System tools to list network connections on both sides immediately before and after the connection attempt:

Displaying network connections on Linux and UNIX

Displaying network connections on Windows

Displaying IPv4 and IPv6 network connections at the IBM i command line

===> NETSTAT OPTION(*CNN) ===> NETSTAT OPTION(*CNN6)

Manually package your files for IBM , including files containing the output from the commands listed in Step 1 and Step 2.

Step 3: Send Data to IBM

A good description of the problem and the data is the most important information you can provide to IBM. Please do not send data without providing a description!

• See Exchanging information with IBM Software Support for FTP and email instructions.
• Go to the IBM My Support site to open or update a case.

Note: Always update your case to indicate that data was sent

If you need to speak with IBM Software Support, contact your country representative. If you need to speak with IBM Software Support in the US, you can call 1-800-IBM-SERV.

Источник