After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 621019 - Evolution always send e-mail through default smtp account
Evolution always send e-mail through default smtp account
Status: RESOLVED DUPLICATE of bug 336337
Product: evolution
Classification: Applications
Component: Mailer
2.28.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2010-06-08 20:26 UTC by zzpaf2006-spam
Modified: 2010-06-09 03:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description zzpaf2006-spam 2010-06-08 20:26:26 UTC 
Binary package hint: evolution

I have configured evolution with several mail accounts (4 POP3 accounts and a Google IMAP account).

When I try to send e-mail, I choose the correct account to send it. But, when I click send/receive button, I see all the mail sending through the same smtp server, that is the smtp server of the default (first POP3) account.

ProblemType: Bug
Architecture: i386
Date: Tue Nov 3 20:45:32 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release Candidate i386 (20091020.3)
Package: evolution 2.28.1-0ubuntu1
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: evolution
Uname: Linux 2.6.31-14-generic i686
Comment 1 André Klapper 2010-06-08 21:03:45 UTC 
How did you exactly find out that this happens?
Comment 2 Akhil Laddha 2010-06-09 03:43:10 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

*** This bug has been marked as a duplicate of bug 336337 ***