Re: Cannot deliver message, decebal, kovoks, gmx.de en outlook.com
On Sat, Oct 27, 2018 at 03:27:43PM +0200, Cecil Westerhof wrote:
> Geert Stappers writes:
>
> > Na het lezen van "How to Report Bugs Effectively"
https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
> > zou in _dit geval_ het een goede stap zijn om
> > met e-mail headers van de e-mails in kwestie te komen.
>
> De headers:
> Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-oln040092066053.outbound.protection.outlook.com [40.92.66.53])
> by cloud01.kovoks.nl (Postfix) with ESMTPS id 0AF9C16876
> for <Cecil@decebal.nl>; Sat, 27 Oct 2018 14:01:26 +0200 (CEST)
> MIME-Version: 1.0
> From: <postmaster@outlook.com>
outlook.com
> To: <Cecil@decebal.nl>
> Date: Sat, 27 Oct 2018 12:01:25 +0000
> Content-Type: multipart/report; report-type=delivery-status;
> boundary="39adf581-00ef-4fb4-8c38-8f9bfd27e93a"
> X-MS-Exchange-Message-Is-Ndr:
> Content-Language: en-US
> Message-ID: <c5a43b7c-6fac-4d93-ab9d-2e206c70cd05@VE1EUR01HT197.mail.protection.outlook.com>
> In-Reply-To: <[🔎] 87ftwrk39a.fsf@munus.decebal.nl>
> References: <[🔎] 87ftwrk39a.fsf@munus.decebal.nl>
Die twee komen overeen met de Message-id
op https://lists.debian.org/debian-user-dutch/2018/10/msg00090.html
> Subject: Undeliverable: Hulp bij het up to date houden van packages
> Auto-Submitted: auto-replied
> X-MS-PublicTrafficType: Email
> X-MS-TrafficTypeDiagnostic: VE1EUR01HT197:
> X-Microsoft-Exchange-Diagnostics:
knip
> X-Exchange-Antispam-Report-CFA-Test:
knip
> X-Microsoft-Antispam-Message-Info:
knip
> X-Microsoft-Exchange-Diagnostics:
knip
> X-OriginatorOrg: outlook.com
> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Oct 2018 12:01:25.4183
> (UTC)
> X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
> X-MS-Exchange-CrossTenant-Network-Message-Id:
> 8b54e127-b41d-48cf-6ca5-08d63c03eb90
> X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1EUR01HT197
> X-spam: bounced
>
>
> Start van het uitgebreide antwoord:
> --39adf581-00ef-4fb4-8c38-8f9bfd27e93a
> Content-Type: multipart/alternative; differences=Content-Type;
> boundary="e5b9f67d-94e8-4b8f-a22d-b3cb0aed1321"
>
> --e5b9f67d-94e8-4b8f-a22d-b3cb0aed1321
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> gmx.net rejected your message to the following email addresses:
>
> tilda32@gmx.de<mailto:tilda32@gmx.de>
> Your message couldn't be delivered. The error returned by the email server =
> outside Office 365 suggests that the Internet's directory listing for the r=
> ecipient's email domain (the text after the "@" symbol in the recipient's e=
> mail address) doesn't exist or isn't set up correctly. A distinct and corre=
> ct listing for the recipient's domain must exist to determine where to send=
> the message. This can only be fixed by the recipient's email admin. To fix=
> the problem, contact the recipient by some other means (by phone, for exam=
> ple) and give them the error message below to give to their email admin to =
> fix.
>
> For Email Admins
> When Office 365 tried to send the message outside of Office 365 the externa=
> l email server returned the error below. This error was reported by an emai=
> l server outside Office 365 and it indicates that the Domain Name System (D=
> NS) mail exchanger (MX) record or A record for the recipient's domain doesn=
> 't exist or isn't set up correctly. To fix this contact the recipient's ema=
> il admin and ask them to work with their domain registrar (or Web host prov=
> ider) to properly set up a correct MX and A record for their domain.
>
> Only the recipient's email admin can fix this. Unfortunately, Office 365 su=
> pport won't be able to help with these kinds of externally reported errors.
>
>
>
> gmx.net gave this error:
> Remote server returned invalid or missing DNS MX or A record for recipient =
> domain -> 550 Requested action not taken: mailbox unavailable;invalid DNS M=
> X or A/AAAA resource record
>
>
>
> Diagnostic information for administrators:
>
> Generating server: VE1EUR01HT197.mail.protection.outlook.com
>
> tilda32@gmx.de
> gmx.net
> Remote Server returned '550 5.4.350 Remote server returned invalid or missi=
> ng DNS MX or A record for recipient domain -> 550 Requested action not take=
> n: mailbox unavailable;invalid DNS MX or A/AAAA resource record'
>
Ik heb een server waar ik succesvol naar tilda 32 AT gmx de kan mailen.
En ik heb een andere server, waar dat niet kan.
Ding wat me het meeste verbaast,
is hoe de mailserver van outlook.com in het spel is gekomen.
Tilda, je hebt een Bcc van dit mailinglist bericht.
Sorry voor het testbericht, ik was dat, vanaf een ander adres.
Stuur mij a.u.b. een reply op _dit_ bericht.
Mijn inschatting is overigens dat jou _geen blaam_ treft.
En via de mailinglist dadelijk meer.
Groeten
Geert Stappers
--
Leven en laten leven
Reply to: