Bug 283442 - SMTP: Sending fails if SMTP authentification occurs with different SMTP user name than factual email address
Summary: SMTP: Sending fails if SMTP authentification occurs with different SMTP user ...
Status: RESOLVED FIXED
Alias: None
Product: kdepimlibs
Classification: Applications
Component: mailtransport (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-06 04:12 UTC by wuselwu
Modified: 2014-09-22 10:53 UTC (History)
2 users (show)

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 wuselwu 2011-10-06 04:12:07 UTC
Version:           4.7 (using KDE 4.7.1) 
OS:                Linux

This problem might be on the SMTP server side, but the setup worked in pre-Akonadi times. I just can't get it to work after the Akonadi switch.

It's a bit difficult to describe:

The german provider 1&1 provides several email adresses, let's call them "standard-mail@provider", "mail2@provider" and "mail3@provider" and so on. However, for all email adresses you have to use the same SMTP account where you authentificate with the user name "standard-mail@provider" and the corresponding password. 

Reproducible: Always

Steps to Reproduce:
That means in kmail I have set up the identities "mail2@provider" and "mail3@provider". For both I have, however, set up custom SMTP settings to use the 1&1 server and authenticate with "standard-mail@provider".

Actual Results:  
Whenever I try to send mail with one of those identities, a error popup says that the SMTP server rejects "mail2@provider" or "mail3@provider" as sender address ("invalid mail address"). However, for authentification purposes, the SMTP server should have been presented with the "standard-mail@provider" email address.

Expected Results:  
Mail sends flawlessly.
Comment 1 Laurent Montel 2011-10-06 08:02:54 UTC
mailtransport
Comment 2 wuselwu 2014-09-22 10:53:21 UTC
As I no longer have the problem, it seems to be fixed.