Re: MCI Cache / ESMTP facilities?

On May 23, 12:12 am, p...@xxxxxxxxxxxx (Per Hedeland) wrote:

confMCI_CACHE_SIZE=1
confMCI_CACHE_TIMEOUT=0

In order to enable the HostStatusDirectory facility?

What makes you think that they have anything to do with
HostStatusDirectory? They don't, AFAIK, but refer to the in-memory
connection cache of a running sendmail process.

The HostStatusDirectory option is disabled automatically if you
disable the MCI connection cache. Sendmail warns you if you try to use
HostStatusDirectory and have the MCI cache size set to zero:

"
Warning: HostStatusDirectory disabled with ConnectionCacheSize = 0
"

Does the remote send the word "SIZE" without a limit? That's valid too,
see RFC 1870. Otherwise you would appear to have found a bug in
sendmail, I find it extremely unlikely that this particular bug exists
though.

I can't see that the other side sent 'SIZE' at all.

Sending SIZE=xxxx on MAIL being related to the connection cache
settings? Sounds extremely unlikely too, but if there is a bug, who
knows - e.g. after having speculated that there is a bug, one could
speculate that the bug consists of sendmail getting confused about which
of the servers in the connection cache that supports the SIZE extension.
But since you're reducing the cache size to 1 from the default of 2,
that ought to make the speculative bug *less* likely to be triggered.

I was more concerned that having to set the Cache Connection time out
to zero (which should negate having the Connection Cache size set to 1
(which keeps the HostStatusDirectory option 'happy') might be an
issue.

I'd guess the MCI cache has/would cache the available facilities, as
sendmail only does a NOOP (and can do little else) when re-using the
connection, so the initial greeting/facilities chatter would only be
seen once - hence my concern that setting the timout to zero (to get
us the HostStatusDirectory) might be triggering a bug, if it's not a
recommended way of getting persistant host status, with only single
'one at a time' connections.

Afterall, if the timeout is zero, it shouldn't be re-using a
connection at all - and should connect/re-negotiate all a fresh.

JB.
.

Relevant Pages

  • ldap cache, option -h -H sendmail 8.13
    ... We try to configure an ldap backup for ldaprouting with sendmail 8.13. ... we saw that sendmail keeps for a while a connection in cache and answer ...
    (comp.mail.sendmail)
  • Re: How to clear Os9 comms blockage?
    ... But meanwhile, my wireless ... >> of my connection. ... It seems unlikely to me that any of my cache files could ... In view of the blanket effect on all my internet apps, ...
    (comp.sys.mac.comm)
  • Re: XP remote connect to Win2K PC?
    ... synch every few months. ... crucial details of the cache behavior which is sometimes useful. ... >> If you have a 100mbps full duplex ethernet, and use a VPN connection ... >> Many here are accustomed to the speeds that RDP achieves over such ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: XP remote connect to Win2K PC?
    ... connection with each other--the "network" will be a VPN connection between ... >> Server 2003 Resource Kit applet that allows for manual control of several ... >> crucial details of the cache behavior which is sometimes useful. ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: What about all of the data the OS stores about us?
    ... Bookmarks are similar to the URL cache but neither really replaces the ... People who switched to the Mac out of security concerns generally did so ... then a connection is made to an Apple ... but a task-oriented local app. ...
    (comp.sys.mac.apps)