- Original Message -
> From: "Christoffer Hansen"
> On 30/07/2019 01:03, Dan Hollis wrote:
>> Jul 29 09:47:27 yuri sendmail[14067]: x6TGlQe4014062:
>> to=, ctladdr=
>> (500/500), delay=00:00:01, xdelay=00:00:01, mailer=esmtp92,
>> relay=amazon-smtp.amazon.com. [207.171.188.4], dsn=5.1.1,
On Tue, Jul 30, 2019 at 1:20 PM Christoffer Hansen
wrote:
> Imagine ARIN did a take from RIPE NCC [Policy Proposal Idea?] and a
> policy came into effect of validating ALL 'OrgAbuseEmail' objects listed
> in the ARIN database.
Just to be precise, such a policy (2019-04) is still in a discussion
On 30 Jul 2019, at 6:44 AM, Scott Christopher
mailto:s...@ottie.org>> wrote:
On 30/07/2019 11:59, Chris Knipe wrote:
Then update your ARIN records to reflect that. Fully agree with Dan on
this one.
Imagine ARIN did a take from RIPE NCC [Policy Proposal Idea?] and a
policy came into effect of
On Tue, Jul 30, 2019 at 2:15 AM Mel Beckman wrote:
> So why not just say so?
Because at the times of USENIX the very next reply to such a message
would've been "what are the steps to reproduce your problem".
--
Töma
On 30/07/2019 13:56, Robert McKay wrote:
> Even if it existed it would just be an autoresponder telling you that
> your email wasn't read and to go resubmit the report on their website.
Both yes and now. See below:*
"""
We are sorry to hear that you received unwanted email through Amazon SES.
On 2019-07-30 10:59, Chris Knipe wrote:
On Tue, Jul 30, 2019 at 11:45 AM Scott Christopher
wrote:
Dan Hollis wrote:
RCPT To:
<<< 550 #5.1.0 Address rejected.
550 5.1.1 ... User unknown
DATA
<<< 503 #5.5.1 RCPT first
Try j...@amazon.com
--
S.C.
Then update your ARIN records to
On 30/07/2019 01:03, Dan Hollis wrote:
> Jul 29 09:47:27 yuri sendmail[14067]: x6TGlQe4014062:
> to=, ctladdr=
> (500/500), delay=00:00:01, xdelay=00:00:01, mailer=esmtp92,
> relay=amazon-smtp.amazon.com. [207.171.188.4], dsn=5.1.1, stat=User unknown
... :wondering: Works fine for me. If sending
I thought it was already a requirement that the POC info had to be validated
once a year and accurate?
> On Jul 30, 2019, at 6:44 AM, Scott Christopher wrote:
>
> Christoffer Hansen wrote:
>
>>> On 30/07/2019 11:59, Chris Knipe wrote:
>>>
>>> Then update your ARIN records to reflect that.
Christoffer Hansen wrote:
> On 30/07/2019 11:59, Chris Knipe wrote:
>
> > Then update your ARIN records to reflect that. Fully agree with Dan on
> > this one.
> >
>
> Imagine ARIN did a take from RIPE NCC [Policy Proposal Idea?] and a
> policy came into effect of validating ALL
On 30/07/2019 11:59, Chris Knipe wrote:
> On Tue, Jul 30, 2019 at 11:45 AM Scott Christopher wrote:
>> Dan Hollis wrote:
>>> >>> RCPT To:
>>> <<< 550 #5.1.0 Address rejected.
>>> 550 5.1.1 ... User unknown
>>> >>> DATA
>>> <<< 503 #5.5.1 RCPT first
>>
>> Try jeff () amazon
>>
> Then update your
On Tue, Jul 30, 2019 at 11:45 AM Scott Christopher wrote:
> Dan Hollis wrote:
>
> > >>> RCPT To:
> > <<< 550 #5.1.0 Address rejected.
> > 550 5.1.1 ... User unknown
> > >>> DATA
> > <<< 503 #5.5.1 RCPT first
>
> Try j...@amazon.com
>
> --
> S.C.
>
Then update your ARIN records to reflect that.
Dan Hollis wrote:
> >>> RCPT To:
> <<< 550 #5.1.0 Address rejected.
> 550 5.1.1 ... User unknown
> >>> DATA
> <<< 503 #5.5.1 RCPT first
Try j...@amazon.com
--
S.C.
12 matches
Mail list logo