Re: Semi-OT: Exchange 2013 SMTP Callout

2013-06-16 Thread LuKreme
On Jun 14, 2013, at 9:10, Bernhard Schmidt wrote: > According to this threat: > > http://social.technet.microsoft.com/Forums/en-US/exchangesvrdeploy/thread/91c26fd2-aa0c-4006-9326-ece609bf4f67/ > > this is expected. I can hardly believe that. > > We do not have in-house experience with 2013 ye

Re: Semi-OT: Exchange 2013 SMTP Callout

2013-06-14 Thread Wietse Venema
Bernhard Schmidt: > This gets even worse when the mail has two recipients ... doesnotexist@ > does not exist, t1@ does... > > mail from: > 250 2.1.0 Sender OK > rcpt to: > 250 2.1.5 Recipient OK > rcpt to: > 250 2.1.5 Recipient OK > data > 354 Start mail input; end with . > test > . > 550 5.1.

Re: Semi-OT: Exchange 2013 SMTP Callout

2013-06-14 Thread Tomoyuki Murakami
On Fri, 14 Jun 2013 17:10:16 +0200, Bernhard Schmidt wrote: > This gets even worse when the mail has two recipients > ... doesnotexist@ does not exist, t1@ does... > > mail from: > 250 2.1.0 Sender OK > rcpt to: > 250 2.1.5 Recipient OK > rcpt to: > 250 2.1.5 Recipient OK > data > 354 Start

Semi-OT: Exchange 2013 SMTP Callout

2013-06-14 Thread Bernhard Schmidt
Hello, this is Semi-OT but since a lot of people run Postfix before Exchange I hope to find some knowledge here. Also heads-up :-) We have a couple of Exchange customers behind our frontend MX servers. We don't turn them up until they have configured their HBT servers to reject unknown recip