Bug 223686 - Automatic selection of SMTP server depending on location
Summary: Automatic selection of SMTP server depending on location
Status: REPORTED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.3
Platform: Ubuntu Unspecified
: NOR wishlist
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-21 15:47 UTC by Aldoo
Modified: 2010-01-21 15:47 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aldoo 2010-01-21 15:47:51 UTC
Version:            (using KDE 4.3.4)
Installed from:    Ubuntu Packages

(this wish concerns both kmail and network-manager integration)

The problem:

I own a laptop and use many mail accounts from several physical locations and networks.

Considering that
- SMTP servers hosted by an ISP only work from the network of the ISP,
- SMTP servers hosted by email providers only work for their email adresses (in the "from" field), and
- most ISPs block all SMTP servers except their own,

currently, when I want to send an e-mail from kmail, I have to manually select the SMTP server depending on the situation, because the only thing kmail proposes is tying a SMTP account to an identity (or to an incoming mail account).

But it is clear that in a lot of cases, choosing the SMTP server (or another outgoing method), should rather depend on the location/network.

I think this situation is common enough among laptop users and deserves some well integrated UI in the KDE desktop.


The solution I propose:

It should be made possible to add more rules in kmail for the selection of the SMTP server, in particular one that would check what current network the computer is connected to.
This could be done by adding a field for the preferred SMTP server in the data associated to a network in knetworkmanager (or the network-manager plasmoid).

(I am actually surprised it hasn't already been done or even proposed in this bug tracker... Did I miss something?)