2007/12/4, Bernd Fondermann <[EMAIL PROTECTED]>: > HI fr33m2n, > > ok, very good question. :-)
Thanks. :) Mail servers receive emails. Without any customization, the server > drops them into the inbox of the receiving user. At any point, the > user can view them, delete them, whatever. That's default behavior. > > Customization is the process of changing the server's configuration > and let it do something which is somehow special to your needs. > > This is done by changing the mail processing pipeline. Either by doing > something with the mail itself, or by altering the routing of the > message. > > 1. Can you make up two simple use cases now, one where the email is > changed on its way to the receiver, one where the routing of the mail > is changed? 1) We must add to the server configuration something like this: domain.com smtp:second-server.com This will allow all mail which is adressed to domain.com be redirected to second-server.com 2) To change routing of the mail is very simple. We must change MX record to destination domain. For example we have MX record: domain.com IN MX 10 mx.server.com If we want to send mail to domain.com through mx.second.server we must change MX record to that domain, like this: domain.com IN MX 5 mx.second.server If we want to have backup mail server for this domain we must add mail server whith highter preference value, for example: domain.com IN MX 5 mx.second.server domain.com IN MX 10 mx.server.com 2. Try to identify, where in James' configuration you can do such > customizations (hint: Mailet API). I think, that we can use prewritten mailets. For example Forward mailet. Sorry, but now i can't test it, because i am at school and on this computer i can't install Java enviroment.] That is why I will answer later... Please come back to the list with any questions or results. > > Bernd > Is my answers are correct? 10x. :)) -- Ozerov Vasiliy aka fr33man
