Stefano, Thank you for taking the time to explain this to me. I see your point of view and it makes sense. I've not convinced my company to agree with your (and now my) point of view, so I am still going to extend RemoteDelivery mailet with my own version that will do an MX lookup for all connections.
If this situation applies to anyone else, please let me know and I will glady share my code. I've been very excited to see Apache James grow and I hope that I can somehow contribute to the project in the future. Thanks Tim Michalski -----Original Message----- From: Stefano Bagnara [mailto:[EMAIL PROTECTED] Sent: Saturday, April 21, 2007 9:43 AM To: James Users List Subject: Re: RemoteDelivery mailet doesn't do an MX lookup on the gateway smtp hostname(s) [EMAIL PROTECTED] ha scritto: > Norman, > > I admit I am not an SMTP guru, so I'm open to accepting that my idea > doesn't make sense. Before I do that though, could you explain to me > why you think that Apache James should resolve addresses differently > when configured as a gateway than how it resolves addresses when > connecting directly to the e-mail destination server? Both email > servers are SMTP servers... Another proof for you: When your provider gives you the SMTP server name and the POP3 server names it provides you HOST NAMES or IP ADDRESSES and not a domain for which your Mail Client have to lookup MX servers. Every email client expect an SMTP HOST and not a domain in his SMTP configuration. This is exactly the same concept of the SMTP gateway in James. Stefano --------------------------------------------------------------------- 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]
