Wow, ok am I just blind, or do you have to jump through flaming hoops into a vat of molten lava to get smtp to be verified by username and password rather then IP address?!?!
The tutorials I've read and followed have all been outrageous ways to get this to work. I've not gotten one to do it correctly. And even if I DO do it by IP, not only will most mail users with dhcp be screwed every other day, but it wont even send anything to any mail domain without being in the rcpthosts file
Does anyone have a, even close to somewhat simple, solution?
I've thought about it, and in theory I would think it'd be, not tooooooo difficult... I mean... I'm even going to try and write this myself...This is my theory, if anyone wants to add to it or help with it, I'm sure allot of you know more then I can imagine about the subject
This is of course, in everyday terms... I think I can write a script that will verify a users user&pass and be able to send out going mail....rename the qmail-smtp program to something like qmail-smtp-run and name this smtp auth script qmail-smtp. I mention doing it this way because I think it would be easiest... no other files to change, all programs are going to still call qmail-smtp, ya know?
I know where the password program is... I can just call that, and then in the next command ask it if the password was correct. And if it was, write $domain from the senders intented addresse to the rcpthosts file real quick, then run ./qmail-smtp-run as normal. Since other things call smtp, don't require the password to be correct to run qmail-smtp-run, simply dont add the entry to rcpthosts if the password is in correct. The sender will just get the sysadmin message that it couldn't send because the domain wasn't in the rcpthosts file. That will hopefully avoid any mishaps... so I think the fucker should send the outgoing mail that way!!! lol sorry, the thing has been a pain in the neck for me
Is one already written?