9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Robert Raschke <rrplan9@tombob.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] strange mail problems
Date: Wed, 26 Jan 2005 11:42:22 +0000	[thread overview]
Message-ID: <05d3cbf48c666b2db042516e12b9a410@tombob.com> (raw)
In-Reply-To: <8a970bbb6d4a3defe95d514e671379c9@hamnavoe.com>

Richard wrote:
>> The dns failure is coming from validatesender, which I thought was
>> only executed if verifysenderdomain is on in the stmpd.conf.  But
>> looking at the source of smtpd, it looks as if validatesender always
>> gets executed, regardless of smtpd.conf or the -r option to smtpd.
> 
> validatesender is different from verifysenderdomain: it makes an SMTP
> connection and sends a "RCPT TO:" command to check whether the sender
> email address actually exists.  To turn this off, you have to delete
> or rename the /mail/lib/validatesender script.

OK, that solves the immediate problem, thnak you.

I am seeing very strange dns problems though and I am unsure how to go
about finding what might be wrong with my setup:

cpu% upas/smtp -p /net/tcp!bazar2.conectiva.com.br /dev/null lua-bounces
smtp: dns: dns failure (/net/tcp!bazar2.conectiva.com.br)
cpu% ndb/csquery
> tcp!bazar2.conectiva.com.br!smtp
/net/tcp/clone 200.140.247.68!25
> 
cpu% upas/smtp -p /net/tcp!bazar2.conectiva.com.br /dev/null lua-bounces
cpu% 

[...wait a couple of minutes...]

cpu% upas/smtp -p /net/tcp/clone bazar2.conectiva.com.br /dev/null lua-bounces
smtp: dns: dns failure (/net/tcp/clone)
cpu% 

I seem to keep on losing some information somewhere.
Where would I look to figure this out?

Thanks,
Robby



  reply	other threads:[~2005-01-26 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-26  9:59 Robert Raschke
2005-01-26 10:05 ` Richard Miller
2005-01-26 11:42   ` Robert Raschke [this message]
2005-01-26 12:04     ` Richard Miller

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=05d3cbf48c666b2db042516e12b9a410@tombob.com \
    --to=rrplan9@tombob.com \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).