Custom postfix delivery agent. May be based on "deliver" or "virtual" agents. Goal is to archive copies of emails, for short-term quarantine and long-term storage. Format based on mbox or mbx format, not maildir, and a simple index entry is stored as well, either in that same file or in a separate index. We want to store all email for a domain in a format of 1 file per day, with an index that allows us to quickly and easily access an individual message in the file. Each domain has it's own storage directory: ie; /mail/d/o/dom.com. Each email has a unique mailid, a 12 char string containing [A-Za-z0-9+-]. Given a domain, date, and mailid, we need to QUICKLY retrieve the particular message. (A mbox scan is too slow). Scenario 1. Postfix is running on a server "[url removed, login to view]" 2. Postfix receives email to "mailid-YEARMONTHDATE(at)[url removed, login to view]" YEARMONTHDATE is in the format 20050721 3. Postfix does a standard map lookup for "YEARMONTHDATE(at)[url removed, login to view]" and finds the mail storage directory Standard postfix map types must be supported (ie Btree, Hash, CDB). example: mailid_YEARMONTHDATE(at)[url removed, login to view] d/o/[url removed, login to view] May also support a PCRE or regex substition map, but must ensure that "." and other disallowed characters are replaced with '_' ie [url removed, login to view] would be stored in /d/_/[url removed, login to view] 4. Delivery agent prepends a top level directory, such as "/mail". 5. Delivery agent stores message in /mail/d/o/[url removed, login to view] 6. Some sort of index is stored into the same or a separate file, again, one index file per day. The index must be fast and small. It could be as simple as an association between the mailid, the size of the message and the offset from the beginning of the mailfile. 7. The message must be able to be quickly retrieved via a simple php script, given the domain, YEARMONTHDATE and mailid. ie, an http request: [url removed, login to view]
1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done.
a) Either a standalone delivery agent, or a patch to "deliver" or virtual, suitable to being applied with patch(1).
b) A simple php script demonstrating the retrieval methodology.
2) Deliverables must be in ready-to-run condition, as follows? (depending on the nature? of the deliverables):
a)? For web sites or? other server-side deliverables intended to only ever exist in one place in the Buyer's environment--Deliverables must be installed by the Seller in ready-to-run condition in the Buyer's environment.
b) For all others including desktop software or software the buyer intends to distribute: A software? installation package that will install the software in ready-to-run condition on the platform(s) specified in this bid request.
3) All deliverables will be considered "work made for hire" under U.S. Copyright law. Buyer will receive exclusive and complete copyrights to all work purchased. (No GPL, GNU, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site per the coder's Seller Legal Agreement).
Linux (specifically Centos 4, a RHEL4 clone) Postfix 2.3 Snapshot 20050716 PHP 5 for the php script example showing the retrieval methodology.