swinog

swinog@lists.swinog.ch

3 participants
2927 discussions

[misc] Research project on blacklists
by Anushah Hossain 16 Jul '19

16 Jul '19

Hi everyone, I'm a researcher at UC Berkeley and the International Computer Science Institute. My colleagues and I are working on evaluating and improving the accuracy of blacklists. As part of this work, we'd like to hear from you about the blacklists you currently use, what you perceive as their strengths and weaknesses, and any thoughts you have on how they might be improved. We've prepared an anonymous survey where you can share your views: https://berkeley.qualtrics.com/jfe/form/SV_200mg5hnQiAOgUl If you have five to ten minutes free today to fill it out, I would greatly appreciate your help! Thank you, and please don't hesitate to respond to me with comments or questions. Best, Anushah -- Anushah Hossain, PhD Student Energy and Resources Group, UC Berkeley

1 0

Call for presentations and RIPE 79
by Franziska Lichtblau 15 Jul '19

15 Jul '19

Dear colleagues, Please find the CFP for RIPE 79 below or at: https://ripe79.ripe.net/submit-topic/cfp/. The deadline for submissions is *16 August 2019*. Please also note that speakers do not receive any extra reduction or funding towards the meeting fee at the RIPE Meetings. However, on an individual basis, participants can apply for a RIPE Fellowship or RACI, see the "Speakers" paragraph in CFP for more information. Kind regards, Franziska Lichtblau RIPE PC Chair https://ripe79.ripe.net/ripe-pc/ ---------------------------------------------------------------------------- Call for Presentations A RIPE Meeting is an open event where Internet Service Providers, network operators and other interested parties get together. Although the meeting is mostly technical, it is also a chance for people to meet and network with others in their field. *RIPE 79 will take place from 14-18 October in Rotterdam, The Netherlands* The RIPE Programme Committee (PC) is now seeking content proposals from the RIPE community for the plenary sessions, BoFs (Birds of a Feather sessions), panels, workshops, tutorials and lightning talks at RIPE 79. See the full descriptions of the different presentation formats: https://ripe79.ripe.net/submit-topic/presentation-forma ts/ Proposals for plenary sessions, BoFs, panels, workshops and tutorials must be submitted for full consideration no later than *16 August 2019*. Proposals submitted after this date will be considered depending on the slots still available in the programme. The PC is looking for presentations covering the topics of network engineering and operations, including but not limited to: - IPv6 deployment - Managing IPv4 scarcity - Data centre technologies - Network and DNS operations - Internet governance and regulatory practices - Network and routing security - Content delivery - Internet peering and mobile data exchange - Connected Things (aka. Internet of Things - IoT) _____________________________________________________ Speakers _____________________________________________________ Presenters, RIPE Working Group Chairs and the RIPE Programme Committee are required to cover their own costs to attend a RIPE Meeting (meeting ticket, travel and accommodation). We have various ticket options available depending on your needs. Please note that participants can apply for a RIPE Fellowship or RACI, on an individual basis, to develop their professional or academic career. For more information, please visit: https://www.ripe.net/participate/ripe/ripe-fellowship https://www.ripe.net/participate/ripe/raci In extraordinary circumstances, the RIPE Chair can waive the meeting fee for presenters. These requests are dealt with on a case-by-case basis via pc(a)ripe.net. _____________________________________________________ Submissions _____________________________________________________ Presenters should be clear on whether they wish to submit a presentation for a plenary or working group (WG) session. At present, most working groups will solicit policy proposals, discussion points or other content directly via their mailing lists. If you’re not sure what kind of session you should be presenting at, please visit: https://ripe79.ripe.net/plenary-or-wg/ RIPE Meeting attendees are quite sensitive to keeping presentations non- commercial, and product marketing talks are strongly discouraged. Repeated audience feedback shows that the most successful talks focus on operational experience, research results, or case studies. For example, presenters wishing to describe a commercial solution should focus on the underlying technology and should not attempt a product demonstration. Presenters should indicate how much time they will require. In general, the time allocated for the different presentation formats is as follows: - Plenary presentations: 20-25 minutes presentation with 5-10 minutes discussion - Tutorials: up to two hours (Monday morning) - Workshops: one hour (during evening sessions) to two hours (Monday morning) - BoFs: approximately one hour (during evening sessions) - Lightning talks: 10 minutes in total for both the presentation and any discussion The following general requirements apply: - Proposals must be submitted using the meeting submission system, https://ripe79.ripe.net/submit-topic/ - Lightning talks should also be submitted using the meeting submission system (https://ripe79.ripe.net/submit-topic/) and can be submitted any time up to and including the meeting week. The allocation of lightning talks will be announced on short notice, in some cases on the same day but often one day prior to the time slot allocated. - Presenters who propose a panel or BoF are encouraged to include speakers from several (perhaps even competing) companies and/or a neutral facilitator. - All presentation proposals will only be considered by the PC if they contain at least draft presentation slides (slides may be updated later on). For panels, proposals must contain a clear description, as well as the names of invited panellists, presenters and moderators. _____________________________________________________ Diversity and Inclusion - On-Site Childcare and the RIPE _____________________________________________________ Meeting Code of Conduct _____________________________________________________ Did you know that RIPE Meetings now have on-site childcare? You can reserve a spot for your child (age 6 months - 10 years) during the registration process for the meeting. Childcare places are limited, so please be quick to reserve a spot for your child while registering for the meeting. More information at: https://ripe79.ripe.net/on-site/on-site-childcare/ Ensuring that RIPE Meeting values are upheld and that attendees experience a professional, respectful and safe meeting is a priority. Please do read the RIPE Meeting Code of Conduct: https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… _____________________________________________________ If you have any questions or requests concerning content submissions, please email pc(a)ripe.net. -- Franziska Lichtblau, Forschungsgruppe Internet Architecture (INET) Max-Planck-Institut für Informatik, Campus E14, 66123 Saarbrücken E1 4 - Raum 514 fon +49 681 9325 3514 mobil: +49 176 63897173 gpg-fp: 4FA0 F1BC 8B9A 7F64 797C 221C C6C6 2786 91EC 5CD5

