public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Rejected due to policy violations: Spam detected
Date: Wed, 08 Apr 2020 10:22:08 +0200	[thread overview]
Message-ID: <186ddc36-dfb8-ad19-316e-7ac21eb6d5f8@ipfire.org> (raw)
In-Reply-To: <e839ac2cc892bf70ef275c8131f3f00b97ee0a90.camel@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]

Hello Erik,

thanks for your reply.

> Hello Peter,
> 
> Am Mittwoch, den 08.04.2020, 09:19 +0200 schrieb Peter Müller:
>> Hello Erik,
>>
>> thanks for reporting this.
> Your welcome.
>>
>> Unfortunately, sqlite[.]org resolves to
>> 2600:3c00::f03c:91ff:fe96:b959, which
>> is currently blacklisted for sending spam. Apart from this, your
>> mails look
>> fine...
> Have no URLs somewhere in the mail.

Well, rspamd thinks you have. :-)

> 
>>
>> May I ask you to simply put brackets between the last dot in the
>> link, rendering
>> it unusable for machines? 
> Sure, you mean like this 
> URL/changes(.)html
> (can not post the URL so have shortend it) if so, it does not help
> since the same message appears again.

No, I meant like: http://www.example[.]com/changes.html

> 
>> I am sorry that this causes trouble again, and it
>> is _very_ interesting to see how much other open source projects care
>> about
>> their IP addresses' reputation. :-/
> Yeah really interesting :-( .

Indeed. We are telling IT people they should monitor their IP address' reputations
for 20 years by now, and apparently, most of them give a shit on this.

Thanks, and best regards,
Peter Müller

  reply	other threads:[~2020-04-08  8:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08  5:36 ummeegge
2020-04-08  5:45 ` Matthias Fischer
2020-04-08  6:52   ` ummeegge
2020-04-08  7:19     ` Peter Müller
2020-04-08  7:44       ` ummeegge
2020-04-08  8:22         ` Peter Müller [this message]
2020-04-08  8:50           ` ummeegge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=186ddc36-dfb8-ad19-316e-7ac21eb6d5f8@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox