public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: James E Wilson <wilson@specifix.com>
To: overseers@sourceware.org
Subject: strange bounces
Date: Fri, 18 Nov 2005 02:05:00 -0000	[thread overview]
Message-ID: <1132278418.9250.66.camel@aretha.corp.specifix.com> (raw)

Since no one seems to know what the problem is, I tried looking for
info, and found an interesting thread on the nntp.perl.org server in the
perl.qsmtpd mailing list, with the subject line "Strange bounce problem"
sent on Nov 4, 2004.  Since there is no convenient URL, I've quoted the
interesting parts of the most interesting message:

I don't know if this might help, but I just spent hours with ethereal
and
full debugging on all the servers and here is what is happening:

telnet server 25
220 server ESMTP qpsmtpd 0.28 ready; send us your mail, but not your spam.
503 MAIL before RCPT
503 MAIL FIRST

Now, looking at the tcpdumps reveals that you in fact never sent anything,
however, if you look at the logs you see that the server was dispatching
something like : RCTP TO: <thisuser@thisdomain.com>, back to ethereal and
you can see that sure enough a server sent that packet a good 10-15
seconds ago but was denied with the require_resolvable_fromhost.  What
seems like is happening is that Qpsmtpd is dropping the connection but the
buffers aren't being flushed so that when the next Qpsmtpd picks up the
file handle the old one had it's getting the data that was left over. 
I am running Pperl with --no-cleanup but enabling cleanup did nothing to
solve the problem as did just calling qpsmtpd directly from tcpserver
without pperl.  The only thing I have found that got rid of the problem
was to edit the require_resolvable_fromhost plugin and change it from
DENYHARD to DENYSOFT.  Hope this helps somebody out there.

Ed McLain

End quote.

There are also some other related suggestions in other messages in the
thread, but this one seemed like the most useful.  You might want to look at
the entire thread.
-- 
Jim Wilson, GNU Tools Support, http://www.specifix.com

             reply	other threads:[~2005-11-18  1:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-18  2:05 James E Wilson [this message]
2005-11-18  2:29 ` Christopher Faylor
2005-11-18 15:40   ` Daniel Jacobowitz
2005-11-18 17:55     ` Christopher Faylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1132278418.9250.66.camel@aretha.corp.specifix.com \
    --to=wilson@specifix.com \
    --cc=overseers@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).