From: Sam Ravnborg <sam@ravnborg.org>
To: Barebox List <barebox@lists.infradead.org>
Cc: Andrey Smirnov <andrew.smirnov@gmail.com>
Subject: Mails lost towards barebox mailing list [Was: [PATCH v4 0/25] at91: move ...]
Date: Mon, 1 Jan 2018 09:34:07 +0100 [thread overview]
Message-ID: <20180101083407.GA9460@ravnborg.org> (raw)
In-Reply-To: <20171231083407.GA16645@ravnborg.org>
Good morning - and happy new year!
Something seems fishy here.
Yesterday when trying to send out this patchset my ISP said
[PATCH 01/25] ... was spam and rejected the mail.
So I used an alternative smtp provider (also my POP3 provider).
And tested this towards my work mail - OK.
And when sent to barebox mailing list I got the cc: mails.
But I can see that no mails have reached the Barebox mailing
list for this or the following patch-set.
(Checked the web version) So something is not OK.
I tried again this morning, and mails sent using git send-email
will reach my work mail.
The mails leave my smtp provider, but are lost somewhere
on the way to the barebox mailing list.
Mail header looks like this (mail copied to myself):
From SRS0=M5gI=D3=ravnborg.org=sam@mail01.mxhotel.dk Sun Dec 31 10:43:50 2017
Return-Path: <SRS0=M5gI=D3=ravnborg.org=sam@mail01.mxhotel.dk>
Delivered-To: unknown
Received: from mail01.mxhotel.dk (91.221.196.236:995) by
localhost.localdomain with POP3-SSL; 31 Dec 2017 09:43:50 -0000
X-Original-To: sam@ravnborg.org
Delivered-To: sam@ravnborg.org
Received: from jupiter.lan (126.158-248-196.customer.lyse.net [158.248.196.126])
(Authenticated sender: sam@ravnborg.org)
by mail01.mxhotel.dk (Postfix) with ESMTPA id 74379194B34;
Sun, 31 Dec 2017 10:35:41 +0100 (CET)
X-Report-Abuse-To: abuse@mxhotel.dk
From: Sam Ravnborg <sam@ravnborg.org>
To: Sam Ravnborg <srn@skov.dk>
Cc: Sam Ravnborg <sam@ravnborg.org>
Subject: [PATCH 01/25] arm: at91: refactor lowlevel_init selection
Date: Sun, 31 Dec 2017 10:35:11 +0100
Message-Id: <20171231093511.8111-1-sam@ravnborg.org>
X-Mailer: git-send-email 2.12.0
In-Reply-To: <20171231083407.GA16645@ravnborg.org>
References: <20171231083407.GA16645@ravnborg.org>
Status: O
Content-Length: 15597
Lines: 478
If you have any hints what to look for, I would be glad to know.
Sam
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2018-01-01 8:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-31 8:34 [PATCH v4 0/25] at91: move reset vector to board code Sam Ravnborg
2018-01-01 8:34 ` Sam Ravnborg [this message]
2018-01-01 17:05 ` Mails lost towards barebox mailing list [Was: [PATCH v4 0/25] at91: move ...] Sam Ravnborg
2018-01-03 18:19 ` Sam Ravnborg
2018-01-01 14:16 ` [PATCH 02/25] arm: at91: drop unused at91sam9x5_lowlevel_init.c Sam Ravnborg
2018-01-01 14:16 ` [PATCH 03/25] arm: at91: add at91sam926x_board_init.h Sam Ravnborg
2018-01-01 14:16 ` [PATCH 04/25] arm: at91: code cleanup in at91sam926x_board_init Sam Ravnborg
2018-01-01 14:16 ` [PATCH 05/25] at91sam9263ek: move reset vector to board code Sam Ravnborg
2018-01-01 14:16 ` [PATCH 06/25] at91sam9261ek, at91sam9g10ek: " Sam Ravnborg
2018-01-01 14:16 ` [PATCH 07/25] pm9261: " Sam Ravnborg
2018-01-01 14:16 ` [PATCH 08/25] at91: drop unused at91sam9261_lowlevel_init Sam Ravnborg
2018-01-01 14:16 ` [PATCH 09/25] pm9263: move reset vector to board code Sam Ravnborg
2018-01-01 14:18 ` [PATCH 11/25] mmccpu: delete unused lowlevel_init Sam Ravnborg
2018-01-05 9:14 ` Sascha Hauer
2018-01-06 9:33 ` Sam Ravnborg
2018-01-01 14:18 ` [PATCH 12/25] mmccpu: move reset vector to board code Sam Ravnborg
2018-01-01 14:18 ` [PATCH 13/25] tny-a926x: delete unused tny_a9263_lowlevel_init.c Sam Ravnborg
2018-01-01 14:19 ` [PATCH 17/25] sama5d{3, 4}{xek, xplained}: move reset vector to board code Sam Ravnborg
2018-01-05 9:27 ` Sascha Hauer
2018-01-06 20:06 ` Sam Ravnborg
2018-01-01 14:19 ` [PATCH 18/25] at91sam9n12ek: " Sam Ravnborg
2018-01-01 14:19 ` [PATCH 19/25] at91sam9260ek, at91sam9g20ek: " Sam Ravnborg
2018-01-01 14:19 ` [PATCH 20/25] at91sam9m10g45ek, at91sam9m10ihd, pm9g45: " Sam Ravnborg
2018-01-01 14:19 ` [PATCH 21/25] animeo: " Sam Ravnborg
2018-01-01 14:19 ` [PATCH 22/25] telit-evk-pro3: " Sam Ravnborg
2018-01-01 14:19 ` [PATCH 23/25] dss11: " Sam Ravnborg
2018-01-01 14:19 ` [PATCH 24/25] at91rm9200ek: " Sam Ravnborg
2018-01-01 14:19 ` [PATCH 25/25] arm: at91: remove leftovers from moving reset code in mach-at91 Sam Ravnborg
2018-01-01 16:48 ` [PATCH 01/25] arm: at91: refactor lowlevel_init selection Sam Ravnborg
2018-01-05 9:24 ` Sascha Hauer
2018-01-01 16:48 ` [PATCH 10/25] usb-a926x: move reset vector to board code Sam Ravnborg
2018-01-01 16:48 ` [PATCH 14/25] tny-a926x: " Sam Ravnborg
2018-01-01 16:48 ` [PATCH 15/25] qil-a926x: " Sam Ravnborg
2018-01-01 16:48 ` [PATCH 16/25] haba-knx: " Sam Ravnborg
2018-01-04 17:12 ` [PATCH v4 0/25] at91: " Andrey Smirnov
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=20180101083407.GA9460@ravnborg.org \
--to=sam@ravnborg.org \
--cc=andrew.smirnov@gmail.com \
--cc=barebox@lists.infradead.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