Ubuntu
evolution package

evolution expanding exchange aliases.

Bug #83500 reported by pablort
2
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Undecided
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Evolution is expanding exchange aliases since 2.9.5 when a message is sent and not by user request.

Package: evolution
Version: 2.9.6-0ubuntu1

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you explain what "expending exchange aliases" is about? Is that evolution-exchange specific?

Changed in evolution:
assignee: nobody → desktop-bugs
status: Unconfirmed → Needs Info
Revision history for this message
pablort (pablort) wrote : Re: [Bug 83500] Re: evolution expanding exchange aliases.

I believe it is.

Do you know when you create a multiple address alias like:
<email address hidden> -> <email address hidden>, <email address hidden>, <email address hidden>,
<email address hidden>

When I try sending an email to '<email address hidden>' right after I press the
send button, evolution
(or evolution-exchange, im not really sure who's doing it) expands it (like
an inline alias expansion) to
"<email address hidden>, <email address hidden>, <email address hidden>, <email address hidden>".

Got it ?

On 2/6/07, Sebastien Bacher <email address hidden> wrote:
>
> Could you explain what "expending exchange aliases" is about? Is that
> evolution-exchange specific?
>
> ** Changed in: evolution (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
> --
> evolution expanding exchange aliases.
> https://launchpad.net/bugs/83500
>

Revision history for this message
Sebastien Bacher (seb128) wrote :

That doesn't look like a bug. The alias name you are using has no reason to be used to the sent mail, replacing it by the correct list of emails looks like the correct behaviour. What is your problem with that?

Revision history for this message
Daniel Holbach (dholbach) wrote :

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.

Changed in evolution:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.