Quoting Milan Zamazal ([email protected]): > Thanks for all the suggestions. I'll discuss the problem with upstream > again and then decide what to do. > > On the Debian side, I'll probably implement the big debconf message. It > should inform the user about the change and suggest stopping MTA on the > computer until crm114 behavior is checked (and fixed if necessary). The > installation script could offer to stop the MTA itself, but I'm afraid > of situations when this action would fail, resulting in various problems > up to mail loss again.
That would need another debconf message and also detect what MTA is running. Also, even in situations where there is no local MTA, users could be hit by this problem (fetchmail+procmail comes to my mind, not sure if some setups can work without MTA but I'm fairly sure one can find some). So, any warning should be generic enough so that anyone using crm114, or having some of his|her users potentially using it should be warned loudly enough. --
signature.asc
Description: Digital signature
