Version: 1.7.2 (using KDE 3.3.2, (3.1)) Compiler: gcc version 3.3.5 (Debian 1:3.3.5-6) OS: Linux (i686) release 2.6.10 When I switch to a different net, I am no longer able to use the same standard smtp server I use at home. That means I have to go into the network settings and switch the standard server to another smtp server which is willing to relay my mail. It would be easier if kmail simply tried the next mail relay on it's server list instead of complaining that the mail could not be sent using the first server on the list.
You can also have different SMTP servers for different identitites in KMail and in the composer switch identity depending on the net you are currently connected to. That works for me as I move between clients and offices. It would be great if you could try that and report back what you think about that feature.
On Saturday 12 March 2005 09:12, Matt Douhan wrote: > ------- You can also have different SMTP servers for different identitites > in KMail and in the composer switch identity depending on the net you are > currently connected to. How? I don't see any settings anywhere for this. Let me tell you straight away, that I am highly sceptical about this aproach. In my experience so far, automatic network detection and identification on linux, is notoriously difficult to set up. Personally I reconfigure my network manually with the etherconf package in Debian, every time I switch network. I think it is really unintuitive that you can add multiple smtp servers to the list, but no matter what you do, kmail will only ever use the standard one.
it does not always use the default one. do the following 1. add 2 or more SMTP servers as sendning accounts. 2. create 2 or more identitites, one per setting you want to use 3. in each identity go to the advanced tab and select the SMTP server you want to use for that identity. this means that a different SMTP server will be used depending on your identity. I have 9 identites, each one using a different SMTP server 1, for work using our work SMTP server 2 for home using my own local SMTP 3 for a customer site, using the customers SMTP and the list goes on. I hope this helps you achieve what you want, please report back success or failure.
Well.. I don't know if you want to call it a failure, but I completely fail see how your suggestions are meant to solve the problem. Do you have some way to automatically switch identities? From your answer, I can only see that you associate one identity with a particular smtp server. I could do this, but I don't see what good it would do me. I would then need some way to tell kmail that I want it to use another identity. If there is no way to set this up automatically, then you have simply changed the problem into switching identities manually instead of switching standard smtp server manually, and you are kind of back to where you started. I restate my request: If the first smtp server on the list fails, kmail should try the next one in line. I think this makes perfect sence. Otherwise why would you have a list to place multiple smtp servers in. You might as well put the outgoing mail server settings in the identity section and not bother with an outgoing mail server list under network settings at all.
the identities and the SMTP transport can be available in the composer window though, meaning you do not have to go into configure kmail -> network -> sending to change things. Ingo: what are your thoughts on this, is it feasible to try one SMTP after another until sending works or the list of servers run out?
Hmm.. Ok.. That probably would be a bit easier. But I still don't see why trying to go through the list for a working smtp server would be a bad thing. It would take a bit longer to send mail, but as soon as you find a working smtp, server kmail could remember that server, and try it first, for at least the remainder of the current session. I just think it would be easier if I didn't need to think about it.
Yes that is why I asked Ingo (KMail maintainer) his thoughts on the matter, if he thinks it makes sense it will be worked on as a wishlist item.
Otherwise my pleas will just be rigorously ignored? (As in closing this wishlist item..) ;)
I'm sorry, but this is a possible security risk. Say you use one transport which uses an unencrypted connection (for whatever reason) and one transport which uses an encrypted connection. Under no circumstances you want kmail to fallback to the unencrypted transport (unless you explicitely tell kmail to use it). We could probably make it easier to resend messages via another sending account by adding File->Send Queued Messages Via->. If you think that would help you then feel free to open a new wishlist item for this.
How about adding that option to the error message, so that when sending fails you are given the option of trying the other smtp servers in the error prompt. I would say that the error prompt is probably what annoys me the most about this. Anders
HEY! Why this bug has been closed as WONTFIX? That's somewhat too easy, isn't it? I suggest to add a "Cycle trough all servers" checkbox in the options. My life: - During weeks I'm studying in a big town and have ADSL. But my ISP allow me to send mails ONLY trough THEIRE SMPT server. - During week-end, I go back to home and have a 56k powered connection :) and I SHOULD use another SMTP server. It's boring to change settings everytimes. As well as it's boring to create X identities and synchronise them (eg. if I change the name of an identity I should change them to the other "mirrors"). As well as it's boring that for EVERY messages I should remember to think "Hey: Where am I? So, what the ISP name should I use?". The solution to "Cycle trough all servers if one is down, and remember the last used server" is not a must-have. If you want to prevent the user to make a security hole by activating it in the seldom cases of crypted/uncrypted servers, you still can add a small link on the left of the option which, once clicked, popup a "What's This?" message which teach the user. Sorry, but I think this bug should be reopenned. It have my vote.
This bug was closed as WONTFIX. Please don't reopen WONTFIX bugs unless you want to assign this to yourself (i.e., tell everyone you'll fix it). That doesn't mean you can't voice your concerns and ideas. You can persuade someone to implement the feature.
re #11: This is part of a more general wish for network profiles. Alternatively, it's part of a wish for automatic service detection. Both wishes already exist. In the next version you will be able to use File ->Send Queued Messages Using Transport ->Transport A ->Transport B ... to send messages with a specific SMTP server. Cycling through several SMTP servers won't be implemented by us and a corresponding patch won't be added to the official version of KMail. Therefore it doesn't make any sense to reopen this bug report.
> Please don't reopen WONTFIX bugs unless you want to assign this to yourself OK, that's noted. Sorry. > In the next version you will be able to use [...] But that doesn't solve the problem! That's a 4th workaround that, one more time, oblige us to take care of a think we don't want to take care at all. Choosing an SMTP server is one of the smallest interest task on the world. > Cycling through several SMTP servers won't be implemented Why? Is there any reason to do so, except the "sometimes make a security hole" one? Are we two alone people to be obliged to use different SMTP servers? Even if it's a simple option and that KMail explaine when it shouldn't be activated?
> Is there any reason to do so, except the "sometimes make a security > hole" one? You're joking, right? I don't want to have a tainted KMail which opens security wholes only because you're not able to manage your currently available SMTP server. I intentionally care for the server I'm using, and I want KMail to keep it's secure behavior. The solution mentioned by Ingo is a fair improvement, what you suggest isn't.
Again, may I suggest that an option is added to the error message itself so that you can select another server from there. You would still have to manually take action when it fails, so I don't see a security problem there, and it would be easier than having to go through a menu.
FWIW, in KDE 3.5 you can use File->Send Queued Messages Via->Some Transport to try another server if the first one failed. I have to use it myself from time to time and it's really not too much hassle IMO.