I wouldn't have any use for it. If I need that capability, I prefer simply install a little smtp service locally and point the app to localhost as the smtp server. Leaving it our would keep SA leaner and cleaner. It is dispiriting when every app vendor in the world seems to decided to add their own smtp service and generalized scheduluer to their app when there are perfectly good operating system services that could be leveraged.
And most people in a corporate situation are liable to run into firewall ACL restrictions at any rate. If you really think you might add this feature, take a careful look before you leap. I added this to an application once because "Oh, all I have to do is an MX rec lookup on the desination server and send it off." Yeah, well... doing it correctly turns out to be quite a bit more complex than it appears on the surface. Unfortunately by the time I realized that we were already committed to providing the feature. arley > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Dirk Bulinckx > Sent: Sunday, August 24, 2003 12:58 PM > To: [EMAIL PROTECTED] > Subject: [SA-list] Direct mail sending (without an "internal" SMTP > server) > > > Sending mail directly to the destination SMTP server is that > something that > is interesting for you guys? > (with that we mean that instead of sending the mail to your smtp > server who > will relay it to the destination SMTP server, we would directly connect to > the destination server (based on the MX record of the TO of the mail) and > send it). > > > > > dirk. > > > > > To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] > With the following in the body of the message: > unsubscribe SAlive > To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
