topic Re: ELM error messages. in Operating System - HP-UX

ELM error messages.

Russ Hancock_1 — Tue, 19 Oct 2004 04:08:47 GMT

Does anyone know where I can look to find any elm error messages.

I sending mails to Outlook in a HTML format using the include method on the command line. All was working fine, but now it doesn't work.( nothings been changed ! )

It still says message sent, but it nevers arrives. Other server still working, so I can't blame exchange.

Any ideas where to start looking? mailx and interactive elm still working!

Re: ELM error messages.

BONNAFOUS Jean Marc — Tue, 19 Oct 2004 06:35:40 GMT

Hi,

You have /var/adm/mail.log file.
See also messages in error on /var/spool/mqueue. You have one file that contain the message and one that contain config and error cause.

If elm works interactively error can be in syntax of your command. What command do you use ?

Rgds
JMB

Re: ELM error messages.

Bill Hassell — Tue, 19 Oct 2004 07:34:30 GMT

Most likely the message is not being delivered due to networking issues, DNS specifically. elm doesn't actually send a message, it creates a message and then hands it off to sendmail for delivery. Send a test message using sendmail's trace feature:

sendmail -v -s test name@somewhere.com < /etc/issue

You'll see the handshake and any errors. mail.log will also have the reason for non-delivery.

Re: ELM error messages.

Russ Hancock_1 — Tue, 19 Oct 2004 07:37:58 GMT

Command and files used below.
Just tested it again on a similar machine, indentical config, and it works.

Cheers
Russ

COMMAND USED,
/usr/bin/elm -s "NODE02 Halifax Check Mail" abc@renishaw.com < /ren/iman/mailer/tmp/elm_input.3675

#######################################
cat /ren/iman/mailer/tmp/elm_input.3675
[include /ren/iman/mailer/lib/TestMail.html text/html base64]

######################################
cat /ren/iman/mailer/lib/TestMail.html

TEST MESSAGE

#######################################
MESSAGE in /var/adm/syslog/mail.log
#######################################
Oct 19 13:27:25 node02 sendmail[3714]: NAA03714: from=root, size=874, class=0, pri=30874, nrcpts=1, msgid=<200410191227.NAA03714@node02.renishaw.com>, relay=root@localhost
Oct 19 13:27:26 node02 sendmail[3716]: NAA03714: to=abc@renishaw.com, ctladdr=root (0/3), delay=00:00:01, xdelay=00:00:00, mailer=relay, relay=halifax [172.16.5.96], stat=Sent (OK)

Re: ELM error messages.

Steven E. Protter — Tue, 19 Oct 2004 07:46:12 GMT

all mail errors should show up in a log file.

/var/adm/syslog/mail.log

mailq

Is the mail getting off the machine?

sendmail -v -q

verbose process the outbound mail queue

Its possible that the exchange server is not allowing relay from your server. That needs to be set up explicitly, via ip address.

sendmail -v -d8.99 -d38.99 someone@your.net
type text

.

maximum diagnostics.

SEP

Re: ELM error messages.

Russ Hancock_1 — Tue, 19 Oct 2004 07:57:27 GMT

Hi Bill
I get , and it gets through, so can I assume this is an MS-Exchange Problem then?

I also ran the -V in ELM and got the same message even though it never got through ?!

Cheers
Russ

(node02) / > sendmail -v -s test abc@renishaw.com < /etc/issue

test... User unknown
abc@renishaw.com... Connecting to SERVER via relay...
220 SERVER.renishaw.com ESMTP Server (Microsoft Exchange Internet Mail Service 5.5.2657.72) ready
>>> EHLO node02.renishaw.com
250-SERVER.renishaw.com Hello [node02.renishaw.com]
250-XEXCH50
250-HELP
250-ETRN
250-DSN
250-SIZE 0
250-AUTH LOGIN
250 AUTH=LOGIN
>>> MAIL From: SIZE=53
250 OK - mail from ; can accomodate 53 bytes
>>> RCPT To:
250 OK - Recipient
>>> DATA
354 Send data. End with CRLF.CRLF
>>> .
250 OK
abc@renishaw.com... Sent (OK)
/dead.letter... Saved message in /dead.letter
Closing connection to SERVER
>>> QUIT
221 closing connection
(node02) / >

Re: ELM error messages.

Bill Hassell — Tue, 19 Oct 2004 08:27:44 GMT

Sorry for the -s option in sendmail--that's the reason for the error message about test. I was thinking about elm and mailx's option for a subject. Yes, the Exchange server got the mail. I would guess that the Exchange administrator implemented some new spam filters and your incoming mail was chewed up rather than delivered. For instance, if your HP-UX server doesn't have a DNS A, CNAME or MX record for node02.renishaw.com (that can be seen at the Exchange server) or possibly a missing WINS record for your node02 computer, then Exchange may silently throw away the email.