Hello!

I've just upgraded to version 1.5.3 from 1.3.7 (it worked stable so there was no reason to upgrade). Right now, I just get the EX_TEMPFAIL message instead of EX_NOUSER. It would be OK if I didn't touch the maildrop/main.C file and replace the static value of nouser from EX_TEMPFAIL to EX_NOUSER - for the sake of newcommers: that's the proper value for a non-existent user. So, I touched the files and replaced the EX_TEMPFAIL with EX_NOUSER. Built the binaries, installed them.... and gone mad. Why the f*@&{ maildrop can implement the correct behaviour when it would be the best LDA available. Right now, it violates sysexists.h and I'm not sure but maybe an RFC which describes how to behave in this situation. Sorry, Sam but I can only speak right from my heart. You gave the community this great piece of software. But why, tell me, why you can't beleive if you just listen to others your respect won't going down and you can make mistakes? Nobody's perfect, you know. Nor you, nor me. So many people told you that this ISN'T the correct behavior, more, I say, with this behaviour maildrop is a security risk. You know why? Because somebody can flood my filesystem. And you know why I don't make my user's list available to the open world? Because so many "great" harvesting tools are out there in the wild. Beside that, it makes bigger load on the machine (because of double checking of users).

So, pleae consider the people's demand and implement it. It won't be a shame. Anyway, it would be a glory that you can tell: " I made a mistake. One in X years." I will appriciate it, at least (If it matters to you).

Anyway, thanks for this software and don't take my words so hard.

To the other's: anybody has a working patch for the correct implemtation? If yes, tell me please and I will send mine to compare them.

bye, Ago