Milter-greylist

Stuart Freedman <stuart@...> wrote:

> This line number corresponds to this chunk of code (770 being the
> mg_log function), given the way the line numbers shifted when I stuck
> the error messages in the ugly way :-) :

Well, feel free to make a cleaner change and to send a patch. The
__FILE__, __LINE__ will be useful for other debuggings.


>                 if ((b->b_lines = malloc(linelen + 1)) == NULL) {
> mg_log(LOG_ERR, "%s:%d malloc failed: %s", __FILE__, __LINE__,
> strerror(errno));

Is it always there? Next step is to display linelen + 1 and see if the
value gets odd.

I see it happens in the code that records the message body. You have
dacl statements? Did you use the maxpeek option to limit the size of
message seen by milter-greylist. If you did not, it's no surprise it may
explode if it is getting multiple big messages at the same time.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...