Bug 906 – sendmail NOQUEUE errors

Bug 906 - sendmail NOQUEUE errors

Summary:	sendmail NOQUEUE errors

Status:	CLOSED CURRENTRELEASE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	sendmail (Show other bugs)
Sub Component:
Version:	5.2
Hardware:	i386 Linux

Priority	medium Severity high
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-01-21 04:02 EST by aeneas
Modified:	2013-05-06 13:15 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	1999-03-22 15:35:21 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description aeneas 1999-01-21 04:02:19 EST

I'm running a system that handles about 50.000 e-mails a
day. On our RHL 4.2 we saw about 100 NOQUEUE messages a day
in our maillog, which was normal. However, after upgrading
to RHL 5.2 we about 300 of NOQUEUE messages per hour in our
maillog. There are two kinds of them:

NOQUEUE: SYSERR: putoutmsg (jupiter.CUBIK.COM): error on
output channel sending "220 bewoner.dma.be ESMTP Sendmail
8.8.7/8.8.7; Thu, 21 Jan 1999 10:03:10 +0100": Broken pipe

and

NOQUEUE: Null connection from [10.128.16.15]

I don't know why all these messages appear in our logs. We
have some users that tell us they have more difficulties
sending e-mail. Any ideas what could cause this?

Comment 1 Preston Brown 1999-03-22 15:35:59 EST

This is most likely caused when a spammer does "bad things" with
sendmail in an attempt to cram spam into your server.  Please see if
our latest sendmail in Red Hat Linux 5.9 beta (sendmail 8.9.3) solves
your problems, and if it doesn't, reopen the bug with additional
information.

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