Red Hat Bugzilla – Bug 496702
Cannot send email to users on same domain
Last modified: 2010-04-28 07:16:45 EDT
Created attachment 340409 [details]
Data dump from openchangeclient plus additional info
Description of problem:
Cannot email other users in same domain through Exchange server.
When attempting to send email through an Exchange MAPI server to other users in the same domain, the email command gives a status of "MAPI_E_SUCCESS (0x0)", but the delivery fails due to invalid address.
Email sent to outside addresses (eg, gmail.com) succeeds, but internal mail fails.
The error appears to be caused by an incorrect administrative group being assigned to the recipient [see attached]. This occurs both at the command-line with openchangeclient and when attempting to mail through evolution using the evolution-mapi plugin.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup Exchange MAPI account using Evolution
2. Execute `openchangeclient -f /home/localuser/.evolution/mapi-profiles.ldb -S --to=another_user@same_domain.com --subject "Subject of test message" --body "Body of test message"`
3. View reject notice from Exchange server
Emails sent to internal (same domain as Exchange server) accounts fail due to invalid address
Emails sent to internal accounts are delivered successfully
Attachment contains sender/receiver account info from `openchangeclient --userlist`, diag info from the Exchange rejection email, and the data-dump/debug-output of the email send command that resulted in the reject.
UPDATE: If the user is in the SAME administrative group, delivery succeeds. This error ONLY occurs if the recipient is in a DIFFERENT administrative group.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.
More information and reason for this action is here:
I can confirm that this currently exists in Fedora 11, and Fedora 12 beta.
Also, I've noticed no difference between administrative groups. For instance, I cannot even send mail from myself to myself (on the domain). Can send mail off the domain perfectly fine.
Confirm this one on Fedora 11 with evolution-mapi 0.26.2 and evolution-exchange 2.26.3.
(In reply to comment #2)
> This bug appears to have been reported against 'rawhide' during the Fedora 11
> development cycle.
> Changing version to '11'.
Since this still exists in 12 (comment #3) should the version be bumped to 12?
Im confirm: Still exists on Fedora 12. This bug make this improvement useless.
Resolved upstream. See http://trac.openchange.org/ticket/125 for the upstream bug report and fix.
Probably easiest just to upgrade to 0.9, which I guess will drop in as part of Fedora 13.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
(In reply to comment #7)
> Resolved upstream. See http://trac.openchange.org/ticket/125 for the upstream
> bug report and fix.
> Probably easiest just to upgrade to 0.9, which I guess will drop in as part of
> Fedora 13.
I can confirm that this does seem to be resolved in F13
Thanks for the followup. Closing this as fixed.