Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: cygwin@cygwin.com From: Robert R Schneck Subject: Re: sending email from Cygwin Date: Thu, 15 Jul 2004 00:11:13 +0000 (UTC) Lines: 13 Message-ID: References: <401DE9E4.60E61FA2@dessent.net> <20040714013022.2CBDF85081@pessard.research.canon.com.au> <6.1.0.6.0.20040713222328.0335a278@pop.prospeed.net> <6.1.0.6.0.20040714102705.03334178@pop.prospeed.net> <20040714150732.GW1389@cygbert.vinschen.de> <6.1.0.6.0.20040714123944.0333d638@pop.prospeed.net> <20040714171754.GY1389@cygbert.vinschen.de> <6.1.0.6.0.20040714140739.0333a9e0@pop.prospeed.net> X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 206-15-139-207.dialup.ziplink.net User-Agent: slrn/0.9.8.0 (CYGWIN_NT-5.1) Larry Hall wrote: >Corinna Vinschen wrote: >>Methinks that a correct approach (for a given value of correct) would >>be to create the symlink in an ssmtp postinstall script. That's what >>exim does, too. Creating the symlink in the cron postinstall script >>was a hack at one point. I'd be happy to get rid of it. > > Capital idea! > Robert, can you add this to the next ssmtp release? I will do so, probably within the next week. Robert -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/