Showing results for 
Search instead for 
Did you mean: 

Inbound SMTP

Go to solution
Steven Schweda
Honored Contributor

Re: Inbound SMTP

> $ set process /priority = 'prio'

Hmmm. AUTHORIZE says:

Username: TCPIP$SMTP
Prio: 5

So, it's possible that I was trying to slow
it down rather than speed it up by setting
the process priority to 4.

Trust no one, I always say.
Steven Schweda
Honored Contributor

Re: Inbound SMTP

It's hard to believe that it'd cause trouble
for "localhost", but a DNS problem could
cause trouble for the SMTP receiver, too.

As usual, many things are possible. (Many
of those are unlikely, too, but "unlikely"
and "impossible" are spelled differently for
a reason.)
Andy Bustamante
Honored Contributor

Re: Inbound SMTP

Just a WAG, try TCPIP SHOW SERVICE SMTP/FULL and check for maximum and peak connections. If memory serves, the default limit is on the low side.

If you don't have time to do it right, when will you have time to do it over? Reach me at first_name + "." + last_name at sysmanager net
Allan Large
Frequent Advisor

Re: Inbound SMTP


Your comment about the SMTP.CONFIG prompted a thought ....

The file only had 2 lines GOOD-CLIENTS and RELAY-ZONES. Doing a process of elimination I found that a reference to a GOOD-CLIENTS specification was causing the delay because of a DNS lookup.

Anyway, removing the reference solved the delay, even though the domain specification was valid.
Trusted Contributor

Re: Inbound SMTP

I was going to suggest DNS problems usually cause these types of issues but because he mentioned localhost I thought Nah, highly unlikely...

I like that phrase Steven... about unlikely and impossible being spelled differently for a reason.