11 messages in net.sourceforge.lists.courier-usersRe: [courier-users] sender verify cal...
FromSent OnAttachments
ScottJul 18, 2006 5:40 pm 
ScottJul 18, 2006 5:43 pm 
Sam VarshavchikJul 18, 2006 6:12 pm 
ScottJul 18, 2006 10:24 pm 
Sam VarshavchikJul 19, 2006 3:59 am 
ScottJul 19, 2006 12:26 pm 
Ben KennedyJul 19, 2006 1:08 pm 
Sebastian LechteJul 20, 2006 4:39 am 
Marcus IlgnerJul 20, 2006 6:24 am 
Jay LeeJul 20, 2006 7:00 am 
Marcus IlgnerJul 20, 2006 8:54 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] sender verify callout vs. tarpitActions...
From:Scott (cour@troutpocket.org)
Date:Jul 18, 2006 10:24:57 pm
List:net.sourceforge.lists.courier-users

Sam Varshavchik wrote:

Scott writes:

I have a problem delivering to a server that uses "sender verify callout"... it makes an SMTP connection back to my server to do a faux connection:

220 mail.myserver.com ESMTP helo mail.theirserver.com 250 mail.myserver.com Ok. mail from: <> 250 Ok. rcpt to: <ada@myserver.com> 250 Ok. quit 221 Bye.

The blank "mail from:" causes starts the tarpit delay after a few tries until

No, it doesn't. Courier doesn't tarpit on a mail from:<>

Ok, so it's not that, but something in his call-back is causing the tarpit type delay to grow until it's about 2 minutes. The telnet session above was done by hand from the remote server so it might not be representative of the exact conversation between hosts. In general does "sender verify callout" cause tarpit type behavior in courier?

Will BOFHSUPPRESSBACKSCATTER=us@theirserver.com clear up this problem?

-Scott