On Sun, Jul 26, 2015 at 08:58:52AM +0200, Moritz Schmitt wrote:
> Thanks a lot for your very helpful reply!
>
> I implemented all the changes you suggested and now it works. My late
> reply is due to the fact that I needed to wait for another mail from
> outlook.com to see if everything works.
>
Dear Viktor,
Thanks a lot for your very helpful reply!
I implemented all the changes you suggested and now it works. My late
reply is due to the fact that I needed to wait for another mail from
outlook.com to see if everything works.
What I find a little odd about outlook.com's behavior is that
> [ Bcc'd to a contact Microsoft, who should be able to help get the
> issue addressed on that end at some point. The problem is a TLS
> stack at outlook.com that is poorly suited to opportunistic TLS.
> However, it is possible to work around this in Postfix, mostly
> by sticking to defaul
[ Bcc'd to a contact Microsoft, who should be able to help get the
issue addressed on that end at some point. The problem is a TLS
stack at outlook.com that is poorly suited to opportunistic TLS.
However, it is possible to work around this in Postfix, mostly
by sticking to default settings,
In reply to my earlier mail:
I kept experimenting a bit by using tcpdump. And the output suggested to
turn on IPv6 support (inet_protocols = all) in Postfix. Now the messages
from outlook.com get delivered but not without problems. Here are the
relevant log entries:
-
Jul 24 12:58:58 serving
