Absender-Email Adresse kann im Outlook nicht gewählt werden

[Dreamoffice]

Hallo Gemeinde

Ich habe meine Mailstation und den Mailserver eingerichtet um von meinem Provider Email zu empfangen und zu versenden. Ich frage mit der Mailstation 2 Email-Konten über POP3 ab. Das funktioniert. Ich habe im Outlook ein Konto angelegt in dem ich die beiden Posteingang-Ordner der POP3 Konten sehe und die Emails auch beantworten kann.

DOCH beim beantworten wird die Email immer mit der Standard-Emailadresse aus ROUNDCUBE verschickt. Wie kann ich das machen das als Absender-Adresse die Adresse verwendet wird an welche die Email ursprünglich auch geschickt wurde?
In Roundcube kann ich die verschiedenen SMTP Server wählen aber in Outlook habe ich die Auswahl nicht.

-Ich habe im Mailserver SMTP aktiviert. (sonst kommt Fehlermeldung in Roundcube)
-Bei Aliasname ist der User drin der Zugriff haben soll.
-Bei IMAP/POP3 sind alle Haken drin.

-In Roundcube sind die 2 SMTP Server angelegt und funktionieren auch
-In Roundcube kann ich beim Antworten die Absender Adresse wählen, In Outlook nicht WARUM???? und wir bekomme ich das hin

Vielen Dank schon mal

Gruss Dreamoffice

 

[Dreamoffice]

Gedankengang...

wenn ich im Outlook Emails über die Mailstation verschicken will und das mit verschiedenen Asendern brauche ich dann für jede Emailadresse einen extra account in der Mailstation?

 

[jahlives]

Kurz und bündig: nein

 

[Basalt]

I have same situation, tried Outlook but could not get the "identities" to work the way I want.
Now I am using Thunderbird, when replying, it automatically selects the same "From:" address as the original "To:" (i.e. TB selects the correct identity)
I am using the same SMTP Server of my ISP for both identities, my ISP allows me to send e-mails with any "From:".

Note that specifying an SMTP Server in Roundcube does not mean you can see it in another e-mail client (like Outlook or TB).

For sake of easier maintenance, I use the SMTP Relay function of Synology's Mail Server, so I only have to specify my ISP's login details there once, and not in every mail client.

Best regards,
Erik

 

[jahlives]

For sake of easier maintenance, I use the SMTP Relay function of Synology's Mail Server, so I only have to specify my ISP's login details there once, and not in every mail client.

and what happens if you send a mail from a domain which has a strict SPF in place? Or if this domains uses dkim or some other signing method? In that case mails you sent via your DS resp your provider's SMTP will fail those checks and if the receiving side uses strict checks on those your mail would be considered spam.
I know it's some more work to do but one should always use the SMTP servers that belong to a given domain. Otherwise it depends on the goodwill of the receiving side if mail is considered spam or not

 

[Basalt]

and what happens if you send a mail from a domain which has a strict SPF in place? Or if this domains uses dkim or some other signing method? In that case mails you sent via your DS resp your provider's SMTP will fail those checks and if the receiving side uses strict checks on those your mail would be considered spam.
I know it's some more work to do but one should always use the SMTP servers that belong to a given domain. Otherwise it depends on the goodwill of the receiving side if mail is considered spam or not

Looks like I am a lucky guy, because I never encountered any issues with this.

Now I did some googling on the subject and found the Port25 website, where an e-mail address is listed. When you send an e-mail to that address, "a reply email will be sent back to you with an analysis of the message’s authentication status. The report will perform the following checks: SPF, SenderID, DomainKeys, DKIM and Spamassassin".

For the e-mails I sent with my Hotmail identity I got "Softerror" reported on SenderID and SPF check. Softerror means "The sender's ADMD believes the client was not authorized to inject or relay mail using the sender's DNS domain, but is unwilling to make a strong assertion to that effect".

Looks like I'd better fix this...

@jahlives: Thanks for pointing this out

Erik.