The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 2,726 other followers

Archive for the ‘Uncategorized’ Category

Als je 55 jaar of ouder bent: Gemeente Teylingen – Doorstroming woningen | Facebook

Posted by jpluimers on 2022/03/04

Helaas is de belangrijkste beperkende voorwaarde dit:

Ik ben een senior, maar laat geen eengezinswoning van Stek achter. Kan ik wel gebruik maken van voorrang voor senioren?

Wanneer u geen eengezinswoning van Stek of 4 kamerappartement in Noordwijk achterlaat, is het niet mogelijk voorrang te krijgen. Wel kunt u reageren op de woningen die op Huren in Holland Rijnland staan. Mochten er geen kandidaten zijn die via ons seniorenbeleid voorrang krijgen, gaan wij verder met de kandidatenlijst en maakt u dus alsnog kans!

Via [Archive.is] Gemeente Teylingen – Doorstroming woningen | Facebook:

Read the rest of this entry »

Posted in Uncategorized | Leave a Comment »

FD: Hoge Raad opent weg voor massaclaim woekerpolissen

Posted by jpluimers on 2022/02/13

For my link archive: [Archive] Hoge Raad opent weg voor massaclaim woekerpolissen

–jeroen

Posted in Uncategorized | Leave a Comment »

Een “Hyp4” aanduiding bij het Kadaster gaat over eigendom, niet over hyopotheek (daar is “Hyp3”) voor

Posted by jpluimers on 2022/02/04

Ik schrok even toen ik in een uittreksel van het kadaster de aanuiding “Hyp4 2228/40 Leiden” vond: was de hypotheek niet afbetaald?

Toch wel: de aanduiding “Hyp4” gaat over eigendommen, niet over hypotheken. Er was geen “Hyp3” aanduiding bij dit perceel, dus de hypotheek was afbetaald en doorgehaald bij het Kadaster.

–jeroen

Posted in Uncategorized | Leave a Comment »

gmail SMTP errors to help clean up your bounces list

Posted by jpluimers on 2022/01/19

From some of the logs:

   ----- Transcript of session follows -----
