Bug 89118 - when evolution tries to send mail: sendmail exited with status 64: mail not sent
when evolution tries to send mail: sendmail exited with status 64: mail not sent
Product: Red Hat Linux
Classification: Retired
Component: sendmail (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Florian La Roche
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2003-04-17 15:38 EDT by Wesley Tanaka
Modified: 2007-04-18 12:53 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-05-05 06:29:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Wesley Tanaka 2003-04-17 15:38:59 EDT
Description of problem:
When trying to send mail through sendmail using evolution 1.2.2 on RedHat
9.0, a dialog box pops up saying:

Error while performing operation:
sendmail exited with status 64: mail not sent.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. compose a new mail
2. send it
Actual results:
above error dialog appears.  mail does not arrive at destination.

Expected results:
no error dialog and mail should arrive at destination.

Additional info:
I originally filed this bug at:

Jeff Stedfast at Ximian informed me through email that he thought this was a
sendmail bug, thus I am now filing it here since I am using the stock redhat
sendmail package.

The command line that evolution is sending to sendmail is:

and when I run /usr/sbin/sendmail -i -f EMAILADDRESS --
directly on the command line, it also exits 64 and does not send any mail.

So, if Jeff is correct, my problem is that sendmail *should* be sending mail
with that command line, but does not.
Comment 1 Florian La Roche 2003-05-05 06:29:42 EDT
Seems to work fine for me.


Florian La Roche

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