Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-12 Thread Jason Tishler
Corinna, On Thu, Aug 12, 2004 at 07:06:24PM +0200, Corinna Vinschen wrote: > On Aug 12 11:55, Jason Tishler wrote: > > BTW, you should be able to reproduce the problem as follows: > > > > [snip] > > procmail's fault. procmail deletes too much of the environment. > > Thou shalt not

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-12 Thread Corinna Vinschen
On Aug 12 11:55, Jason Tishler wrote: > Corinna, > > On Thu, Aug 12, 2004 at 05:09:37PM +0200, Corinna Vinschen wrote: > > On Aug 12 10:16, Jason Tishler wrote: > > > Good idea -- unfortunately, it didn't help. > > > > Sounds weird perhaps but... what if you change this line in > > .procmailrc: >

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-12 Thread Jason Tishler
Corinna, On Thu, Aug 12, 2004 at 05:09:37PM +0200, Corinna Vinschen wrote: > On Aug 12 10:16, Jason Tishler wrote: > > Good idea -- unfortunately, it didn't help. > > Sounds weird perhaps but... what if you change this line in > .procmailrc: > > PATH=/bin > > to > > PATH=/bin:/cygdrive/c/W

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-12 Thread Corinna Vinschen
On Aug 12 10:16, Jason Tishler wrote: > Corinna, > > On Thu, Aug 12, 2004 at 03:31:33PM +0200, Corinna Vinschen wrote: > > On Aug 12 09:11, Jason Tishler wrote: > > > I WAG that this problem may have something to due with the > > > setgid/setuid winsock problems that Pierre and I have seen (with >

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-12 Thread Jason Tishler
Corinna, On Thu, Aug 12, 2004 at 03:31:33PM +0200, Corinna Vinschen wrote: > On Aug 12 09:11, Jason Tishler wrote: > > I WAG that this problem may have something to due with the > > setgid/setuid winsock problems that Pierre and I have seen (with > > exim) before. Unfortunately, the trick of givi

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-12 Thread Corinna Vinschen
On Aug 12 09:11, Jason Tishler wrote: > Chris, > > On Wed, Aug 11, 2004 at 02:53:03PM -0400, Christopher Faylor wrote: > > I've added a line to cygwin which should display the failing hostname > > prior to displaying the winsock error. > > > > Could you retry with either the latest snapshot or th

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-12 Thread Jason Tishler
Chris, On Wed, Aug 11, 2004 at 02:53:03PM -0400, Christopher Faylor wrote: > I've added a line to cygwin which should display the failing hostname > prior to displaying the winsock error. > > Could you retry with either the latest snapshot or the latest cvs? It > won't fix the problem but it mig

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-11 Thread Christopher Faylor
On Wed, Aug 11, 2004 at 02:31:52PM -0400, Jason Tishler wrote: >Corinna, > >On Wed, Aug 11, 2004 at 07:03:48PM +0200, Corinna Vinschen wrote: >> $ net helpmsg 11001 >> >> No such host is known. >> >> What does the line before the above line in the strace output look >> like? > >See attached. I'v

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-11 Thread Jason Tishler
Corinna, On Wed, Aug 11, 2004 at 07:03:48PM +0200, Corinna Vinschen wrote: > $ net helpmsg 11001 > > No such host is known. > > What does the line before the above line in the strace output look > like? See attached. Thanks, Jason -- PGP/GPG Key: http://www.tishler.net/jason/pubkey.asc or ke

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-11 Thread Corinna Vinschen
On Aug 11 12:38, Jason Tishler wrote: > On Wed, Aug 11, 2004 at 01:42:05PM +0400, Eugene Kotlyarov wrote: > > I have problem using ssmtp from procmail after upgrading to cygwin > > 1.5.10-3. It only exists when ssmtp is called from procmail, when it > > is called directly it works fine. Does anyone

Re: Problem with ssmtp / procmail / cygwin 1.5.10-3

2004-08-11 Thread Jason Tishler
On Wed, Aug 11, 2004 at 01:42:05PM +0400, Eugene Kotlyarov wrote: > I have problem using ssmtp from procmail after upgrading to cygwin > 1.5.10-3. It only exists when ssmtp is called from procmail, when it > is called directly it works fine. Does anyone have any idea what's > wrong with it? No, bu