Hi,
Although this is not defined in any RFC, i would vote for the
popserver to reverse the order in which messages are counted.
message 1 should be the oldes, and message N (>1) should be younger.
Messages should be ordered according to arrival-timestamp at the
dbmail server (not date header).
The reasons I have for this are:
1) Principle of least surprise, all popservers I know off use the
above described ordering algorithm.
2) When debugging a mailclient (as it gets stuck on certain messages,
i.e. outlook with virusscanner) then changing message numbers
while doing a tcpdump are not very convenient.
3) When putting lmtp and pop logs next to eachother to follow
messages through the delivery chain, it wil not help debugging if
the order in which *most*
clients fetch messages is reversed against the order in which they
arrive. And most clients tend to go at it starting from 1 up.
It is probably easily fixed by changing ASC to DESC in db.c line
2167. However I'd like it to go into dbmail source.
Best regards,
Marc Dirix
_______________________________________________
Dbmail-dev mailing list
[email protected]
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