1 0

bluewin & DNSNULL
by Andreas Fink 11 Jul '19

11 Jul '19

Does any one have a clue what DNSNULL means in the following context of a mail delivery error? <....(a)bluewin.ch <mailto:claudine.beaud@bluewin.ch>> (mx-v02.bluewin.ch <http://mx-v02.bluewin.ch/>: 554 mxbw.lb.bluewin.ch <http://mxbw.lb.bluewin.ch/> vim dzmsp-mxin12.bluewin.ch <http://dzmsp-mxin12.bluewin.ch/> Swisscom AG IP: 79.134.251.203, You are not allowed to send us mail. Please see DNSNULL if you feel this is in error)Reporting-MTA: dns; mail.fink.org <http://mail.fink.org/> Arrival-Date: Thu, 11 Jul 2019 11:19:58 +0200 ... Andreas Fink ------------------------------------------------------------------ Paradieshofstrasse 101, 4054 Basel, Switzerland andreas(a)fink.org <mailto:andreas@fink.org> https://www.fink.org <https://www.fink.org/> Mobile: +41-78-6677333 Office: +41-61-6666330 Home: +41-61-6666345 Skype: andreasfink Jabber/XMPP: andreas(a)fink.org <mailto:andreas@fink.org> ICQ: 8239353 Twitter: @kiwi66 PGP Key: https://www.fink.org/FILES/afink-pgp.asc ------------------------------------------------------------------

3 2

Re: [swinog] swinog Digest, Vol 174, Issue 3
by Andreas Fink 11 Jul '19

11 Jul '19

Except that this is not applicable. In my case my mailserver is not hosted at Swisscom but on my own infrastructure, is on the same IP since years, has proper MX records and reverse DNS entries and has delivered email to the same bluewin customer yesterday successfully. Only the reply on that receiver today which I received and replied again got rejected. And the response is cryptic to me. And if you mail to abuse(a)bluewin.ch <mailto:abuse@bluewin.ch> you get the same error... So who is this famous DNSNULL I should contact? > On 11 Jul 2019, at 13:49, Florin sfetea <f_sfetea(a)yahoo.com> wrote: > > See https://community.swisscom.ch/t5/E-Mail/Bluewin-akzeptiert-E-Mails-von-eige… <https://community.swisscom.ch/t5/E-Mail/Bluewin-akzeptiert-E-Mails-von-eige…> > > > Beste Grüsse, Regards si s-auzim de bine > Florin Sfetea > > From: swinog-request(a)lists.swinog.ch <mailto:swinog-request@lists.swinog.ch> > Sent: Thursday, July 11, 2019 12:00 > To: swinog(a)lists.swinog.ch <mailto:swinog@lists.swinog.ch> > Subject: swinog Digest, Vol 174, Issue 3 > > Send swinog mailing list submissions to > swinog(a)lists.swinog.ch <mailto:swinog@lists.swinog.ch> > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog <http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog> > or, via email, send a message with subject or body 'help' to > swinog-request(a)lists.swinog.ch <mailto:swinog-request@lists.swinog.ch> > > You can reach the person managing the list at > swinog-owner(a)lists.swinog.ch <mailto:swinog-owner@lists.swinog.ch> > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of swinog digest..." > > > Today's Topics: > > 1. bluewin & DNSNULL (Andreas Fink) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 11 Jul 2019 11:32:38 +0200 > From: Andreas Fink <afink(a)list.fink.org <mailto:afink@list.fink.org>> > To: "swinog(a)swinog.ch <mailto:swinog@swinog.ch>" <swinog(a)swinog.ch <mailto:swinog@swinog.ch>> > Subject: [swinog] bluewin & DNSNULL > Message-ID: <75DA5D85-1A68-4D10-94B8-6237FD9D54DB(a)list.fink.org <mailto:75DA5D85-1A68-4D10-94B8-6237FD9D54DB@list.fink.org>> > Content-Type: text/plain; charset="us-ascii" > > > Does any one have a clue what DNSNULL means in the following context of a mail delivery error? > > > > <....(a)bluewin.ch <http://bluewin.ch/> <mailto:claudine.beaud@bluewin.ch <mailto:claudine.beaud@bluewin.ch>>> (mx-v02.bluewin.ch <http://mx-v02.bluewin.ch/> <http://mx-v02.bluewin.ch/ <http://mx-v02.bluewin.ch/>>: 554 mxbw.lb.bluewin.ch <http://mxbw.lb.bluewin.ch/><http://mxbw.lb.bluewin.ch/ <http://mxbw.lb.bluewin.ch/>> vim > dzmsp-mxin12.bluewin.ch <http://dzmsp-mxin12.bluewin.ch/> <http://dzmsp-mxin12.bluewin.ch/ <http://dzmsp-mxin12.bluewin.ch/>> Swisscom AG IP: 79.134.251.203, You are not allowed > to send us mail. Please see DNSNULL if you feel this is in error)Reporting-MTA: dns; mail.fink.org <http://mail.fink.org/> <http://mail.fink.org/ <http://mail.fink.org/>> > Arrival-Date: Thu, 11 Jul 2019 11:19:58 +0200 > ... > > > > Andreas Fink > ------------------------------------------------------------------ > Paradieshofstrasse 101, 4054 Basel, Switzerland > andreas(a)fink.org <mailto:andreas@fink.org> <mailto:andreas@fink.org <mailto:andreas@fink.org>> https://www.fink.org <https://www.fink.org/> <https://www.fink.org/ <https://www.fink.org/>> > Mobile: +41-78-6677333 Office: +41-61-6666330 Home: +41-61-6666345 > Skype: andreasfink Jabber/XMPP: andreas(a)fink.org <mailto:andreas@fink.org> <mailto:andreas@fink.org <mailto:andreas@fink.org>> ICQ: 8239353 > Twitter: @kiwi66 PGP Key: https://www.fink.org/FILES/afink-pgp.asc <https://www.fink.org/FILES/afink-pgp.asc> > ------------------------------------------------------------------ > > > > > >

2 2

Re: [swinog] swinog Digest, Vol 174, Issue 3
by Florin sfetea 11 Jul '19

11 Jul '19

See https://community.swisscom.ch/t5/E-Mail/Bluewin-akzeptiert-E-Mails-von-eige… Beste Grüsse, Regards si s-auzim de bine Florin Sfetea From: swinog-request(a)lists.swinog.ch Sent: Thursday, July 11, 2019 12:00 To: swinog(a)lists.swinog.ch Subject: swinog Digest, Vol 174, Issue 3 Send swinog mailing list submissions to swinog(a)lists.swinog.ch To subscribe or unsubscribe via the World Wide Web, visit http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog or, via email, send a message with subject or body 'help' to swinog-request(a)lists.swinog.ch You can reach the person managing the list at swinog-owner(a)lists.swinog.ch When replying, please edit your Subject line so it is more specific than "Re: Contents of swinog digest..." Today's Topics: 1. bluewin & DNSNULL (Andreas Fink) ---------------------------------------------------------------------- Message: 1 Date: Thu, 11 Jul 2019 11:32:38 +0200 From: Andreas Fink <afink(a)list.fink.org> To: "swinog(a)swinog.ch" <swinog(a)swinog.ch> Subject: [swinog] bluewin & DNSNULL Message-ID: <75DA5D85-1A68-4D10-94B8-6237FD9D54DB(a)list.fink.org> Content-Type: text/plain; charset="us-ascii" Does any one have a clue what DNSNULL means in the following context of a mail delivery error? <....(a)bluewin.ch <mailto:claudine.beaud@bluewin.ch>> (mx-v02.bluewin.ch <http://mx-v02.bluewin.ch/>: 554 mxbw.lb.bluewin.ch <http://mxbw.lb.bluewin.ch/> vim dzmsp-mxin12.bluewin.ch <http://dzmsp-mxin12.bluewin.ch/> Swisscom AG IP: 79.134.251.203, You are not allowed to send us mail. Please see DNSNULL if you feel this is in error)Reporting-MTA: dns; mail.fink.org <http://mail.fink.org/> Arrival-Date: Thu, 11 Jul 2019 11:19:58 +0200 ... Andreas Fink ------------------------------------------------------------------ Paradieshofstrasse 101, 4054 Basel, Switzerland andreas(a)fink.org <mailto:andreas@fink.org> https://www.fink.org <https://www.fink.org/> Mobile: +41-78-6677333 Office: +41-61-6666330 Home: +41-61-6666345 Skype: andreasfink Jabber/XMPP: andreas(a)fink.org <mailto:andreas@fink.org> ICQ: 8239353 Twitter: @kiwi66 PGP Key: https://www.fink.org/FILES/afink-pgp.asc ------------------------------------------------------------------

1 0

*****SPAM***** Re: *****SPAM***** bluewin & DNSNULL
by Claudio Kuenzler 11 Jul '19

11 Jul '19

Spam detection software, running on the system "mail01.infiniroot.net", has identified this incoming email as possible spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Not sure about the bluewin severs, but my server sent your mail immediately to spam because of this: 8.5 URIBL_SBL Contains an URL's NS IP listed in the Spamhaus SBL blocklist [URIs: mail.fink.org] Might be the same or related to this. Content analysis details: (7.6 points, 7.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.0 HTML_MESSAGE BODY: HTML included in message 0.1 URIBL_SBL_A Contains URL's A record listed in the Spamhaus SBL blocklist [URIs: fink.org] 8.5 URIBL_SBL Contains an URL's NS IP listed in the Spamhaus SBL blocklist [URIs: fink.org] The original message was not completely plain text, and may be unsafe to open with some email clients; in particular, it may contain a virus, or confirm that your address can receive spam. If you wish to view it, it may be safer to save it to a file and open it with an editor.

1 0

Call for Presentations European Peering Forum 14 (EPF14) // SwiNOG
by Arnold Nipper 10 Jul '19

10 Jul '19

Dear Community This is the Call for Presentations European Peering Forum 14 (EPF14) AMS-IX, DE-CIX, LINX and Netnod are happy to host the 14th European Peering Forum (EPF) in Tallinn, Estonia from the 16th - 18th September 2019. The event will welcome up to 300 peering managers and coordinators from networks connected to the host Internet exchanges. Besides an interesting topical agenda, the three-day event accommodates room for attendees to meet on a one-to-one basis to discuss bilateral peering business opportunities. The programme committee will be looking for presentations and lightning talks related to peering and technical topics of interconnection. Your presentation should address * Interconnection Automation * Regional Peering * Interconnection / Peering Internet Governance and Regulatory Topics * Economic and Product Trends * Peering / Interconnection strategies * Interesting findings about Peering / Interconnection * 400GE and beyond Submissions =========== Presentations must be of a non-commercial nature. Product or marketing heavy talks are strongly discouraged. Submissions of presentations should be made to the programme committee <epf-pc(a)peering-forum.eu>. Please include: * Author's name and e-mail address * Presentation title * Abstract * Slides (if available) * Time requested (max. 30 minutes incl. Q&A) Deadlines ========= Presentation Abstract Deadline 15/07/2019 12:00 UTC Final Selection of Speakers 26/07/2019 Presentation Slides Submission Deadline 02/09/2019 12:00 UTC More information about the event and other activities around EPF14 may be found at * https://peering-forum.eu/ * https://www.facebook.com/groups/1486607564933665/ Best regards Arnold -- Arnold Nipper email: arnold(a)nipper.de mobile: +49 172 2650958

1 1

Fwd: Teilrevision GebV-ÜPF: Vernehmlassungsverfahren / Révision partielle OEI-SCPT; procédure de consultation / Revisione parziale OEm-SCPT; procedura di consultazione
by Roman Hochuli 03 Jul '19

03 Jul '19

FYI

1 0

Geldspielgesetz: Zugangssperren Q&A
by Benoit Panizzon 28 Jun '19

28 Jun '19

Hallo zusammen Nachdem ich ausgiebigen Kontakt mit Suissedigital hatte, hier noch ein paar Infos zusammengefasst, welche Euch vermutlich auch interessieren könnte. F: Wann muss dies umgesetzt sein? A: Die Behörden sind noch nicht so weit. Es gibt keine Liste von zu sperrenden Domains, welche am 1. Juli publiziert wird. Es wird vermutlich Herbst, bis eine erste Liste publiziert wird. F: Muss jeder ISP selber diese Stoppage hosten, auf welcher die Besucher der gesperrten Domains geleitet werden sollen? Wer bezahlt die Hosting Kosten? A: Nein, die Behörden hosten diese Seite bereits, um auch schnell Anpassungen am Text und den Informationen auf der Seite vornehmen zu können. In der technischen Dokumentation sei die IP Adressen zum Eintragen in die DNS Zonenfiles zu finden (ich habe diese nicht gefunden, Suissedigital konnte sie mir auf Anhieb nicht nennen, kennt die jemand?). ISP mit Bedenken betreffend dem Schutz der Privatspäre Ihrer Kunden, dürfen dies aber auch selber Hosten. Ein Template ist auf der Webseite der ESBK erhältlich. F: Werden die Emails mit den Sperrlisten irgendwann als Emails versendet oder nur umständlich als .eml Download angeboten? Wie erfährt man, wenn eine neue Liste publiziert wird? A: Vorgesehen war der Versand per Email, dies ist aber auf wenig Akzeptanz bei den Providern gestossen, daher werden die .eml Dateien der Emails als Work-Around zum Download angeboten. Nicht schön, hat 'Verbesserungspotential' (Text-Datei anstatt .eml). An eine Lösung für eine Notification über Updates der Liste wird gearbeitet. F: 99% der Casino Seiten benutzen SSL. Stimmt das SSL Cert der Sperrseite nicht, kriegt der Besucher nur eine Fehlermeldung und sieht so die Informationen warum die Seite gesperrt ist nicht. Wird mit der CA des Bundes daher gültige Zertifikate für alle gesperrten Domains generiert? A: Ja, dies ist ein Problem welches nicht gelöst ist. Es ist nicht vorgesehen, dass die Sperrseite ein gültiges Zertifikat haben soll und der Problematik dass die Browser dann eine Fehlermeldung anzeigen sind sich alle bewusst. Suissedigital ist froh um Tipps, wie man dieses Problem lösen könnte. F: Was passiert mit dem MX Einträgen zu diesen Casinos? Müssen wir sicherstellen dass Email noch funktioniert? Sprich die Original MX Einträge in die Zonenfiles kopieren? SPF Einträge auch? Oder könnte man ein 'Zentrales' Zonenfile generieren und die verschiedenen Hostnamen darauf zeigen lassen und der Bund betreibt dann einen SMTP Relaying Server der sicherstellt, dass Emails an die Casino Domain richtig weitergeleitet werden (und diese möglicherweise mit liest). A: An das Thema wurde noch gar nicht gedacht. Noch eine Bemerkung am Rande: Die meisten versendeten PDF Dokumente haben ungültige Links. Man hat dies bei der ESBK erst kürzlich bemerkt und werde diese Dokumente nochmals korrigiert versenden. :-) Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

11 12

Geldspielgesetz: Zugangssperren. Wirklich vom Volk so gewünscht?
by Benoit Panizzon 26 Jun '19

26 Jun '19

Hallo zusammen Ich darf mich mit der Aufforderung der Eidgenössische Spielbankenkommission und Suissedigial auseinandersetzen die gewünschten DNS Sperren bei uns per 1. Juli einzurichten. Es geht mir hierbei hauptsächlich um die technische Umsetzung, so dass der Wunsch der ESBK wirklich umgesetzt wird. * Muss der Traffic auf Port 53 intercepted werden, damit Kunden keine eigene DNS Server mehr betreiben können und nicht die DNS Server von Google und CloudFlare nutzen können? Wir möchten vor allem verhindert, dass durch diese Aktion unsere Kunden mehr zu Google & Co getrieben werden und diesen noch mehr Daten über ihr Nutzugsverhalten zur Verfügung stellen. * Wir setzen wir vom Bakom gewünscht DNSSEC Validierung ein. Woher erhalten wir gültige Keys für die DNS Zonen welche wir 'hijacken'? Suissedigital sagt mir, es gehe nur einzig darum, auf unseren 'Caching' DNS Server die genannten Domains zu sperren, damit die Kunden diese darüber NICHT resolven können. Alles andere sei nicht verlangt. Ich habe eingewendet, dass dies absolut nutzlos sei, da die Kunden sehr genau wissen, wie dies zu umgehen ist. Suissedigital wie auch Bakom stimmen mir hier zu. Suissedigital sagt mir aber diese DNS Sperren seien bei einer Volksabstimmung Thema gewesen und das Volk habe, obwohl von allen Experten immer wieder darauf hingewiesen wurde, dass dies nicht funktioniert, sich für die Variante DNS Sperren entschieden. Interessant, ich müsste diese Volksabstimmung doch irgendwie mitgekriegt haben. Stimmt dies? Wie setzt ihr dies um? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________

5 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

swinog