Bug 20977 - Sendmail queues message which can actually be delivered
Summary: Sendmail queues message which can actually be delivered
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: sendmail
Version: 7.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Florian La Roche
QA Contact: Dale Lovelace
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-11-16 19:51 UTC by ppinto
Modified: 2007-04-18 16:29 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-08-06 10:46:04 UTC


Attachments (Terms of Use)

Description ppinto 2000-11-16 19:51:44 UTC
When mail is sent using the command line or sendmail -v, mail is sent
correctly.

When netscape connects to sendmail over localhost, all messages are
queued, but never sent until one runs sendmail -q, at which point they
are properly sent on their way.

When

      FEATURE(`accept_unresolvable_domains')

is commented out, the problem disappears.

When one connects to sendmail via port 25, and runs commands by hand,
when one gives the RCPT myname@anothermachine.domain.name command,
it responds that the recipient is ok, and then "will queue".

When the feature (?) is turned off, then everything works as it should (at
least
as I expect it should -- mail is sent).

It is as if it hasn't yet check to see if it can resolve the recipient
domain when the
message is accepted and queued for later delivery, yet if the message is
not accepted
at this point, sendmail goes on to find that the domain can in fact be
resolved and
all is well.

Comment 1 Florian La Roche 2001-08-06 10:45:58 UTC
I can't reproduce this here. It sounds strange that this problem goes away
when disablen accept_unresolvable_domains.

Can you forward me a complete email that is failing/working? Seems to
work fine for me here.

Thanks,

Florian La Roche


Comment 2 Florian La Roche 2002-03-10 08:01:33 UTC
Looks all fine to me. Please re-open if you still think sendmail is doing
something wrong here.

Thanks,

Florian La Roche



Note You need to log in before you can comment on or make changes to this bug.