----- Original Message -----
From: "Hawk" <[EMAIL PROTECTED]>
To: "Imail Gateway" <[EMAIL PROTECTED]>
Sent: Friday, January 17, 2003 8:43 PM
Subject: [IMGate] Error message from postfix 2.0.2


>
> Hi all,
>
> I keep getting this message from postfix:
>
> Subject: Postfix SMTP server: errors from mailin-04.ly.net[12.159.188.6]
> Transcript of session follows.
> Out: 220 imgw-3.ly.net - ESMTP - Postfix - Attn: UCE trespassers will be
> pursued.
> In:
> Out: 500 Error: bad syntax
> In: quit
> Out: 221 Bye
>
>
> mailin-04.ly.net[12.159.188.6] is our Imail 7.12 server.
>
>
>
> This is smtp -v:
>
> Jan 17 23:40:09 ns postfix/smtpd[3126]: connect from
> mailin-04.ly.net[12.159.188.6]

The connection.

> Jan 17 23:40:09 ns postfix/smtpd[3126]: > mailin-04.ly.net[12.159.188.6]:
> 220 imgw-3.ly.net - ESMTP - Postfix - Attn: UCE trespassers will be
pursued.

Postfix sends banner.

> Jan 17 23:40:09 ns postfix/smtpd[3126]: watchdog_pat: 0x80a6a90
> Jan 17 23:40:09 ns postfix/smtpd[3126]: < mailin-04.ly.net[12.159.188.6]:

Imail does NOT send a HELO, EHLO, or other valid command.

> Jan 17 23:40:09 ns postfix/smtpd[3126]: > mailin-04.ly.net[12.159.188.6]:
> 500 Error: bad syntax

Not getting a proper HELO, etc. Postfix says 500 Error: bad syntax

5xx errors are permanent errors.  4xx errors are temporary errors.

When a mail server gets a 5xx error, it should never try the mail again.

When a mail server gets a 4xx error, it should come back later.

> Jan 17 23:40:10 ns postfix/smtpd[3126]: watchdog_pat: 0x80a6a90
> Jan 17 23:40:10 ns postfix/smtpd[3126]: < mailin-04.ly.net[12.159.188.6]:
quit

Imail recognizes the 5xx series error, and sends back quit.

> Jan 17 23:40:10 ns postfix/smtpd[3126]: > mailin-04.ly.net[12.159.188.6]:
> 221 Bye

Postfix accepts the quit and returns 221 Bye.

> Jan 17 23:40:10 ns postfix/smtpd[3126]: smtpd_chat_notify: notify
postmaster

You have the assorted "spam the postmaster" settings turned on.  Sorry,
notification_classes.

The next several lines are gathering information about the failed
transaction.  Then Postfix, according to the rules you put in it, notifies
you about the failed transaction.

None of the rest has anything to do with why it failed, and is only the
aftermath.

> Jan 17 23:40:10 ns postfix/smtpd[3126]: connect to subsystem
public/cleanup
> Jan 17 23:40:10 ns postfix/smtpd[3126]: public/cleanup socket: wanted
> attribute: queue_id
...much deleted as not to flood list with useless babble...
> Jan 17 23:40:10 ns postfix/smtp[3120]: 6EA1A1FB157:
> to=<[EMAIL PROTECTED]>, relay=12.159.188.6[12.159.188.6], delay=0,
> status=sent (250 Message queued)
>
>
> Can someone please translate this into english :-)

You are using -v, which is probably not needed.  It is like using a flame
thrower to kill a fly.  It gets all over and burns up more than just the
fly.


My best guess is that Imail is getting busy in the middle of a trasaction.
Well, at the start really.

While busy, or for whatever the real reason is, it is sending out a bad
connection, and getting zapped by Postfix.

You could adjust Postfix to send out a 4xx error in this situation, or you
can find out what is really happening to your Imail box.

This is almost assuredly something on the Imail box.

What else is it running?  A firewall?

Have you lookd at the IMail KB for session errors of this type?

http://support.ipswitch.com/kb/

There are TONS of things in the KB that could correspond to your situation,
but you MUST look at the Imail side of things, find what is on the logs, and
plug it into the KB to see.

--Eric


Reply via email to