Red Hat Bugzilla – Bug 388491
Sendmail and older version of Thunderbird conflict
Last modified: 2018-04-11 06:30:14 EDT
Description of problem:
I am using sendmail-8.14.1-4.2.fc8 along with dovecot-1.0.7-2.fc8 configured as
a mail server with no encoding or encryption on the FC8 box. IMAP and POP3 are
I find that evolution-2.8.3-2.fc6 is able to send SMTP mail, however
thunderbird-188.8.131.52-3.fc6 and thunderbird-184.108.40.206-2.fc6 is not able to send
SMTP mail. I find with 2 machines running FC6 when I try to send an email I
have a login screen with "Mail Server Password Required" pop up. When I enter
the password for that account another login screen pops up. If I hit OK without
a password it says:
Sending of message failed.
The server may be unavailable or is refusing SMTP connections.
From the maillog when I log into the server:
Nov 17 10:12:28 wwns dovecot: pop3-login: Login: user=<david>, method=PLAIN,
I don't see any sign (with the default log level for sendmail) that the data is
being seen by the server.
I don't know if it is a protocol conflict with sendmail.
Version-Release number of selected component (if applicable):
Very. Tried on 2 boxes running FC6 and thunderbird
Steps to Reproduce:
1. Run thunderbird on computer
2. Try to send a message
3. See login screen pop up.
thunderbird doesn't send email, however evolution seems to work.
Email being sent should work.
send me an email if more info is needed. email@example.com
I do not know why this should be a sendmail problem at all.
Assigning to thunderbird.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach logs from your SMTP communication between the Thunderbird and
sendmail. The instructions how to get one are available at
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.