Re: No transport provider was available for delivery to this recipient
On Thu, Jan 25, 2001 at 07:53:48AM -0800, john roberts wrote: > I sometimes get this message when I am trying to send mail from Outlook 2000 > or 97 to qmail 1.03 server: > > No transport provider was available for delivery to this recipient. Dies this message pop up immediately or after some kinda timout? What do the qmail logs say? Maybe tcpservers max connection limit was hit at that time? \Maex -- SpaceNet AG| Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 Research & Development | D-80807 Muenchen| Fax: +49 (89) 32356-299 Stress is when you wake up screaming and you realize you haven't fallen asleep yet.
Re: No transport provider was available for delivery to this recipient
john roberts <[EMAIL PROTECTED]> wrote: > > No transport provider was available for delivery to this recipient. This comes up a lot -- if you search the qmail mailing list archives, one of the pointers is to this MS kb article: http://support.microsoft.com/support/kb/articles/Q197/4/17.ASP?LN=EN-US&SD=gn&FR=0 Basically, they're violating the SMTP spec by not enclosing addresses in <>. Charles -- --- Charles Cazabon<[EMAIL PROTECTED]> GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: No transport provider was available for delivery to this recipient
There is nothing in /var/log/maillog when this happens. Its like it never gets to the mailserver to process. Typically the message sits in the outlook outbox for a few seconds before I get the message back "no delivery". How do I look to see what the tcpservers max connection limit is? John >From: Markus Stumpf <[EMAIL PROTECTED]> >To: john roberts <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED] >Subject: Re: No transport provider was available for delivery to this >recipient >Date: Thu, 25 Jan 2001 17:11:03 +0100 > >On Thu, Jan 25, 2001 at 07:53:48AM -0800, john roberts wrote: > > I sometimes get this message when I am trying to send mail from Outlook >2000 > > or 97 to qmail 1.03 server: > > > > No transport provider was available for delivery to this recipient. > >Dies this message pop up immediately or after some kinda timout? > >What do the qmail logs say? >Maybe tcpservers max connection limit was hit at that time? > > \Maex > >-- >SpaceNet AG| Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 >Research & Development | D-80807 Muenchen| Fax: +49 (89) >32356-299 >Stress is when you wake up screaming and you realize you haven't fallen >asleep yet. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: No transport provider was available for delivery to this recipient
On Thu, Jan 25, 2001 at 10:17:07AM -0600, Charles Cazabon wrote: > john roberts <[EMAIL PROTECTED]> wrote: > > > > No transport provider was available for delivery to this recipient. > http://support.microsoft.com/support/kb/articles/Q197/4/17.ASP?LN=EN-US&SD=gn&FR=0 > > Basically, they're violating the SMTP spec by not enclosing addresses in > <>. Dan "fixed" this (i.e. added the workaround for non RFC compliant clients) in at least qmail-1.03 (just verified, works). The problem only happens with pre qmail-1.03 versions (our old qmail-1.01 server does not accept addresses withou the <>). \Maex -- SpaceNet AG| Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 Research & Development | D-80807 Muenchen| Fax: +49 (89) 32356-299 Stress is when you wake up screaming and you realize you haven't fallen asleep yet.
Re: No transport provider was available for delivery to this recipient
On Thu, Jan 25, 2001 at 08:40:12AM -0800, john roberts wrote: > delivery". How do I look to see what the tcpservers max connection limit > is? tcpservers option "-c" defines the number of simultaneous connections. Default is 40. See http://cr.yp.to/ucspi-tcp/tcpserver.html You have to check your qmail-smtpd startup script to see what value you are using. \Maex -- SpaceNet AG| Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 Research & Development | D-80807 Muenchen| Fax: +49 (89) 32356-299 Stress is when you wake up screaming and you realize you haven't fallen asleep yet.
RE: No transport provider was available for delivery to this recipient
We've experienced this error a few times here, generally when sending large files (>2Mb). I thought it was a timeout problem with Outlook so I set the server timeout to a higher figure in the internet email service and it doesn't happen now. -Original Message- From: john roberts [SMTP:[EMAIL PROTECTED]] Sent: Thursday, January 25, 2001 4:40 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: No transport provider was available for delivery to this recipient There is nothing in /var/log/maillog when this happens. Its like it never gets to the mailserver to process. Typically the message sits in the outlook outbox for a few seconds before I get the message back "no delivery". How do I look to see what the tcpservers max connection limit is? John >From: Markus Stumpf <[EMAIL PROTECTED]> >To: john roberts <[EMAIL PROTECTED]> >CC: [EMAIL PROTECTED] >Subject: Re: No transport provider was available for delivery to this >recipient >Date: Thu, 25 Jan 2001 17:11:03 +0100 > >On Thu, Jan 25, 2001 at 07:53:48AM -0800, john roberts wrote: > > I sometimes get this message when I am trying to send mail from Outlook >2000 > > or 97 to qmail 1.03 server: > > > > No transport provider was available for delivery to this recipient. > >Dies this message pop up immediately or after some kinda timout? > >What do the qmail logs say? >Maybe tcpservers max connection limit was hit at that time? > > \Maex > >-- >SpaceNet AG| Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0 >Research & Development | D-80807 Muenchen| Fax: +49 (89) >32356-299 >Stress is when you wake up screaming and you realize you haven't fallen >asleep yet. _ Get your FREE download of MSN Explorer at http://explorer.msn.com
Re: Re: No transport provider was available for delivery to this recipient
>john roberts <[EMAIL PROTECTED]> wrote:>> >> No transport provider was available for delivery to this recipient.>This comes up a lot -- if you search the qmail mailing list archives,>one of the pointers is to this MS kb article: From my experience, it's not the brackets - I have and exchange server relaying all messages to qmail server - never got this problem, except when had a problem with the Internet mail connector definitions in exchange __IncrediMail - Email has finally evolved - Click Here
