WARNING: Ignoring deprecated option --unzip

Glenn Steen glenn.steen at gmail.com
Mon Jan 26 21:58:13 GMT 2009

2009/1/26 Julian Field <MailScanner at ecs.soton.ac.uk>:
> On 26/1/09 18:23, Kevin Miller wrote:
>> -----Original Message-----
>>> its really strange that's all, the system is easily managing to
>>> keep up now but telnet to 25 is still really slow to respond,
>>> like 5 - 10 seconds or it'll time out completely.  I noticed my
>>> mailscanner sql db is getting a bit fat so maybe this is causing
>>> some problem...
>> Getting into the game late here, so maybe it's been asked already, but
>> are you running a caching DNS server on the box?  That may help.
>> Too, I've seen telnet spin it's wheels when there was no reverse zone
>> for the source (i.e., your) host.  You don't actualy need a reverse
>> entry for your host if you don't have one, but having even a single
>> entry in the reverse zone allows the name server to return a 'not found'
>> almost instantly, whereas it seems to wait to timeout if no reverse zone
>> exists...
> Yes, that's exactly what I was going to suggest. If telnet 25 produces a
> long delay before giving a sendmail welcome prompt, it's a *sure* sign of
> trouble resolving DNS names, as sendmail does forward and reverse lookups on
> your address to work out who you are before it talks to you.
> Jules
Not only Sendmail... Postfix usually does too. Might be visible in the
warnings log file (if one does lig file separation).

-- Glenn
email: glenn < dot > steen < at > gmail < dot > com
work: glenn < dot > steen < at > ap1 < dot > se

More information about the MailScanner mailing list