topic Re: transient parse errors. Sendmail Version 8.9.3 (PHNE_24419+JAGae58098) in Operating System - HP-UX

transient parse errors. Sendmail Version 8.9.3 (PHNE_24419+JAGae58098)

Ana Martinez Olaizola — Wed, 19 Mar 2003 09:19:30 GMT

I have updated to sendmail Version 8.9.3 (PHNE_24419+JAGae58098) and since then I get on the screen the error "transient parse error--- message queue for future delivery" with some emails. I see that the domains where these email have to go cannot be resolved. I have also tried other name servers and they don't know the domains either.
I have a name server than runs on the same machine than sendmail, and it had no problems before.
What do I have to do to get rid of the error?

Re: transient parse errors. Sendmail Version 8.9.3 (PHNE_24419+JAGae58098)

Berlene Herren — Wed, 19 Mar 2003 15:12:04 GMT

It is temporary error and it is logged every time when sendmail re-sent message in mqueue. (default is every 30m). The new binary changed the alert level for the 4.x.x messages to alert, to let the user know that there maybe a delay in transmitting the message. If
are using good fqdns (no dns issues), then you should not received the transient messages.

A fix for this will be included the in the GR sendmail patch. Until then, you can remove from syslog.conf:
*.alert /dev/console

Probably not a good idea.

Or configure syslog.conf for every subsystem (time consuming)

Berlene

Re: transient parse errors. Sendmail Version 8.9.3 (PHNE_24419+JAGae58098)

Ana Martinez Olaizola — Wed, 26 Mar 2003 11:24:36 GMT

I use good fqdn and I do not know why I get the error. I get it only with emails that are sent to domains that do not exist. I don't know why sendmail keeps trying to send these emails.

Re: transient parse errors. Sendmail Version 8.9.3 (PHNE_24419+JAGae58098)

Berlene Herren — Wed, 26 Mar 2003 12:02:23 GMT

Ana, there will be a general release patch out soon that will correct this. If you are not subscribed to the HP Security Bulletins, please do and you will be notified when this patch is released.

We have seen this behavior in a few cases and including this fix is a reason the patch has not been released yet. But it will be soon.

Regards,
Berlene