Hello Aaron,
Now fixed in CVS for dbmail_2_0_branch (HEAD coming soon).
Thanks, for taking care of it. I think, you are speaking of this change:
http://cvs.dbmail.org/cgi-bin/cvsweb.cgi/dbmail/main.c.diff?r1=1.65.2.3&r2=1.65.2.4&f=h
This will work perfectly for my case. But I am not sure, if this is the
right solution for everyone. I have to admit that I do not fully
understand the whole insertion code, but there seems to be a problem:
dsn.c:dsnuser_worstcase_list(...) should return the worst case. With the
current solution, if there are two deliveries (A with DSN_CLASS_OK and B
with DSN_CLASS_FAIL), there will be no delivery to A because of the
failure with B. Maybe a better solution would be to make
pipe.c:insert_messages(...) respect the individual status of the entries
of dsnusers? It seems to me that insert_messages currently ignores (even
overwrites) the dsn classes, which are computed in
dsn.c:dsnuser_resolve_list(..).
Btw.: dsnuser_worstcase_list does not always return the worst case: if
one delivery results in DSN_CLASS_TEMP and another in DSN_CLASS_FAIL it
returns DSN_CLASS_TEMP. I don't know if this may cause problems anywhere.
A little confused,
Michael
