Show Bid Request
Simple POP3 Server Needed
Bid Request Id: 41197
|
|
|
|
Posted by: |
Chen Avinadav (1 ratings)
(Software buyer rating 10 )
|
|
Non-action Ratio: |
Very Good - 0.00%
|
|
Posted: |
Dec 26, 2002
12:03:31 PM EDT
|
|
Bidding Closes: |
Jan 9, 2003
12:26:09 PM EDT
|
|
Viewed (by coders): |
923 times
|
|
Deadline: |
1/20/2003
TIME EXPIRED
|
|
|
|
|
Description:
What I'm looking for is basically a simple POP3 server that can run as a service on my server. It must support the basic commands - USER, PASS, LIST, STAT, TOP, RETR, DELE, QUIT, etc. (No APOP support is required).
I am open to suggestions when it comes to the language. I would rather use C/C++ but Perl or anything else can only be considered.
The system will be used by other people but me, so needs to be easy to set up - most of them are not rocket scientists.
If you have any questions please do let me know. Please download the attached file (pop_spec.zip) for more information.
Deliverables:
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request.
3) Complete ownership and distribution copyrights to all work purchased.
Platform:
*nix Web servers.
Must be 100% finished and received by buyer on:
Jan 20, 2003 EDT
Deadline legal notes: All times are expressed in the time zone of the site EDT (UT - 5). If the buyer omitted a time, then the deadline is 11:59:59 PM EDT on the indicated date.
Special Conditions / Other:
There is no particular deadline, I just don't want it to take too long.
Additional Files:
This bid request includes IMPORTANT additional attached files. Please download and read fully before bidding.
|
|
|
Bidding/Comments:
|
All monetary amounts on the site are in United States dollars.
Rent a Coder is a closed auction, so coders can only see their own bids and comments. Buyers can view every posting made on their bid requests. |
See all rejected bids (and all comments)
| Name |
Bid Amount
|
Date |
Coder Rating |
|
|
This bid was accepted by the buyer!
|
$500 (USD)
|
Dec 27, 2002
8:20:35 AM EDT
|
9.95
(Excellent)
|
|
|
Hi
I can do this for you, but first I'd like to make a few suggestions and ask a few questions ;)
I'm not sure that using a database is a good idea. It would probably be better (and surely faster) to just store all the stuff in files.
That is, to have structure similar to
/somepath/userid - user's directory
/somepath/userid/mail - user's mail directory
userid could be e.g. first several bytes of hashed user name. If you want the best security for it, I'd suggest keeping hash of hash of user's password. This way retrieving user's password will be impossible, yet it can be easily validated. This, of course, makes sending forgotten passwords to users impossible, though.
Eliminating need to have a database installed and having data stored in the way I described would increase portability and performance, and greatly reduce code size and complexity (thus reducing chances for bugs to appear).
I take it that I shouldn't bother with the way new emails get into users' inboxes and assume that the files just magically appear in those directories?
I can write it in C++ and make the code able to be compiled on any *nix OS - I have experience with writing *nix servers. (must admit there was no POP3 one, but that's just a matter of reading the RFC ;)
I would appreciate it if you contact me to ask any questions you may have.
Looking forward to hear from you.
Good luck,
Ivan
|
|
|
|
|
|
|
