Most incoming message events start their log history as courieresmtpd: started,ip=[xx.xxx.x.xxx]
Successful delivery or an error indication terminate the event. However, sometime there is no termination. IMO there should be no log if the remote host QUITs, whilst abrupt TCP disconnection should be logged as an error. In particular, I see that behavior when several connections overlap with one another. Perhaps, they are remote MTAs gettin a TO, and will retry. That kind of not-requested randomized greylisting is probably due to Debian sarge poor scheduling and/or my inability to configure that system properly. I'd like to know how often it happens. What should I do? Patching courierlog is not enough. I could patch the esmtp module (e.g. changing iovreadline so that it returns NULL on errors that courieresmtpd.c's main loop should log.) Is it relevant to know if the banner has been shown or not? Patched courierlog can recognize returning MTAs by their IP address, or should it consider their netblock? Any other idea? ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
