There is rough consensus so that many mailing list manager software have
similar implementations. Details to be hashed out, bugs to be fixed, hairs to
be split, all the usual details remaining of course.
--srs
> On 22-Feb-2017, at 11:23 AM, Hans Petter Holen wrote:
>
>
>
>> On 21 February
On 21 February 2017 at 16:27, Suresh Ramasubramanian
wrote:
> The question before the house is ripe's mailing list software being
> configured to appropriately rewrite headers to support dmarc
>
>
As this is a topic that interests me in my day job, I tried to read up on
the IETF list on how to "
The question before the house is ripe's mailing list software being configured
to appropriately rewrite headers to support dmarc
--srs
> On 21-Feb-2017, at 7:15 AM, Gert Doering wrote:
>
> None of the working group chairs have a personal @ripe.net address.
>
> Gert Doering
>-- NetMas
I wouldn’t expect anyone to, but the entire “fix X on RIPE” ..
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
https://www.blacknight.com/
http://blacknight.blog/
Intl. +353 (0) 59 9183072
Direct Dial: +353 (0)59 9183090
Personal blog: https://michele.blog/
Some thoughts:
Hi,
On Tue, Feb 21, 2017 at 02:03:36PM +, Michele Neylon - Blacknight wrote:
> He doesn???t have a RIPE email address apparently .. so ..
None of the working group chairs have a personal @ripe.net address.
Gert Doering
-- NetMaster
--
have you enabled IPv6 on something today...?
S
Suresh
He doesn’t have a RIPE email address apparently .. so ..
Now why he doesn’t have a RIPE email address is probably another matter
entirely ☺
M
--
Mr Michele Neylon
Blacknight Solutions
Hosting, Colocation & Domains
https://www.blacknight.com/
http://blacknight.blog/
Intl. +353 (0) 59 9
DMARC policy compliance is something that RIPE needs to fix at their end –
ensuring that the mailing list manager rewrites headers appropriately.
Most mailing list manager software has already been rewritten to support this
by default, so unless RIPE NCC is using something heavily patched and
c
0 February 2017 at 6:36 AM
To: Suresh Ramasubramanian , denis
Cc:
Subject: Re: [anti-abuse-wg] an ISP can't do anything?
Hi Suresh
I was replying to a message on the DB-WG and got this response:
The message could not be delivered, the mail server at
idvmailin04.datev.com [193.27.49.132] said
postmaster role all that necessary.
--srs
From: denis
Date: Monday, 20 February 2017 at 6:36 AM
To: Suresh Ramasubramanian , denis
Cc:
Subject: Re: [anti-abuse-wg] an ISP can't do anything?
Hi Suresh
I was replying to a message on the DB-WG and got this response:
The message could n
Hi Suresh
I was replying to a message on the DB-WG and got this response:
The message could not be delivered, the mail server at
idvmailin04.datev.com [193.27.49.132] said:
<<< 554 5.7.1 Service unavailable; Sender address [ripede...@xs4all.nl]
blocked using dbl.webradar.datev.de; gesperrt vom
On 20-Feb-2017, at 2:22 AM, denis wrote:
>
> It seems like XS4ALL is not able to do anything about being blacklisted.
> Obviously the message about handling abuse is not getting through
It would help if you posted just what bounce and from where. XS4all has
historically been quite proacti
Hi, Denis,
It’s high time you turned the flaws of the current email system (the use of
reputation rating) to your advantage and got yourself an email account on a
domain that no ISP would risk to block.
Best regards,
Oleg
> On 20 Feb 2017, at 11:22, denis wrote:
>
> HI
>
> It seems like XS4
On Mon, 20 Feb 2017 11:22:26 +0100
denis wrote:
> HI
> It seems like XS4ALL is not able to do anything about being
> blacklisted. Obviously the message about handling abuse is not
> getting through
We need to also talk about the nature of abuse and as it is a community
shortcoming and comple
HI
It seems like XS4ALL is not able to do anything about being blacklisted.
Obviously the message about handling abuse is not getting through
cheers
denis
co-chair DB-WG
Original Message
Subject: RE: Feedback Werkingproduct (Email-Id: 6483239)
Date: 2017-02-20 09:51
Fro
14 matches
Mail list logo
