Opened 4 years ago
Closed 4 years ago
#2547 closed task (fixed)
How to identify which account sends spurious emails
Reported by: | rouault | Owned by: | cvvergara |
---|---|---|---|
Priority: | normal | Milestone: | Unplanned |
Component: | SysAdmin/Mailman | Keywords: | |
Cc: |
Description
On the libtiff mailing list, a subscriber has its mail server configured to respond with a "NDN: ...." message each time a message is sent on the list. This annoys everyone of course. I cannot unfortunately identify from the info which subscriber it is to unscribe it. Any idea. Below one such spurious message
Return-Path: <> Delivered-To: [.... me .... ] Received: from spool.mail.gandi.net (spool4.mail.gandi.net [217.70.178.213]) by nmboxes134.sd4.0x35.net (Postfix) with ESMTPS id 0F6146057F for < ... me ... ]>; Fri, 18 Dec 2020 23:56:34 +0000 (UTC) Received: from fc.aslan.com (unknown [75.99.237.194]) by spool.mail.gandi.net (Postfix) with ESMTP id 89DA37804AC for <[ ... me ... ]>; Fri, 18 Dec 2020 23:56:33 +0000 (UTC) Message-id: <fc.001e84d1012c78f63b9aca006753d248.12c78f7@aslan.com> Date: Fri, 18 Dec 2020 18:55:47 -0500 Subject: NDN: Re: [Tiff] New libtiff release? X-FC-Icon-ID: 2031 X-FC-MachineGenerated: true To: [ ... me ... ] From: Mailer-Daemon@aslan.com MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-GND-Status: BOUNCE Received-SPF: Sorry. Your message could not be delivered to: Keith Hale (Mailbox or Conference is full.)
Change History (6)
comment:1 by , 4 years ago
Component: | Systems Admin → Mails & Mailing Lists |
---|---|
Owner: | changed from | to
comment:2 by , 4 years ago
follow-up: 4 comment:3 by , 4 years ago
Found the email. For privacy reasons I'll send it via PM to you.
comment:4 by , 4 years ago
Replying to neteler:
Found the email. For privacy reasons I'll send it via PM to you.
@neteler Did you PM me ? Can't find email
comment:6 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
The same happened in one of the grass lists. I was able to identify the person and disable the account. Tomorrow I can check the name.