... while talking to alt1.gmail-smtp-in.l.google.com.:
>>> DATA
<<< 421-4.7.0 [###.###.###.###      15] Our system has detected that this message is
<<< 421-4.7.0 suspicious due to the very low reputation of the sending domain. To
<<< 421-4.7.0 best protect our users from spam, the message has been blocked.
<<< 421-4.7.0 Please visit
<<>> DATA
<<< 550-5.7.1 [###.###.###.###      12] Our system has detected that this message is
<<< 550-5.7.1 likely unsolicited mail. To reduce the amount of spam sent to Gmail,
<<< 550-5.7.1 this message has been blocked. Please visit
<<< 550-5.7.1  https://support.google.com/mail/?p=UnsolicitedMessageError
<<< 550 5.7.1  for more information. c184si14930209pfa.345 - gsmtp
554 5.0.0 Service unavailable

The ###.###.###.### are the outgoing WAN IP addresses of our SMTP server.

Basically filtering on .* Our system has detected that this message is helps clearing up a lot of bounce messages until I’ve found better black-lists.

Related:

  • [Wayback] “421-4.7.0” “Our system has detected that this message is” – Google Search
  • [Wayback] “550-5.7.1” “Our system has detected that this message is” – Google Search
    • [Wayback] How to Remove Your IP from the Gmail Blacklist – rackAID

      1. Why is Gmail Blocking My Emails?
      2. Authenticate Your Email
      3. Follow Gmail’s Best Practices
      4. Submit Gmail Blacklist Removal Form
      5. Waiting on the Gmail Blacklist Removal
      6. Get Removed from Gmail’s Blacklist

      421, “4.4.5”, Server busy, try again later.
      421, “4.7.0”, IP not in whitelist for RCPT domain, closing connection.
      421, “4.7.0”, Our system has detected an unusual rate of unsolicited mail originating from your IP address. To protect our users from spam, mail sent from your IP address has been temporarily blocked. Review our Bulk Senders Guidelines.
      421, “4.7.0”, Temporary System Problem. Try again later.
      421, “4.7.0”, TLS required for RCPT domain, closing connection.
      421, “4.7.0”, Try again later, closing connection. This usually indicates a Denial of Service (DoS) for the SMTP relay at the HELO stage.
      450, “4.2.1” The user you are trying to contact is receiving mail too quickly. Please resend your message at a later time. If the user is able to receive mail at that time, your message will be delivered. For more information, review this article.
      450, “4.2.1”, The user you are trying to contact is receiving mail at a rate that prevents additional messages from being delivered. Please resend your message at a later time. If the user is able to receive mail at that time, your message will be delivered. For more information, review this article.
      450, “4.2.1”, Peak SMTP relay limit exceeded for customer. This is a temporary error. For more information on SMTP relay limits, please contact your administrator or review this article.
      451, “4.3.0”, Mail server temporarily rejected message.
      451, “4.3.0”, Multiple destination domains per transaction is unsupported. Please try again.
      451, “4.4.2”, Timeout – closing connection.
      451, “4.5.0”, SMTP protocol violation, see RFC 2821.
      452, “4.2.2”, The email account that you tried to reach is over quota. Please direct the recipient to this article.
      452, “4.5.3”, Domain policy size per transaction exceeded, please try this recipient in a separate transaction.
      452, “4.5.3”, Your message has too many recipients. For more information regarding Google’s sending limits, review this article.
      454, “4.5.0”, SMTP protocol violation, no commands allowed to pipeline after STARTTLS, see RFC 3207.
      454, “4.7.0”, Cannot authenticate due to temporary system problem. Try again later.
      454, “5.5.1”, STARTTLS may not be repeated.
      501, “5.5.2”, Cannot Decode response.
      501, “5.5.4”, HELO/EHLO argument is invalid, please review this article.
      502, “5.5.1”, Too many unrecognized commands, goodbye.
      502, “5.5.1”, Unimplemented command.
      502, “5.5.1”, Unrecognized command.
      503, “5.5.1”, “EHLO/HELO first.
      503, “5.5.1”, MAIL first.
      503, “5.5.1”, RCPT first.
      503, “5.7.0”, No identity changes permitted.
      504, “5.7.4”, Unrecognized Authentication Type.
      530, “5.5.1”, Authentication Required. Learn more here.
      530, “5.7.0”, Must issue a STARTTLS command first.
      535, “5.5.4”, Optional Argument not permitted for that AUTH mode.
      535, “5.7.1”, Application-specific password required. Learn more here.
      535, “5.7.1”, Please log in with your web browser and then try again. Learn more here.
      535, “5.7.1”, Username and Password not accepted. Learn more here.
      550, “5.1.1”, The email account that you tried to reach does not exist. Please try double-checking the recipient’s email address for typos or unnecessary spaces. For more information, review this article.
      550, “5.2.1”, The email account that you tried to reach is disabled.
      550, “5.2.1”, The user you are trying to contact is receiving mail at a rate that prevents additional messages from being delivered. For more information, review this article.
      550, “5.4.5”, Daily sending quota exceeded. Learn more here.
      550, “5.4.5”, Daily SMTP relay limit exceeded for user. For more information on SMTP relay sending limits please contact your administrator or review this article.
      550, “5.7.0”, Mail relay denied.
      550, “5.7.0”, Mail Sending denied. This error occurs if the sender account is disabled or not registered within your G Suite domain.
      550, “5.7.1”, Email quota exceeded.
      550, “5.7.1”, Invalid credentials for relay.
      550, “5.7.1”, Our system has detected an unusual rate of unsolicited mail originating from your IP address. To protect our users from spam, mail sent from your IP address has been blocked. Review our Bulk Senders Guidelines.
      550, “5.7.1”, Our system has detected that this message is likely unsolicited mail. To reduce the amount of spam sent to Gmail, this message has been blocked. For more information, review this article.
      550, “5.7.1”, The IP you’re using to send mail is not authorized to send email directly to our servers. Please use the SMTP relay at your service provider instead. For more information, review this article.
      550, “5.7.1”, The user or domain that you are sending to (or from) has a policy that prohibited the mail that you sent. Please contact your domain administrator for further details. For more information, review this article.
      550, “5.7.1”, Unauthenticated email is not accepted from this domain.
      550, “5.7.1”, Daily SMTP relay limit exceeded for customer. For more information on SMTP relay sending limits please contact your administrator or review this article.
      552, “5.2.2”, The email account that you tried to reach is over quota.
      552, “5.2.3”, Your message exceeded Google’s message size limits. Please review our size guidelines.
      553, “5.1.2”, We weren’t able to find the recipient domain. Please check for any spelling errors, and make sure you didn’t enter any spaces, periods, or other punctuation after the recipient’s email address.
      554, “5.6.0”, Mail message is malformed. Not accepted.
      554, “5.6.0”, Message exceeded 50 hops, this may indicate a mail loop.
      554, “5.7.0”, Too Many Unauthenticated commands.
      555, “5.5.2”, Syntax error.

–jeroen

Posted in Uncategorized | Leave a Comment »

Het moment om Schiphol te laten krimpen is nu – Follow the Money – Platform voor onderzoeksjournalistiek

Posted by jpluimers on 2022/01/12

[Wayback/Archive] Het moment om Schiphol te laten krimpen is nu – Follow the Money – Platform voor onderzoeksjournalistiek

Via [Archive] Eric Smit on Twitter: “In Europa zijn boekwerken volgeschreven over de vraag hoe je een groeiende capaciteit tussen luchtvaartmaatschappijen verdeelt, maar is er nooit nagedacht over de consequenties van een afnemende capaciteit … via @ftm_nl” / Twitter

jeroen

Posted in Uncategorized | Leave a Comment »

 
%d bloggers like this: