Goline Logo

Home

    About Us

      Services

      Solutions

      Systems Architecture

      Support

      FAQ

      News

      • Route RPKI validation April 1st, 2022
        RPKI is a security framework by which network owners can validate and secure the critical route updates or Border Gateway Protocol (BGP) announcements between public Internet networks. BGP is essentially the central nervous system of the Internet and one of its fundamental building blocks. The main function of BGP is to facilitate efficient routing between Autonomous Systems (AS), by building and maintaining the Internet routing table. The Internet routing table is effectively the navigation system of the Internet and without it, traffic would be unable to flow between its constituent networks. Unfortunately, routing equipment alone cannot distinguish between legitimate and malicious routing announcements,...
      • RIPE – Atlas Anchor February 17th, 2022
        We have become an even more integral part of the RIPE Atlas project by hosting an anchor, a device that allows for latency analysis of traffic between autonomous systems.https://atlas.ripe.net/probes/7073/RIPE Atlas anchors play an integral role in the RIPE Atlas network by acting both as enhanced RIPE Atlas probes with more measurement capacity, as well as regional measurement targets within the greater RIPE Atlas network. Anchors are able to perform many more measurements than a regular RIPE Atlas probe, and the large amount of data they collect is made available to everyone. In addition, anchors act as powerful targets that can...
      • MANRS June 20th, 2020
        GOLINE firmly believes in initiatives to protect networks, improve security and resilience of the global routing system. Therefore we decided to support the MANRS project and join as participants.Mutually Agreed Norms for Routing Security (MANRS) is a global initiative, supported by the Internet Society, that provides crucial fixes to reduce the most common routing threats. MANRS offers specific actions via four programs for Network Operators, Internet Exchange Points, CDN and Cloud Providers, and Equipment Vendors. Requirements for Participation Please read the full MANRS Actions document before applying. You can become a participant if you meet these requirements: You (or your company) support...

      Libraesva ESG: Message contained password-protected archive (workaround)

      Gianni Ricca Mail 22 June 2022

      Problema:
      Per default gli archivi ZIP protetti da password vengono bloccati con messaggio "Message contained password-protected archive"
      Risoluzione:
      Aggiungere una regola di "Allow" in System > Content Analysis > Attachment Filters > Archive Check Rules > Password Protected Archives

      ———-

      Problema:
      Le email vengono considerate Spam con messaggio ESVA_LOCAL_DMARC_FAIL_PNONE
      "DMARC failed: for internal domains policy "none" is treated as "quarantine""
      Risoluzione:
      La regola ESVA_LOCAL_DMARC_FAIL_PNONE scatta quando:
      nel campo header-from il mittente è un indirizzo email su un dominio protetto da Libraesva ESG
      la mail proviene dall'esterno;
      il dominio mittente ha pubblicato un record DMARC;
      il controllo dmarc fallisce.

      Dalla release 4.6, quando è pubblicato un record dmarc per uno dei domini protetti da Libraesva ESG, viene applicata la policy DMARC "quarantine" anche se la policy pubblicata è "none" in quanto per i domini ospitati da ESG i controlli antispoofing sono più restrittivi: https://docs.libraesva.com/libra-esva-4-6-released/#changes-in-v460

      Per risolvere il problema si può fare una di queste cose:
      1 Assicurarsi che le mail inviate dall'esterno con campo From su un dominio interno passino la validazione DMARC mediante allineamento con SPF o DKIM, ad esempio aggiungere la firma DKIM alle newsletter inviate da piattaforme di terzi;
      2 Rimuovere il record DMARC pubblicato sul dns;
      3 Usare whitelist puntuali per le mail che si desidera far passare.

      ———-

      Problema:
      Le email di un particolare dominio (es. Tiscali) non vengono accettate perchè il dominio è blacklistato,
      Risoluzione:
      Aggiungere una regola di "Override" per quel server SMTP in System > Mail Transport > Relay Configuration > SMTP Check Override

      ———-

      Problema:

      0 0 votes
      Article Rating
      Subscribe
      Notify of
      0 Comments
      Inline Feedbacks
      View all comments
      0
      Would love your thoughts, please comment.x
      ()
      x