heybluez wrote:
OK. I download James untarred it and it was easy to accept email. I was
wondering how 1] to not have to add a user but have it check my database
(all it needs to see is one field) and 2] what do I need to know to modify
the localdelivery mailet? For the latter, I want it to deliver the
FileStreamStore version to a different directory and not to the "inbox"
Could I put a mailet in before the localdelivery, drop the email where I
want and then set Mail.GHOST?
If you use James 2.3.0 (RC3) you can simply make direct use of the
ToMultiRepository mailet (remove the LocalDelivery and the lookup to the
UsersRepository).
You can configure the ToMultiRepository:
<mailet match="All" class="ToMultiRepository">
<repositoryUrl>file:///some/place/</repositoryUrl>
<repositoryType>MAIL</repositoryType>
</mailet>
This will not check anything: it will just get the localpart of the
recipient address (the part before the @) and use it as a subfolder for
the /some/place folder to store there the files.
Nothing can be more simple than this ;-)
PS: you may want to use the HostIsLocal matcher (match="HostIsLocal") to
check at least that the domain of the recipient is valid for your james.
To summarize:
You remove all the default processors/mailets configuration and just add:
<processor name="root">
<mailet match="HostIsLocal" class="ToMultiRepository">
<repositoryUrl>file:///some/place/</repositoryUrl>
<repositoryType>MAIL</repositoryType>
</mailet>
.. do something else with non-local message (like bounce, or simply
loose them ...
</processor>
Restart james and send a mail to it!
Stefano
BTW, James is f'ing cool. I want to take it a step further and integrate it
with our archiving system....but first things first :)
Vincenzo Gianferrari Pini wrote:
Yes, it would be very simple to do that with James, and it would be very
lightweight.
In the simplest form, you would simply use the default configuration,
drop out some unneeded functionalities, disallow the pop3
functionalities, define the users, and the emails sent to a user would
end up in its mailbox that by default is a dedicated directory in the
file system.
You could decide to use a database for the inboxes and add many extra
functionalities, tailoring the system to your needs.
Vincenzo
heybluez wrote:
Hello All,
I am building an email archiving application and I would like to have an
SMTP reciever that I can "email" to. Basically, I want to be able to send
email to "[EMAIL PROTECTED]" and have it deposit the email into a dir
(/some/place/foo/) and so on for other email addresses......
I will then have a process pick these up and do the archive.
Is James the server to do this with? I want something lightweight and do
not need any POP/IMAP and so on.
Thanks,
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
