phc-discussions - Re: confirm subscribe to discussions@...sword-hashing.net

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1438363789.357828.338398225.7081DC0D@webmail.messagingengine.com>
Date: Fri, 31 Jul 2015 19:29:49 +0200
From: Peter Vils Hansen <pvh@...tmail.com>
To: discussions@...sword-hashing.net
Subject: Re: confirm subscribe to discussions@...sword-hashing.net



On Fri, Jul 31, 2015, at 07:29 PM, discussions-help@...sword-hashing.net
wrote:
> Hi! This is the ezmlm program. I'm managing the
> discussions@...sword-hashing.net mailing list.
> 
> I'm working for my owner, who can be reached
> at discussions-owner@...sword-hashing.net.
> 
> To confirm that you would like
> 
>    pvh@...tmail.com
> 
> added to the discussions mailing list, please send
> an empty reply to this address:
> 
>    discussions-sc.1438363750.nmieneekhdiglpakfknk-pvh=fastmail.com@...sword-hashing.net
> 
> Usually, this happens when you just hit the "reply" button.
> If this does not work, simply copy the address and paste it into
> the "To:" field of a new message.
> 
> This confirmation serves two purposes. First, it verifies that I am able
> to get mail through to you. Second, it protects you in case someone
> forges a subscription request in your name.
> 
> Some mail programs are broken and cannot handle long addresses. If you
> cannot reply to this request, instead send a message to
> <discussions-request@...sword-hashing.net> and put the
> entire address listed above into the "Subject:" line.
> 
> 
> --- Administrative commands for the discussions list ---
> 
> I can handle administrative requests automatically. Please
> do not send them to the list address! Instead, send
> your message to the correct command address:
> 
> For help and a description of available commands, send a message to:
>    <discussions-help@...sword-hashing.net>
> 
> To subscribe to the list, send a message to:
>    <discussions-subscribe@...sword-hashing.net>
> 
> To remove your address from the list, just send a message to
> the address in the ``List-Unsubscribe'' header of any list
> message. If you haven't changed addresses since subscribing,
> you can also send a message to:
>    <discussions-unsubscribe@...sword-hashing.net>
> 
> For addition or removal of addresses, I'll send a confirmation
> message to that address. When you receive it, simply reply to it
> to complete the transaction.
> 
> If you need to get in touch with the human owner of this list,
> please send a message to:
> 
>     <discussions-owner@...sword-hashing.net>
> 
> Please include a FORWARDED list message with ALL HEADERS intact
> to make it easier to help you.
> 
> --- Enclosed is a copy of the request I received.
> 
> Return-Path: <pvh@...tmail.com>
> Received: (qmail 18930 invoked by uid 89); 31 Jul 2015 17:29:10 -0000
> Received: by simscan 1.4.0 ppid: 18924, pid: 18926, t: 0.2466s
>          scanners: attach: 1.4.0 spam: 3.2.5
> X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on
> 	qmailtoaster.cryptyx.com
> X-Spam-Level: ***
> X-Spam-Status: No, score=3.4 required=4.0 tests=AWL,EMPTY_MESSAGE,
> 	MISSING_SUBJECT,RDNS_NONE,TVD_SPACE_RATIO autolearn=no version=3.2.5
> Received: from unknown (HELO out1-smtp.messagingengine.com) (66.111.4.25)
>   by qmailtoaster.cryptyx.com with (DHE-RSA-AES256-SHA encrypted) SMTP;
>   31 Jul 2015 17:29:09 -0000
> Received-SPF: pass (qmailtoaster.cryptyx.com: SPF record at
> spf.messagingengine.com designates 66.111.4.25 as permitted sender)
> Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
> 	by mailout.nyi.internal (Postfix) with ESMTP id 3065F20A2E
> 	for <discussions-subscribe@...sword-hashing.net>; Fri, 31 Jul 2015 13:29:09 -0400 (EDT)
> Received: from web5 ([10.202.2.215])
>   by compute3.internal (MEProxy); Fri, 31 Jul 2015 13:29:09 -0400
> DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h=
> 	content-transfer-encoding:content-type:date:from:message-id
> 	:mime-version:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=2jmj7l5rSw0
> 	yVb/vlWAYkK/YBwk=; b=1QnglzE/QgtjwD+b+sSkXLEOgeQcgAdmOdeYzq0kKET
> 	M4QjM7QsZsvhskUx+qsgk3AN/vnlv9Zvd4HPNOAmY1GA1Roybe+owXnOU5QH70xI
> 	X/XBc9ApEhUEC8R0Phe5dMbneqiLILcrOnNPaxIHONNL+Xz1gywa/MunIJefUohU
> 	=
> DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
> 	messagingengine.com; h=content-transfer-encoding:content-type
> 	:date:from:message-id:mime-version:to:x-sasl-enc:x-sasl-enc; s=
> 	smtpout; bh=2jmj7l5rSw0yVb/vlWAYkK/YBwk=; b=VwO8j96JC+JEQoSGM3J6
> 	dTwOQ/3xRL6hBS8B8iuRxd543Z/IzLsXSDORewK+TRPYS6hd75PAoXOOFRkxhxpa
> 	KZj8+GuhPEkMBb5m10qPc7o4c+VL/KHf6Tx8KI4Tm2UfgDF6w3MlcVrnBxOOKOFU
> 	p6RYn+uNV3P0HT+2QgdVucU=
> Received: by web5.nyi.internal (Postfix, from userid 99)
> 	id 0A9A6A70EFB; Fri, 31 Jul 2015 13:29:09 -0400 (EDT)
> Message-Id:
> <1438363748.357772.338397817.0CE17E62@...mail.messagingengine.com>
> X-Sasl-Enc: QVsT8zU5gKJED9cBWnGZUm88MZ1LwIxLfMsoz29ukfN3 1438363748
> From: Peter Vils Hansen <pvh@...tmail.com>
> To: discussions-subscribe@...sword-hashing.net
> MIME-Version: 1.0
> Content-Transfer-Encoding: 7bit
> Content-Type: text/plain
> X-Mailer: MessagingEngine.com Webmail Interface - ajax-63a5d8c6
> Date: Fri, 31 Jul 2015 19:29:08 +0200
> 
>