Re: [swinog] Bluewin MX Protocol Errors
Many thanks to Marcel Gschwandl, we are still investigating together the root cause for these problems. For a workaround, try to disable TLS for @bluewin.ch and @bluemail.ch Postfix/main.cf smtp_tls_policy_maps = hash:/etc/postfix/tls_policy # cat tls_policy bluewin.ch none bluemail.ch none Bests, - Dan On 03.11.2015 09:43, Skwar Alexander wrote: > Hallo > > Ja, wir haben da seit dem 2. November auch ein paar. > > > > (ep01-zcs-prod ) 0 # egrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | > wc -l > 27 > (ep01-zcs-prod ) 0 # bzegrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' > /var/log/maillog.0.bz2 | wc -l > 71 > (ep02-zcs-prod ) 0 # egrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | > wc -l > 24 > (ep02-zcs-prod ) 0 # bzegrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' > /var/log/maillog.0.bz2 | wc -l > 63 > (ep03-zcs-prod ) 0 # egrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | > wc -l > 24 > (ep03-zcs-prod ) 0 # bzegrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' > /var/log/maillog.0.bz2 | wc -l > 64 > (ep04-zcs-prod ) 0 # egrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | > wc -l > 10 > (ep04-zcs-prod ) 0 # bzegrep > 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' > /var/log/maillog.0.bz2 | wc -l > 45 > > > Von insgesamt: > > (ep01-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog | wc -l > 140 > (ep01-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog.0.bz2 | wc -l > 602 > (ep02-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog | wc -l > 149 > (ep02-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog.0.bz2 | wc -l > 582 > (ep03-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog | wc -l > 122 > (ep03-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog.0.bz2 | wc -l > 625 > (ep04-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog | wc -l > 138 > (ep04-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' > /var/log/maillog.0.bz2 | wc -l > 584 > > > > > Wir nutzen: > > (ep01-zcs-prod ) 0 # pkg info | grep postfix > postfix-2.11.3_3,1 Secure alternative to widely-used Sendmail > > Grüsse > Alexander > > > > ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Bluewin MX Protocol Errors
We were able to identify and reliably reproduce the problem in out testing environment, it is related to the TLS-Offloading which interferes with the traffic in some cases and brakes the communication with sending RSET commands and not handling the responses correctly. Thanks to all who contacted me directly and provided their logs and inputs, it was most helpful. As a workaround we disabled StartTLS inbound again and are working on a fix so we can re-enable it as soon as possible. Regards Marcel ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Bluewin MX Protocol Errors
Hallo Ja, wir haben da seit dem 2. November auch ein paar. (ep01-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 27 (ep01-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 71 (ep02-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 24 (ep02-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 63 (ep03-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 24 (ep03-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 64 (ep04-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 10 (ep04-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 45 Von insgesamt: (ep01-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 140 (ep01-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 602 (ep02-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 149 (ep02-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 582 (ep03-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 122 (ep03-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 625 (ep04-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 138 (ep04-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 584 Wir nutzen: (ep01-zcs-prod ) 0 # pkg info | grep postfix postfix-2.11.3_3,1 Secure alternative to widely-used Sendmail Grüsse Alexander -- EveryWare AG Alexander Skwar Systems Engineer Zurlindenstrasse 52a CH-8003 Zürich tel: +41 44 466 60 00 fax: +41 44 466 60 10 mail: alexander.sk...@everyware.ch web: http://www.everyware.ch ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
Re: [swinog] Bluewin MX Protocol Errors
Hi I made this change as well. Let's see, what happens. But no TLS is not such a good solution… :) Cheers Alexander EveryWare AG Alexander Skwar Systems Engineer Zurlindenstrasse 52a CH-8003 Zürich tel: +41 44 466 60 00 fax: +41 44 466 60 10 mail: alexander.sk...@everyware.ch web: http://www.everyware.ch On 03.11.2015 10:23, Daniel Kamm wrote: Many thanks to Marcel Gschwandl, we are still investigating together the root cause for these problems. For a workaround, try to disable TLS for @bluewin.ch and @bluemail.ch Postfix/main.cf smtp_tls_policy_maps = hash:/etc/postfix/tls_policy # cat tls_policy bluewin.ch none bluemail.ch none Bests, - Dan On 03.11.2015 09:43, Skwar Alexander wrote: Hallo Ja, wir haben da seit dem 2. November auch ein paar. (ep01-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 27 (ep01-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 71 (ep02-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 24 (ep02-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 63 (ep03-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 24 (ep03-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 64 (ep04-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog | wc -l 10 (ep04-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=bounced.*Protocol error' /var/log/maillog.0.bz2 | wc -l 45 Von insgesamt: (ep01-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 140 (ep01-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 602 (ep02-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 149 (ep02-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 582 (ep03-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 122 (ep03-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 625 (ep04-zcs-prod ) 0 # egrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog | wc -l 138 (ep04-zcs-prod ) 0 # bzegrep 'relay=mxbw.lb.bluewin.ch.*status=sent' /var/log/maillog.0.bz2 | wc -l 584 Wir nutzen: (ep01-zcs-prod ) 0 # pkg info | grep postfix postfix-2.11.3_3,1 Secure alternative to widely-used Sendmail Grüsse Alexander ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
[swinog] SwiNOG #29 is day after tomorrow
Dear Participants and Speakers Please find general information about the SwiNOG #29 meeting below. Date: 05.11.2015 - Registration 08h15 - 09h15 Location: Gurtenpark, Bern. NEW Location: it's now closer to the station. Follow the signs. >From Bern main station you may take: - S-Bahn S3 Belp and exit at Wabern station - Tram 9 (Wabern) and exit at Gurtenbahn stop (http://www.bernmobil.ch/file/pdf_fahrplaene/141214/L9/ah_01009L_j15_B_1 _3.pdf?_=1446578381) ==> Then take the Gurtenbahn to the Gurtenpark. You DO NOT have to pay a fee, just tell you attend to the SwiNOG event. Don't throw away the ticket - you'll need it to get down. Map (Ground Station of the cable rail): https://goo.gl/maps/5uSKtgbianM2 Suggested trains from Geneva: 06h14 Zurich: 07h02 WIRELESS ACCESS During the meeting you have access to free WLAN! - SSID: MOBILE - Credentials will be printed on your badge - YOU are responsible for the security of your data, this WLAN is not encrypted! Many thanks to our sponsors! Juniper, Brocade, Cisco See you at SwiNOG #29! Simon Ryf SwiNOG Organisation ___ swinog mailing list swinog@lists.swinog.ch http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
