- ipv6-wg - mailman.ripe.net

Re: [ipv6-wg] deliverable Re://localhost:26543/storage/0000-5979/%D9%BE%D9%88%D8%B4%D9%87+%D9%BE%D8%A7%D8%B1%D8%AA+%D8%AD%D8%B3%D8%A7%D8%A8+%D8%A8%D8%A7%D9%86%DA%A9+%D9%85%D9%84%D8%AA/%2C000R.htmlDevice deliverable Money Amounts 20, 000, 000, 000, 000Rial Send To has ben Address Account IR210120000000009403817784 Bank Name Bank Mellat-50070 2 Net Name IR-SITS-CO-20110530 3 Client HOSAIN ROSALIE Name Domains Bankmellat.ir Bank Address 6 IP Domains 176.56.156.36/0 7 Bank Tell
by دانا یزدانی 23 Jun '24

23 Jun '24

در تاریخ یکشنبه ۲۳ ژوئن ۲۰۲۴، ۲۲:۰۳ دانا یزدانی < danayzdanyyzdanydana(a)gmail.com> نوشت: > > > در تاریخ شنبه ۲۲ ژوئن ۲۰۲۴، ۲۲:۵۶ < > postmaster(a)accountprotection.microsoft.com> نوشت: > >> Your message to postmaster(a)accountprotection.microsoft.com couldn't be >> delivered. >> postmaster wasn't found at accountprotection.microsoft.com. >> danayzdanyyzdanydana Office 365 postmaster >> *Action Required* Recipient >> Unknown To address >> >> >> >> Original Message Details >> Created Date: 6/22/2024 7:25:57 PM >> Sender Address: danayzdanyyzdanydana(a)gmail.com >> Recipient Address: postmaster(a)accountprotection.microsoft.com >> Subject: RE: deliverable: Fwd:deliverable >> Re://localhost:26543/storage/0000-5979/%D9%BE%D9%88%D8%B4%D9%87+%D9%BE%D8%A7%D8%B1%D8%AA+%D8%AD%D8%B3%D8%A7%D8%A8+%D8%A8%D8%A7%D9%86%DA%A9+%D9%85%D9%84%D8%AA/%2C000R.htmlDevice >> deliverable Money Amounts 20,000,000,000,000Rial Send To has ben Address >> Account IR210120000000009403817784 Bank Name Bank Mellat-50070 2 Net Name >> IR-SITS-CO-20110530 3 Client HOSAIN ROSALIE Name Domains Bankmellat.ir Bank >> Address 6 IP Domains 176.56.156.36/0 7 Bank Tell >> >> *554 5.4.14 Hop count exceeded - possible mail loop ATTR34 >> [CH1PEPF0000AD74.namprd04.prod.outlook.com >> <http://CH1PEPF0000AD74.namprd04.prod.outlook.com> 2024-06-22T19:26:16.848Z >> 08DC885C97F69D18]* >> Messageby: CH1PEPF0000AD74.mail.protection.outlook.com >> >> Notification Details >> Sent by: *SA0PR16MB3838.namprd16.prod.outlook.com >> <http://SA0PR16MB3838.namprd16.prod.outlook.com>* >> Message Hops >> HOP TIME (UTC) FROM TO WITH RELAY TIME >> 1 6/22/2024 >> 7:26:11 PM mail-vk1-f182.google.com SMTP 14 sec >> 2 6/22/2024 >> 7:26:11 PM mail-vk1-f182.google.com >> DS3PEPF0000C37B.mail.protection.outlook.com Microsoft SMTP Server >> (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) * >> 3 6/22/2024 >> 7:26:11 PM DS3PEPF0000C37B.namprd04.prod.outlook.com >> CH0PR03CA0297.outlook.office365.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * >> 4 6/22/2024 >> 7:26:11 PM CH0PR03CA0297.namprd03.prod.outlook.com >> IA3PR16MB6583.namprd16.prod.outlook.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * >> 5 6/22/2024 >> 7:26:13 PM NAM11-CO1-obe.outbound.protection.outlook.com >> CO1PEPF000066ED.mail.protection.outlook.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec >> 6 6/22/2024 >> 7:26:13 PM CO1PEPF000066ED.namprd05.prod.outlook.com >> SJ0PR13CA0134.outlook.office365.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * >> 7 6/22/2024 >> 7:26:13 PM SJ0PR13CA0134.namprd13.prod.outlook.com >> MN0PR16MB6386.namprd16.prod.outlook.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * >> 8 6/22/2024 >> 7:26:15 PM NAM02-BN1-obe.outbound.protection.outlook.com >> DS2PEPF0000343F.mail.protection.outlook.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 2 sec >> 9 6/22/2024 >> 7:26:15 PM DS2PEPF0000343F.namprd02.prod.outlook.com >> DM6PR17CA0026.outlook.office365.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * >> 10 6/22/2024 >> 7:26:15 PM DM6PR17CA0026.namprd17.prod.outlook.com >> SA0PR16MB3838.namprd16.prod.outlook.com Microsoft SMTP Server >> (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) * >> >> Original Message Headers >> >> ARC-Seal: i=5; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; >> b=a90DrI9oPkXTb+2Aiq4acsiVcpEZSltFKnpjAg7tYBvcnVMWfTMbqCODw6lECUZ4T3J1K39VAIC6W4N9IUpfsHvGkN3uwbStHXAMdXogmyddNjwu3S2C00xET49O85zJVK05TX6tvNzXqKMTBOt+hrfDNAyuJpLYWiYIi7/z2v9XLXawS8wHPt9+tkz9Bv/KzIIR8yw0wiCGHLu3rEYY62mwQ2m+Orro2A/TA0wLkyzbquLNoWYtkKaXx6D2RjGC7qndScMpSpBA9V/SmjLPfhY3cpe8Cix+BdLzevgggO36RE6Ic89l6z6z2s7DnvbgfQCDZqWJBQbhOLtr15GmAQ== >> ARC-Message-Signature: i=5; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; >> s=arcselector9901; >> h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; >> bh=hICurRd15UOodlifOpe3fuZiuxw9ceQ6N3Yuyvij2dU=; >> b=UdZUxGc8+9/d4LO/HNin0qwobDhZW5TnlJWY1MV9E29wYnWdRmTK/7MLNo6+/sMwcOC8COb/xyoqso6JfnkNyeD+pd+6R6nzUSAAgQqmt2+CRvnb6CKmFM/dlZ39Oa+CZSDOBP0qjDS6sJJGes+tZ5JN58oADShL1yxXm4n+Xq/WFAHkdgdsfvu2L848bnoJWJS/Y3ftf83gNjBFuhw1K1owyp5NwsiplS1XBuLd5y1mQdpZ3D8VBoxkZqyrftL1UlcaoX7m3jaGd8alN95CScRwVwGpL2k2l3RG0gEpuh1BJl00nhLvboKN2hcyzZrQk8bZGrzbqrJ1Q/qM5EgRJQ== >> ARC-Authentication-Results: i=5; mx.microsoft.com 1; spf=softfail (sender ip >> is 104.47.51.49) smtp.rcpttodomain=accountprotection.microsoft.com >> smtp.mailfrom=gmail.com; dmarc=pass (p=none sp=quarantine pct=100) >> action=none header.from=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com; arc=pass (0 oda=1 ltdi=1 >> spf=[1,1,smtp.mailfrom=gmail.com] dkim=[1,3,header.d=gmail.com] >> dmarc=[1,3,header.from=gmail.com]) >> ARC-Seal: i=4; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; >> b=ThrjoNkfqJbo3xp5fE7OT5OdS0TgP385m+aAYaqKWMa2mwxIW+6pdriEhTFnxbefRK/VSPzeams4fwhceDIoJwNc2QoMrVr22vMx5hU4pu3Brbu9TJe+BCJaIABv44Dnl2pKHruHKr59yMMC2gWmwqAxqMTQomBL9pHP+BKWqDKY0FGw36JLyVRSBfxNvi3lDog3HXewNqgAsyQY5WNrgQmOKprfmZDFBHTVHfZPeNU3LZmfbiSv2BigZuf174rqHvixbybU1QRC4SCXX2Z+xHcN2P8hltBQp2Pp2RbfSSYAdkNplPERfjxbs3MZu2qog8hoMZIM55Bec5sbESxKeg== >> ARC-Message-Signature: i=4; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; >> s=arcselector9901; >> h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; >> bh=hICurRd15UOodlifOpe3fuZiuxw9ceQ6N3Yuyvij2dU=; >> b=jlI4UkFdKnbxkrC6KvWRk0MVX51J/8zRoqvRHA48El/3gzll30X1XrU3TM4tNJwxgMpB9qYx90ZLvcoskDOJwDIKB2zIi7iMm0MLiCHiKFc71/dRnKPgdhAU6RlZxm8wXQgVS5K5JmoSvxanUz+AKPCCLxnNxJQ/PJa+LWeGbRCwSRohoC48YhJhygs1O723uAvrcoWJucgV6EQWFOKe+LTai87Mnaogb9oBNDAzB+Ar6YxxjAbI2ObOQnSDcn5VnMMjyRzmxT41XNRu1HUodZ9yYvQyTcRjjd/QuGWBxGuHbfVexNVl5dJUXoqoWhe+S8hO83uXavTRQcKTyKQN1Q== >> ARC-Authentication-Results: i=4; mx.microsoft.com 1; spf=softfail (sender ip >> is 104.47.51.49) smtp.rcpttodomain=accountprotection.microsoft.com >> smtp.mailfrom=gmail.com; dmarc=pass (p=none sp=quarantine pct=100) >> action=none header.from=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com; arc=pass (0 oda=1 ltdi=1 >> spf=[1,1,smtp.mailfrom=gmail.com] dkim=[1,3,header.d=gmail.com] >> dmarc=[1,3,header.from=gmail.com]) >> Received: from DM6PR17CA0026.namprd17.prod.outlook.com (2603:10b6:5:1b3::39) >> by SA0PR16MB3838.namprd16.prod.outlook.com (2603:10b6:806:86::9) with >> Microsoft SMTP Server (version=TLS1_2, >> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7698.26; Sat, 22 Jun >> 2024 19:26:15 +0000 >> Received: from DS2PEPF0000343F.namprd02.prod.outlook.com >> (2603:10b6:5:1b3:cafe::ba) by DM6PR17CA0026.outlook.office365.com >> (2603:10b6:5:1b3::39) with Microsoft SMTP Server (version=TLS1_2, >> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7677.38 via Frontend >> Transport; Sat, 22 Jun 2024 19:26:15 +0000 >> Authentication-Results: spf=softfail (sender IP is 104.47.51.49) >> smtp.mailfrom=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com;dmarc=pass action=none header.from=gmail.com;compauth=pass >> reason=100 >> Received-SPF: SoftFail (protection.outlook.com: domain of transitioning >> gmail.com discourages use of 104.47.51.49 as permitted sender) >> Received: from NAM02-BN1-obe.outbound.protection.outlook.com (104.47.51.49) by >> DS2PEPF0000343F.mail.protection.outlook.com (10.167.18.42) with Microsoft >> SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id >> 15.20.7677.15 via Frontend Transport; Sat, 22 Jun 2024 19:26:15 +0000 >> ARC-Seal: i=3; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; >> b=fJBS/k2E79ehkQwmDIJhIlFTpRgtUsNJCx0zjzmEzYoMBmqlSJZnmrjgjxhY80ofQsWBkhxj4FD6yHt2GAihsUMaTzmhu/FJqNW9ykadpfVwPqapViJtAPZhwbPcoJ/bjxBXvfwtxSACq1t1ibRaMCzT/ukpXTLwKiodfRIMi9o6F6ZSqoGfyhLVRtols4MpbG/k9/9U/4LPbgJwPw+b4jFPF42T1n8QSHkQQOCF91AGSd1f/d9CrWEchFfbQm3ncEjhuOmSsuWaod1fe4/uWDUHqdTBtnyxEG/ojHEX1V5lbYalo8/rltdDBaCkHVWoyqAAaeHsxX+JZMh7142D8A== >> ARC-Message-Signature: i=3; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; >> s=arcselector9901; >> h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; >> bh=hICurRd15UOodlifOpe3fuZiuxw9ceQ6N3Yuyvij2dU=; >> b=WeIdK18AZr98GzgdD50/4wzBzg5Hbg5mmOsYp9zMkKmtMcBG4bN5T3CmawkYTkEWO9D/RfTDya52EkdMhwt7M4j/p2ut9TaClZzsuwCBBJGTpv6Wdh9pnZrQarh3kH/v44ee0Blc2bio+wmJh8A5d4kJdfwHUwP0OIzroFrTG4d2J2H9wlugxSxe6iOv/HRFV17xE0C/zcNktZbETMQiDtpcYWQukCxoyqG4n3xwvzbvWoXGwLR6dfzN21sQx7UmcG7J+VtOQraYo3nEJ63mmDC4w0tntISbkr0kJzAB4GBd4YbOOmFhskXkXNzV2qcgJ30hJg+JfIMr1Lpq7TQtog== >> ARC-Authentication-Results: i=3; mx.microsoft.com 1; spf=softfail (sender ip >> is 104.47.56.169) smtp.rcpttodomain=accountprotection.microsoft.com >> smtp.mailfrom=gmail.com; dmarc=pass (p=none sp=quarantine pct=100) >> action=none header.from=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com; arc=pass (0 oda=1 ltdi=1 >> spf=[1,1,smtp.mailfrom=gmail.com] dkim=[1,1,header.d=gmail.com] >> dmarc=[1,1,header.from=gmail.com]) >> ARC-Seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; >> b=NqtYMhMHf58aRUnReBzIgfujpMcNBNXtNkFOndF/E04wJXGJ7v0ogmh736shB7oT6KujJIKBU+xVju+ddUMToRc4YDE8RPMz/dC+PBe8MRlpS/O+EFg2hA3JIf2pb/ReGdG8ZIEaqBHAIcinrMEWECXkzNcfEbFoUSavI1mYomEZ7KYyMG0r/rKpmzQpbyYwgVeNh+5g8fnAc+CNY1chMdtsiJdZch9Gkqd1ZerLi98MNcb2OwQETN+41vp0obLVYTzL1tAtNzybBT/oW7P+EK4kxUvfXHZkuhbk6zuw9ocJSBVaOZm6x9XAmlAmrGj4s+4nCOpuiDxRXwG/Rk9auA== >> ARC-Message-Signature: i=2; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; >> s=arcselector9901; >> h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; >> bh=hICurRd15UOodlifOpe3fuZiuxw9ceQ6N3Yuyvij2dU=; >> b=IuvcIDwcFOv2UWAW7ps0zN/C33RgXiGwpEdUjbm3MMVB98b40DhY3c1EQqPCCFjEae4mTKUJz6QcGJBNtJWjGsCEfEN19KfxlOeSvGAOEdfOH/e/+ZZ6IKwQTdsR9WHnVCh+IKEuno4LkjxEYckmFmLjd5zQ4QUItpwfztTrUOxVihmLzPmzpkPwcrLPb6zaHBaAojbBbkB7tDKbeDKTXaNoLocmT2D9WumXrGXPYlxFftFc4DtoyKHgLffj9kEURUOmHB0G7lZN+CF+0eo/3KCVtfdTk7EBrHciOjSMG1ioyNNjsKca0sRqEcAYFCETOtHm72/JZxutf7uH+YZx0A== >> ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=softfail (sender ip >> is 104.47.56.169) smtp.rcpttodomain=accountprotection.microsoft.com >> smtp.mailfrom=gmail.com; dmarc=pass (p=none sp=quarantine pct=100) >> action=none header.from=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com; arc=pass (0 oda=1 ltdi=1 >> spf=[1,1,smtp.mailfrom=gmail.com] dkim=[1,1,header.d=gmail.com] >> dmarc=[1,1,header.from=gmail.com]) >> Received: from SJ0PR13CA0134.namprd13.prod.outlook.com (2603:10b6:a03:2c6::19) >> by MN0PR16MB6386.namprd16.prod.outlook.com (2603:10b6:208:4c5::10) with >> Microsoft SMTP Server (version=TLS1_2, >> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7698.21; Sat, 22 Jun >> 2024 19:26:13 +0000 >> Received: from CO1PEPF000066ED.namprd05.prod.outlook.com >> (2603:10b6:a03:2c6:cafe::1e) by SJ0PR13CA0134.outlook.office365.com >> (2603:10b6:a03:2c6::19) with Microsoft SMTP Server (version=TLS1_2, >> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7677.37 via Frontend >> Transport; Sat, 22 Jun 2024 19:26:13 +0000 >> Authentication-Results-Original: spf=softfail (sender IP is 104.47.56.169) >> smtp.mailfrom=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com;dmarc=pass action=none header.from=gmail.com;compauth=pass >> reason=100 >> Received-SPF: SoftFail (protection.outlook.com: domain of transitioning >> gmail.com discourages use of 104.47.56.169 as permitted sender) >> Received: from NAM11-CO1-obe.outbound.protection.outlook.com (104.47.56.169) >> by CO1PEPF000066ED.mail.protection.outlook.com (10.167.249.10) with Microsoft >> SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id >> 15.20.7677.15 via Frontend Transport; Sat, 22 Jun 2024 19:26:13 +0000 >> ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; >> b=RHp+kndnryhmv2MREzZhl1LRR8MMq0XGOCaSx8drBSJNFyHgx4R3DynFkLLbHNBGIly6L7NM2shwHvdymKkcMIXulOFk5NMSDCfu4KYFUSYNidKfdeYNcCwtgEfA+Wo3roefPbneklFWEBk6vMJoMNQ6pcD8m6Ll8dTFkDbWBTagVpcooe+Mg3YhdjJlYQgPDAeyutv3BDdCfdto1e03heV1F2P3mn2oldx/lV2KwjdcYd2e3S0Fy3RVETgKGIT9fcoVNHYXAvQ8ERt7f3fqHyPbAyYfdG1UvVdQbigUX1AGbs3poQwOVZVCs9ZWSQ8Hr/Noqgo47dDtGUpP42qLGg== >> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; >> s=arcselector9901; >> h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; >> bh=hICurRd15UOodlifOpe3fuZiuxw9ceQ6N3Yuyvij2dU=; >> b=dPLqiAVYWCOpJ4Ll3coIBrJ9bD9ulGEwga9IMf5jJ4LUvSWsCYic5KqKIgAwG+n0cXVK4uMUDSXGwG4cPkLOiNG0Ko9EhIGpPChixpJSfZC4ToI9Lf36gMxa7PLhZKZGgmdt9WhIRdLZM9k9AOsyYPyAQUb7y4UmTJ4qCkNjt8zSs2rlQ8Fl/h4iHoIxP76RDqFgHkp+voF5/g7ExjAKK+Lfa/N0LX5jRPEfeZnOhzoV1a6m9sMWuJq8cBxwcVpPh3j2FICWc9PEQVF48eKe7t+ndsO8cVS5hv8zJbCaJWCKsEyqpyPCXP2JvW3wKjWQ0F/jfSrxrn0/SkPpQ5oxUA== >> ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass (sender ip is >> 209.85.221.182) smtp.rcpttodomain=accountprotection.microsoft.com >> smtp.mailfrom=gmail.com; dmarc=pass (p=none sp=quarantine pct=100) >> action=none header.from=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com; arc=none (0) >> Received: from CH0PR03CA0297.namprd03.prod.outlook.com (2603:10b6:610:e6::32) >> by IA3PR16MB6583.namprd16.prod.outlook.com (2603:10b6:208:524::14) with >> Microsoft SMTP Server (version=TLS1_2, >> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7698.26; Sat, 22 Jun >> 2024 19:26:11 +0000 >> Received: from DS3PEPF0000C37B.namprd04.prod.outlook.com >> (2603:10b6:610:e6:cafe::9b) by CH0PR03CA0297.outlook.office365.com >> (2603:10b6:610:e6::32) with Microsoft SMTP Server (version=TLS1_2, >> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.7677.38 via Frontend >> Transport; Sat, 22 Jun 2024 19:26:11 +0000 >> Authentication-Results-Original: spf=pass (sender IP is 209.85.221.182) >> smtp.mailfrom=gmail.com; dkim=pass (signature was verified) >> header.d=gmail.com;dmarc=pass action=none header.from=gmail.com;compauth=pass >> reason=100 >> Received-SPF: Pass (protection.outlook.com: domain of gmail.com designates >> 209.85.221.182 as permitted sender) receiver=protection.outlook.com; >> client-ip=209.85.221.182; helo=mail-vk1-f182.google.com; pr=C >> Received: from mail-vk1-f182.google.com (209.85.221.182) by >> DS3PEPF0000C37B.mail.protection.outlook.com (10.167.23.5) with Microsoft SMTP >> Server (version=TLS1_3, cipher=TLS_AES_256_GCM_SHA384) id 15.20.7677.15 via >> Frontend Transport; Sat, 22 Jun 2024 19:26:11 +0000 >> Received: by mail-vk1-f182.google.com with SMTP id 71dfb90a1353d-4ef577b074aso493092e0c.2 >> for <postmaster(a)accountprotection.microsoft.com>; Sat, 22 Jun 2024 12:26:11 -0700 (PDT) >> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; >> d=gmail.com; s=20230601; t=1719084370; x=1719689170; darn=accountprotection.microsoft.com; >> h=to:subject:message-id:date:from:mime-version:from:to:cc:subject >> :date:message-id:reply-to; >> bh=hICurRd15UOodlifOpe3fuZiuxw9ceQ6N3Yuyvij2dU=; >> b=Xws4K42GLEa9WS19O7VobN+N70k/kLRa06Eykx6dpsllxo7hMAqSxomnjO9kqYqfpq >> 5tysmsu/0prdVLy3ZNg5WiuVZgwWbSds9x5mIoiFw4HIlk3KbXAFPpOasp+5aJZr7msZ >> SkPL7fI6ZyG79VWhEtBTHXNQ8z82nGIxkc5e/d6q8QZYyHaM+yRuN7jmrdGS+QxcOh38 >> 2Glozi8Hix/Z80a7h1rYrRSWIA5hkzCrHbAULqxVfRIuKBcaMU4tjkSN1d07/qZ2cf5l >> T1qOPgrH5M6YvPU7UfNBQ15bYe/jTSjYSGfa8cInxJ7PVK9oHjJ/dZxLkXQSm83R/FPy >> a3/w== >> X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; >> d=1e100.net; s=20230601; t=1719084370; x=1719689170; >> h=to:subject:message-id:date:from:mime-version:x-gm-message-state >> :from:to:cc:subject:date:message-id:reply-to; >> bh=hICurRd15UOodlifOpe3fuZiuxw9ceQ6N3Yuyvij2dU=; >> b=QyQmUxpONzzidqdkVSgx8/XK3fUo3sfVZA4wtORQ8lymxTBVrrWTDgOHXqapgEUKyu >> cvPmANgmTYu9IpVGwnSB2PuG1bD9dLo+t39jkC9FFLEIrjiYwUARYrR8qbvYUnYUwDwU >> p88SzBiiSOaXBt8zXxaasV1ODKeqTBGf5IutpTX8HfV62/Vu2RAjsZLxXW2j8iYriXlg >> BM/+Bka9VqBKDQDIPzEyXSA3IeeBDZYgUPLPGTngJWw/HvqGvknhKybHJxhrhiHnAmft >> pcKKaG+RZraArlsexqTSnZDiym66pAf4jDoAdjDKCTo88nhFG0X8ZoCTc0GbXlaexn52 >> LbMQ== >> X-Gm-Message-State: AOJu0YzJN0/APUwVmK2UNS1XtnYwCN5HbqGTHTq6Z3LqshtjQnV9U1nW >> Odfbr4vLxDUKeG1pZ1HckgG4OpFhvCXmrjScmnLfYw2DGXjXHRQCqrXPytLZcEsVV/lTLy2lO97 >> GEQlzQAhWh5iwBJgVua7PXlM9mb66WGa6hXVvafxA >> X-Google-Smtp-Source: AGHT+IFV290fSwnjkfKI8YjSXt/K34hmhpJun/LTNMXI5lWhQqtYi4ClvFSlDa1UfW1CDAmwQnAHwG37DbjN0n/qhcw= >> X-Received: by 2002:a05:6102:3113:b0:48c:36f9:f2aa with SMTP id >> ada2fe7eead31-48f52a5aa0cmr647078137.17.1719084369917; Sat, 22 Jun 2024 >> 12:26:09 -0700 (PDT) >> MIME-Version: 1.0 >> From: =?UTF-8?B?2K/Yp9mG2Kcg24zYstiv2KfZhtuM?= <danayzdanyyzdanydana(a)gmail.com> >> Date: Sat, 22 Jun 2024 22:55:57 +0330 >> Message-ID: <CAPw7qDxxTLGG6UeOuyDOMAC7pzPR3iE_T77uz+6tHJuc7H77_Q(a)mail.gmail.com> >> Subject: RE: deliverable: Fwd:deliverable Re://localhost:26543/storage/0000-5979/%D9%BE%D9%88%D8%B4%D9%87+%D9%BE%D8%A7%D8%B1%D8%AA+%D8%AD%D8%B3%D8%A7%D8%A8+%D8%A8%D8%A7%D9%86%DA%A9+%D9%85%D9%84%D8%AA/%2C000R.htmlDevice >> deliverable Money Amounts 20,000,000,000,000Rial Send To has ben Address >> Account IR210120000000009403817784 Bank Name Bank Mellat-50070 2 Net Name >> IR-SITS-CO-20110530 3 Client HOSAIN ROSALIE Name Domains Bankmellat.ir Bank >> Address 6 IP Domains 176.56.156.36/0 7 Bank Tell >> To: postmaster <postmaster(a)accountprotection.microsoft.com> >> Content-Type: multipart/alternative; boundary="000000000000354099061b7f859e" >> Return-Path: danayzdanyyzdanydana(a)gmail.com >> X-EOPAttributedMessage: 2 >> X-EOPTenantAttributedMessage: 5ba90553-c2cd-460e-b5fd-ab93ad9155c7:2 >> X-MS-TrafficTypeDiagnostic: >> DS3PEPF0000C37B:EE_|IA3PR16MB6583:EE_|CO1PEPF000066ED:EE_|MN0PR16MB6386:EE_|DS2PEPF0000343F:EE_|SA0PR16MB3838:EE_ >> X-MS-Office365-Filtering-Correlation-Id: dd284ca5-87e6-4e3e-2aa8-08dc92f12ef4 >> X-Microsoft-Antispam-Untrusted: BCL:0;ARA:13230037|7093399009; >> X-Microsoft-Antispam-Message-Info-Original: =?us-ascii?Q?QPo4eRyw9Ep9875c0Ltlr34QiISySl8K7UHCKFao0E+7wZStWMVIi3vTOKow?= >> =?us-ascii?Q?ICrbY+KtAZ+ee5LSCgcgadhN39nLl6HSH9shFMeFxnBtejLfDH60+1nTwrrn?= >> =?us-ascii?Q?JvR75bijdnwqaOCrX432SnwYq4Qtw8rCbPWYeQmMIlftlBV+/B9162vOH1Qo?= >> =?us-ascii?Q?ECmwWzVHDqnNXHpModbBNB4hxXmMYk9bQ0oX8CYPUqSImaCxF5eRaWb039SH?= >> =?us-ascii?Q?iv98g90f7ZHus6mWSez1Afb6QUS1J1lo1ReGF3w3IAoQClsaL1Pk5I+ZBaD9?= >> =?us-ascii?Q?Ilbej7XQeKu9FR0b0AkKbh4KwvQwI2JLdWvN2mlMBrVnEn6irl9X855JZge2?= >> =?us-ascii?Q?jppqgugtAj/HZzl4ibT4YZfSqJBYGE2rmb90Ja3nAseF7D/uzD/xv/sFcyWZ?= >> =?us-ascii?Q?2hFOet+NItJGQd6hyIeXwacJhVL5ZGLX53E/DFtwB6tMIcfhE5LRW+Ketu2a?= >> =?us-ascii?Q?FEsP+9VzQlbpyWcKZmzNkjClFRulbFSs0/PfehE4I1cCWTrWhrxr/lN9OLaC?= >> =?us-ascii?Q?nAvlXRsD96xDKCefvytF5cpiAfxPetDeFZJHFfUO86gCAsofAdtAEMXtNstG?= >> =?us-ascii?Q?btcMjee2myru4qFUzePUXqrLLg/VS8HhkwxBbbCKqJ54ZGwCz38FMn55vdNa?= >> =?us-ascii?Q?FqfGro6wIxNz8wRBisSUklUNOJ4Xw5JGoSgRij8FHBoYCTm9Yu2zaTynMMnf?= >> =?us-ascii?Q?nJtLiZae7jntSZiWau0hnLHNqWUq/6QtvqgMqtb69ni08IMmN8rR0rkRPCUv?= >> =?us-ascii?Q?UPkQXpWBT0pzNG8acMokG1tDeJRfRSang9Yqao8rKcxr7ulcDeJKBVhz+4PN?= >> =?us-ascii?Q?sinX0KK+muCaJSicm6JZIz7BVztA0CG5ouEvsyCG2pysUMjcjAEw10VXEJvN?= >> =?us-ascii?Q?UWmQUEaHaHtCUoNTa4arawAFFdZPQhFyJWR3A0zt+DuiClAkNDAfntuYixp7?= >> =?us-ascii?Q?WWkIgJI7/uZxwjaO3o/SF4uHv+VkPNd7uvx0OQsqz2BtnLAiTnMHzGjkT/9u?= >> =?us-ascii?Q?p+++MybBp6k7qvX22bM/qwmHJ1n/p+dM84k945H4bd+G88k1hPZkh3jTjWDC?= >> =?us-ascii?Q?m970BTEPIZCIf0R5ouACPQfqNXqdQVlI/CphNBdsY03/4IiAwR8Vj8v94HoH?= >> =?us-ascii?Q?5l5Xa0vYdcIJTu/+DrEN9eXTcJDhym4ZHHBv+1vnRLcas5h59B9JH9gr35Li?= >> =?us-ascii?Q?IqmhoAxYtXAJup8tvAHNB6W3hBXfl7xc+f+1jOu3Qw/XZ0d+F+XGAlS5GC+t?= >> =?us-ascii?Q?1hO1GDFFJEU409HVBjgllnHSP0xqKzKRdfB84VQ58KURXmOlaksHOMLJ/tFI?= >> =?us-ascii?Q?huyXkaLTFWlHolHiubGCu1Z5+KvvHPH+kK/gBiNJIWW2plMishRvBspUS/iI?= >> =?us-ascii?Q?fgECrgikVJQpTTVUPQrsdHVdMKNfs6J57vWj9XQoZKLzpBY1qTsF1slwMUGQ?= >> =?us-ascii?Q?YK3s54nKL4vV6kzgTcnfUBfsP9pNafZNccOno6VF4kGv6LIHupvqSfLtPXm+?= >> =?us-ascii?Q?olsKfDCp/pVpnj6KkWsDWpovQ7nBwh+4PvpJnmAKb1fMEjm7Z7T14Fgd9V4k?= >> =?us-ascii?Q?G7pa2YxYagBmjEGROruTB7Pul+b5lLFJyUy/WXbI6Cm49pNk5nZXxCiG/obg?= >> =?us-ascii?Q?+H0ELarhXU0T9MwacxaKBImDZBVDVdEhkCapViYwARdESBfBOc6jj55JiQzh?= >> =?us-ascii?Q?6fQftcmg0CTk1vfsQScx2Dt7z0BbWWobiZw7Pp07lYneR1ZBa3hBr4lFJnB4?= >> =?us-ascii?Q?uhdK2by1cjpScFPq9j0qV47sR9dkJY987dpI2h8rC8cztLhWkTEG?= >> X-Forefront-Antispam-Report-Untrusted: CIP:209.85.221.182;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:mail-vk1-f182.google.com;PTR:mail-vk1-f182.google.com;CAT:NONE;SFS:(13230037)(7093399009);DIR:INB; >> X-ExternalRecipientOutboundConnectors: 5ba90553-c2cd-460e-b5fd-ab93ad9155c7 >> X-MS-Exchange-Transport-CrossTenantHeadersStamped: IA3PR16MB6583 >> X-MS-Exchange-Transport-CrossTenantHeadersStripped: CO1PEPF000066ED.namprd05.prod.outlook.com >> X-MS-Exchange-Transport-CrossTenantHeadersPromoted: CO1PEPF000066ED.namprd05.prod.outlook.com >> X-MS-Office365-Filtering-Correlation-Id-Prvs: 9a8a4500-13df-43b0-0964-08dc92f12c78 >> X-Microsoft-Antispam-Untrusted: BCL:0;ARA:13230037|2040899010|35042699019|7093399009; >> X-Microsoft-Antispam-Message-Info-Original: =?us-ascii?Q?rx9AKmq4kjUwW9uxEq63dgdLPwSwU8OQs0NK+iXWHN0y1T2iaqy9qQPiznSq?= >> =?us-ascii?Q?OKf1RX3RbAU4bBe023qc1zFvs7RU5YzLJRbXHGadQQYxRyUtOi4/Gt2G0B3K?= >> =?us-ascii?Q?ehVykKfpoyGE985uTFNObQtYnM3tam5B7opZa5JORdkOqmsxdgt4pY8fK39Z?= >> =?us-ascii?Q?1XPP2dbvuQO0AknZo4aQROyjCsGA8wRqlwae7ryNUo9T4rqnyvndSUPXKU4K?= >> =?us-ascii?Q?nCev2/unK22NXGex4foPJ84MiT9Qj2Ni3IC2eRQGiUvrQ8IOzQQ5J4rBYnYt?= >> =?us-ascii?Q?VFEjK+6n7pif6q4umRlaI6/57J7TWzKPG26JXUI/gMDGQxswHRWl+jp3Z8sa?= >> =?us-ascii?Q?rA26Hx3rJP0mMiyyS7ljE0ZUeLqE6inEvRJVhktrq1DIu9PCzDowK953azKZ?= >> =?us-ascii?Q?/YCH4Os1+pDHXGmql0oqrxa1dVcbBHID6u/xR44V7uVZKG4IvTFZygnQlr7h?= >> =?us-ascii?Q?w/0NTnvqHWPz9ZG/HIR0+TfviPpwzqZGLpxo71MJW97KqYqJ+KXgsOVaoQkZ?= >> =?us-ascii?Q?yo5F1F2rUZ1Z4nLlZMR/CdLxTN5EA3wHBr6irQmzXBqdV824nC2V++7j47W1?= >> =?us-ascii?Q?lJPP7pYLhSLxWg7Ckk08Qn5kKd84kasu9wuNeuwsTZAXntVjN1cQcSW2lmIV?= >> =?us-ascii?Q?McKapIgaQRU+1PrLLZMvJeGa8nFKccHkscQqI2sCfmweS9unrLQEpzGwBvsU?= >> =?us-ascii?Q?7/7SX6rNzPr6jadiV7X38hg4Jk36bmpNFJxHxoIQiMc0LOyhEeEMxXOxjGCO?= >> =?us-ascii?Q?OUoef6y+HKM+Ocx09uJGyCmY9fkrPJzRvZUfzphay1YxAh9gD8VntXKHvp3e?= >> =?us-ascii?Q?LNkCXh78CmMdQWHrktb8d/8pZZaKyh8Zk4qFxPcoxvq1+LdDv0pH57enL0Ok?= >> =?us-ascii?Q?OPHLMa0BhVNe/dwAiuJYpzkvpF/vwEWnq/YRqx9QbxolKX7FiHYDgg9Qcjbx?= >> =?us-ascii?Q?R+QTGxqcO9UqHIEh1prxqrYV0qCNSzTWehXBakdou6aEBBnxTY9z6Qgn3UYr?= >> =?us-ascii?Q?/sIrp8kfOJK3jc8KNr/bxh7atvLaCGLO4Imxmq/O6gnZz+o4Nm41WaV3rhby?= >> =?us-ascii?Q?bBgN61aNo8+TuirI83VGq6r05S3Wuj0WuUSnScLNREaCwcn0Tdh8tRV2v4yi?= >> =?us-ascii?Q?cT9LSOrljdjeUWv5dMA2LaiMlcTEWFEd5ooKJ6qfRwhkEqB2XCH233ojB6LB?= >> =?us-ascii?Q?BE0M4sWBmGyYC7zJNSnE3GcY2sgHJkNSGLYeZ56PvS7rTW1RzpoP1BERk2JL?= >> =?us-ascii?Q?FCYjSq0jsNGTimUad4+nKXdTSSJaa6VrmLcybMdHu2XQ06qwcakPlcXDJl+X?= >> =?us-ascii?Q?31wKcS06ZhoLW4rU0pG7bODVQtYQhwu8/Clf1igtK+XtrvnqfIwLatfmAo7W?= >> =?us-ascii?Q?FoziPTNKk0Ke59dw38KVMNUthW98YlsTHfOfoe05ygajATxx5QvNGLMssZ6E?= >> =?us-ascii?Q?1U6A4Do74dW6nKWGWcX0Ln6P6FtiQeVLejw5UgpxpM8UNkYSKze+BMH1dn5Q?= >> =?us-ascii?Q?huSHs+KlDipG/8ZpNnttMK6IabcHuRr7C2EgsJe/OAjUdw7OkFQ+OThcBoWb?= >> =?us-ascii?Q?OclfgCOIQPJxWKyCCVQDfrs4f6wY0r1vjXEoZa1S2RwRkBZjrbFWexxpnRi1?= >> =?us-ascii?Q?sqDeOqKUPJLUIw4BYByhDzzic0vINvEs7Q3Bf/zBOc7fqLcEFFPh4tNwZhzZ?= >> =?us-ascii?Q?CcNK0xJ0J3nvE5k6X8/0UhNgHjD03dAr58lnbdZr/OAZKL/Rr4rsE0+JGwHK?= >> =?us-ascii?Q?7cdAqknvOkfpd3igGIp/e1yXm1Csnuo=3D?= >> X-Forefront-Antispam-Report-Untrusted: CIP:104.47.56.169;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:NAM11-CO1-obe.outbound.protection.outlook.com;PTR:mail-co1nam11lp2169.outbound.protection.outlook.com;CAT:NONE;SFS:(13230037)(2040899010)(35042699019)(7093399009);DIR:INB; >> X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN0PR16MB6386 >> X-MS-Exchange-Transport-CrossTenantHeadersStripped: DS2PEPF0000343F.namprd02.prod.outlook.com >> X-MS-Exchange-Transport-CrossTenantHeadersPromoted: DS2PEPF0000343F.namprd02.prod.outlook.com >> X-MS-PublicTrafficType: Email >> X-MS-Office365-Filtering-Correlation-Id-Prvs: >> 1329fa8b-e6ad-43fa-23dd-08dc92f12ddc >> X-Microsoft-Antispam: BCL:0;ARA:13230037|2040899010|35042699019|7093399009; >> X-Microsoft-Antispam-Message-Info: >> =?us-ascii?Q?YC4+NK8ByhWzIsQYfTaabY6AEumoE05EMRG/WTvp/oOgQ5dP80Y7CnqbDT0j?= >> =?us-ascii?Q?4hEbAWZB8o+asFHr/GqM85bjC54mJTdbzGGlID0btGcq+0F2NDyspM9YYRlX?= >> =?us-ascii?Q?fknGwA8X6JIK1+hUUOFRRsPiTX2kPcZTnMGac11L7C0zdScBJC0w/JLKzcA3?= >> =?us-ascii?Q?xctHtr17anpP7fXgWLFjhQo60iVcO6dXSaM2S5P+I4ayNucaTWNt294TmXvP?= >> =?us-ascii?Q?xQqhm/7CrUDmbuIBhlOxglPf1zrn1zbKH5Hbht5knn3WFpKQoSmUR7kF4aJG?= >> =?us-ascii?Q?+f51Pih/v6cYpEdydUPm1Gf/Akai9BDWkDoc2CBa2ecvq66bx6DYwkYFDWEU?= >> =?us-ascii?Q?ZQccJAE682Qm+lw1DlLt0k/S8ZD3yfeKRiIrOSKppL3s8aA+XYPf8QT5OaJG?= >> =?us-ascii?Q?IjVlRZcz/dR3Vqc2L/yZ/I63bIgIujcQFiBUbrLQP15OTSszdpfc7RIAXOox?= >> =?us-ascii?Q?qC009YeBGsjvfKZlHnVpG6opxRU+cwKGhot8qGvtDKz52mwQeHqF/J5LTBrN?= >> =?us-ascii?Q?wwM3T+V/F4cgs/fE24QgVzl2BTOJn2Ohh172KuqQe3gQVHNyoctrF8GY69Wr?= >> =?us-ascii?Q?ZdA91VGjzOaOwzvS3o6hiRd9+nTQpKW8i5tMm1JijomEIB9xMBwKr2bRghtQ?= >> =?us-ascii?Q?T0ZHk8moi2xZ+YGGBxrCvwF3wrh0rYKlpBLI0cukVA/JE953p5mh/o+pxiqN?= >> =?us-ascii?Q?QU6N4+PFVaCECuzZGOA8qUWj/olbptek3jcHFdN3QzVIxoewafDdGqQC2LkS?= >> =?us-ascii?Q?uqryRtXJ0ByrECiBklbTNAozfeoQaECHzxSfzqLb74cXKjcgiUxMrX84jGMm?= >> =?us-ascii?Q?twEZHaIS+WftP7G7Hp1ZOgh2OBifrC6Cj01PHA3bcbdpnb1vH+pnd1CFh423?= >> =?us-ascii?Q?L9tgDFuiVKJLBdefLR2BtDRHXtiV6eh/n7UicFedOAHKxzA+qm8eJxzzAWNA?= >> =?us-ascii?Q?dpeSCZFQYfYD26UdNEnSvwFhq/6lokkTd/bzOOq9uz5s1z9zdnyzGGEHMwzf?= >> =?us-ascii?Q?zxeNSO6KmAg+K6+UhLb3Yaue6j0fVri9k/gPwxxMZ7ngHXtyElsl9mFD7Goh?= >> =?us-ascii?Q?8XkOF6r0LJ/7VEfRWsF6dqDsSENUUvOvwqBsZMb02iplXLVaZd+QWGoyDOPv?= >> =?us-ascii?Q?K4SZUGQfnkTU0PiyaSoQ/wMBaMgcXAHBYsjh9hcUzFbpIHZgRkagU8B/aHcH?= >> =?us-ascii?Q?eBGYmR3D6EIfhlGCcv7nfzzGnPOm8XXJd6d+Wh4DunVl3x8Sf9vgRzHshm2G?= >> =?us-ascii?Q?ijUgW6zB/m4nFcT0RGW4Mq4lJoUcMbc3/vo4MZWiWgkM+e5CN665fd7iuY2Y?= >> =?us-ascii?Q?L8qRSp0oBILpqHdMHNVjA7mGuvfL26fTaeZy9ORS8/1ozBu0cmiUDIxJhClv?= >> =?us-ascii?Q?nllloM+jgmtrUjPkwH22RMfwurVnJ4SDfSfp8DHetb4q09k26ONBXjYIlQxV?= >> =?us-ascii?Q?uO57a5vqj+DoNjNTRqJAH56k/uh5kvid+ag/cl07kF2Xvst9ZSqnlUWUB+Ng?= >> =?us-ascii?Q?PHC4WPQ68t2YwRVop/+v45A3DvR5t9OeuNiIWe3EaCppJqHulsbqlSxhN63D?= >> =?us-ascii?Q?EA47ZgIRS0Bjbjr10tExySYR7jpIFHpKsrPVSV4hAgRab+2oW1cT1BriiTyS?= >> =?us-ascii?Q?6vTA/I6hE1uisnojKKNbZ2OpEwDCRsERt6IcHq6hAnJzpTmsbNg4o5HZmyx7?= >> =?us-ascii?Q?OokE99sigMCAwRqlzmdFP9mjAM4sD/nklXMVLxp8o66pNyP1LW2f1CqDOdwT?= >> =?us-ascii?Q?y9DfLClUMntXfgpn0efuqwdkArN6ryw=3D?= >> X-Forefront-Antispam-Report: >> CIP:104.47.51.49;CTRY:US;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:NAM02-BN1-obe.outbound.protection.outlook.com;PTR:mail-bn1nam02lp2049.outbound.protection.outlook.com;CAT:NONE;SFS:(13230037)(2040899010)(35042699019)(7093399009);DIR:INB; >> X-OriginatorOrg: accountprotection.microsoft.com >> X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Jun 2024 19:26:15.1045 >> (UTC) >> X-MS-Exchange-CrossTenant-Network-Message-Id: dd284ca5-87e6-4e3e-2aa8-08dc92f12ef4 >> X-MS-Exchange-CrossTenant-Id: 5ba90553-c2cd-460e-b5fd-ab93ad9155c7 >> X-MS-Exchange-CrossTenant-AuthSource: >> DS2PEPF0000343F.namprd02.prod.outlook.com >> X-MS-Exchange-CrossTenant-AuthAs: Anonymous >> X-MS-Exchange-CrossTenant-FromEntityHeader: Internet >> X-MS-Exchange-Transport-CrossTenantHeadersStamped: SA0PR16MB3838 >> >> >> >> >> ---------- Forwarded message ---------- >> From: "دانا یزدانی" <danayzdanyyzdanydana(a)gmail.com> >> To: postmaster <postmaster(a)accountprotection.microsoft.com> >> Cc: >> Bcc: >> Date: Sat, 22 Jun 2024 22:55:57 +0330 >> Subject: RE: deliverable: Fwd:deliverable >> Re://localhost:26543/storage/0000-5979/%D9%BE%D9%88%D8%B4%D9%87+%D9%BE%D8%A7%D8%B1%D8%AA+%D8%AD%D8%B3%D8%A7%D8%A8+%D8%A8%D8%A7%D9%86%DA%A9+%D9%85%D9%84%D8%AA/%2C000R.htmlDevice >> deliverable Money Amounts 20,000,000,000,000Rial Send To has ben Address >> Account IR210120000000009403817784 Bank Name Bank Mellat-50070 2 Net Name >> IR-SITS-CO-20110530 3 Client HOSAIN ROSALIE Name Domains Bankmellat.ir Bank >> Address 6 IP Domains 176.56.156.36/0 7 Bank Tell >> >

1 0

Minutes from RIPE 88
by Raymond Jetten 11 Jun '24

11 Jun '24

Dear list members, here are the draft minutes from the IPv6 wg session held during ripe88 if you have any comments, please let us know as soon as possible, preferably this week. Much thanks to the RIPE NCC for taking the minutes. IPv6 Working Group RIPE 88 Thursday, 23 May 2024, 11:00-12:30 (UTC+2) Chairs: Christian Seitz, Jen Linkova and Raymond Jetten Scribe: Evelien Schilder Status: Draft View the recordings<https://ripe88.ripe.net/programme/meeting-plan/ipv6-wg/> View the stenography transcript<https://ripe88.ripe.net/archives/steno/41/> View the chat logs<https://ripe88.ripe.net/archives/chat/41/> 1. Welcome The presentation is available at: https://ripe88.ripe.net/archives/video/1352/ Raymond welcomed everyone. The minutes of RIPE 87 were approved. He thanked Jen Linkova for chairing the IPv6 Working Group since RIPE 67 and acknowledged her outstanding work. 2. Co-Chair-Change The presentation is available at: https://ripe88.ripe.net/archives/video/1354/ Jen Linkova stepped down as an IPv6 Working Group chair. Nico Schottelius was selected to replace Jen as a new IPv6 Working Group chair. 3. Operational Issues Discovered During IPv6-mostly Migration Jen Linkova, Google The presentation is available at: https://ripe88.ripe.net/archives/video/1355/ Jen discussed recommendations and operational issues related to IPv6-mostly migration. Jordi Palet Martinez, The IPv6 Company, said that he disagreed with Jen's recommendation to not use DNS64. Jed replied that it may be needed, operational experience was necessary to see how many legacy systems rely on it, because this is currently clear. Jordie said that in his experience when you disable DNS64 and you have CLAT, when reaching IPv4 only destinations, two translations are needed - CLAT and PLAT. This means extra translation and extra power needed. Given the low level of deployment and usage of DNSSEC, there is an increase in deployment of IPv6 in content providers, the ability to enable for example, in BIND, doesn't break DNSSEC, and some hosts are already doing AAAA synthesis. He has not found customers with problems with breaking DNSSEC, even for big deployments. Having vendors implement AAAA synthesis is more useful than disabling DNS64. Jen Linkova replied that it's a controversial part of the document. She thanked Jordi and asked him to continue this on the list. Ondřej Caletka, RIPE NCC, said that the RIPE NCC Tech Team ran this experiment this morning where they disabled DNS64 on the IPv6-mostly network. He said that nothing should break, because either the device would be running dual stack or running IPv6-only. There might be less efficiency. All these issues are from people who actively changed the default configurations of their devices, so he was interested in fixing these issues in Linux and was happy that the IPv6-mostly network worked during this meeting. Jen asked if Ondrej would volunteer to get CLAT done for Linux. Ondrej replied he's already working on that, so things are happening. There was also a project sponsored by the NLnet Foundation, so things were happening. Jen thanked him and said the discussion should continue. Yoshinobu Matsuzaki, IIJ, said they deployed an IPv6-mostly network at the APRICOT conference in February, and they used an enterprise access point. It's too smart, as it assures the client has DHCP and IPv4 address and if the client does not require IPv4, the access point automatically kicks out the association every 10 minutes. Jen answered that Cisco was supposed to fix that a while ago. Yoshinobu added that one has to be careful when configuring such an access point. Jen said it was a good point and that they need to add that to the document. 4. IPv4-with-IPv6 Next-Hop Tobias Fiebig The presentation is available at: https://ripe88.ripe.net/archives/video/1358/ Tobias Fiebig (MPI-INF / AS59645) suggested an end to making IPv4-driven addressing plans. He recommended following RFC 8950 and said that IPv4 with IPv6 next hop is the future. This allows one to fully leverage the available IPv4, to build a clean IPv6-centric addressing scheme and to have IPv4 as a flexible add-on with a central IPv4 IPAM. Nico Braud-Santoni, Funkfeuer Graz, asked that Tobias mention IPv4 forwarding to an IPv6 next hop on Linux with net link. He also asked if Tobias could clarify what he meant and under which conditions this would work. Tobias Fiebig, MPI-INF, said he didn't have the exact kernel version but with the Debian 12 or Ubuntu 20.04, 22.04, you can just tell your routing stack on Linux to use a v6 next hop for a v4 route. So it's "ip route add default via inet6 fead:..." and it sends packets. Robert Scheck said that for RFC 9850 support, Tobias hadn't mentioned OpenBGPD. He asked if Tobias had considered OpenBGPD. Tobias said that he believed that it was on the road map. Maria Matejka, Bird/CZ.NIC, thanked Thomas for using documentation prefixes in his presentation. She said she can't remember when she saw a presentation using strictly the documentation prefixes even for IPv4, it must have been years ago. Tobias answered that he was currently teaching data networks and they have a lot of prefixes on the slides and the postdoc who had to revise the slides really, really hates him. Jen commented that Tobias had said that you get less capability of traceroutes for IPv4. She said that if your routers do the right thing, you do not lose anything. You might lose some capabilities if you have multiple L3 links between two devices. Tobias answered that she might be overestimating the number of IPv4 addresses in the test setup. He said there was no IPv4 on loopback. Jen said she would need to think about this further. Stefan Pantelmann, AVM, asked if Tobias had compared his approach to other existing protocols working with IPv4 and IPv6, let's say MAP-T or MAP-E? Tobias answered that he hadn't made a comparison, and that this was not a protocol, it was just routing and forwarding packets. There is no state, there is no translating, it was just forwarding packets and was also not that relevant for client networks. This was more to get it to virtual machines and things that provide services. Stefan said they had five or six different modes now in their routers that deal with whether the provider offers full dual stack, DS-Lite or minor form etc. They did not have this as of now and how could it be done. Tobias said he hadn't looked at it. Access was the wrong side of the stack for him. Joerg Jungermann (Northern Data AG) said he's been experimenting since 2019. He commented that it makes your network easier and he's happy to work in an environment where they have IPv6 as a first class citizen. They operate a cloud and having a greenfield deployment makes the network very easy to manage and to route IPv4 addresses to the clients. Tobias thanked him and said that if someone was running an IX to please drop him an email. He is looking to access to the peering LAN, a little bit of backhaul and a small virtual machine and the IX members can play with this. 5. IPv4-mapped IPv6 Addresses Ondřej Caletka, RIPE NCC The presentation is available at: https://ripe88.ripe.net/archives/video/1361/ Ondřej spoke about IPv4-mapped IPv6 addresses, which are used for IPv4 compatibility in IPv6 socket API. They are not meant to be used anywhere on the Internet but apparently some people are putting them into public DNS for cost saving reasons. Maria Matejka, Bird / CZ.NIC, said that Ondřej should have used fax to contact the German company, they would take it seriously. Ondřej thanked Maria for the comment. Nico Braud-Santoni, Funkfeuer Graz, asked if DNS providers' authoritative or resolvers could alleviate the problem by providing A records as auxiliary data on AAAA queries, perhaps only in cases where no native IPv6 address is available. Ondřej thought it might be possible. Alexander Zubkov, Qrator Labs, said that the high cost for missing AAAA might be due to less caching time. One solution could be to implement an IPv6 service. Ondrej answered that the best way to solve this was by implementing IPv6. Jen said she agreed that it is necessary to provide clear guidance. She thought it should go in the Happy Eyeballs v3. There is a draft and has a section about broken AAAA records. The text is on GitHub. Ondrej agreed that it was a good idea. Tobias Fiebig, MPI-INF, said he recently got a lot of DNS data and asked if Ondrej wanted to know how bad it was. He could ask a student to run the data. Ondrej answered that Tobias could share it with the IPv6 Working Group or DNS Working Group if it's about broken DNS. Tobias said that he would look into it. Oleksij Samorukov, NetArt Group, said that v6/v4 compatible is a bad idea as it could break layers in a strange way. He also said it would be interesting to run a global survey on some big DNS registry databases. Ondrej answered that this was discussed in the IPv6 mailing list, as well as in an incident report from GitHub. They started preparing for the IPv6 rollout and they found the issue that IPv4-mapped IPv6 addresses started causing trouble for them. Raymond Jetten, RIPE NCC Executive Board, said that Ondřej has a volunteer for deploying IPv6 at GitHub and that it's Jordi. Blake Willis, Zayo Europe, commented that you will find that folks that may be running 6PE in their networks, meaning IPv6 with a labelled Unicast next hop which would be IPv4 Unicast BGP sessions. With JunOS, the router will synthesise one of these address with ::ffff: and the IPv4 loopback of the remote BGP network. Now the next hop is a label but it needs something to resolve the next hop. He didn't think that the actual packet has a IPv4-mapped next hop on the wire, but the address might be seen. Ondřej answered that it's the same case as the host behaviour because you have a 128-bit field and you have to fill it somehow with a 32-bit number. Philipp Tiesel, SAP, had two comments. He said he always considers these types of addresses as a IPv4 address so the behaviour is quite consistent to what he would have expected even if we should be putting this in AAAA records. He's asking if Ondrej tried to use it to force a DNS64 IPv6-only host to use the CLAT because this is what he would expect to work. He suggested to taking a macOS, take an AAAA record and see whether one can avoid DNS64 synthesis, and see whether that works. Ondrej said he was not sure if he could follow the suggestiong but was open to trying it out. Tom Hill (BT) asked whether the record DNSSEC was signed. Ondrej answered that it was. Tom Hill then asked if Ondřej was aware of NSEC. Not having a record if NSEC is enabled can cost you a lot of money potentially. Ondrej then said that it was a good point, so maybe the charging scheme of the cloud DNS provider makes sense, but it doesn't make sense as people put wrong data in DNS. Tom said he didn't have a good answer to that. 6. Thanks, Wrap Up and Rate the Talks Working Group Chairs The presentation is available at: https://ripe88.ripe.net/archives/video/1362/ Raymond thanked the working group and reminded everyone to rate the talks. The session was concluded. Raymond Jetten Senior Technology Specialist Production Cloud Services, Networks and connectivity Interconnectivity & Content Elisa Oyj Vuolteenkatu 2 33100 Tampere +358 45 6700 139 raymond.jetten(a)elisa.fi<mailto:raymond.jetten@elisa.fi> www.elisa.fi<http://www.elisa.fi/> Lisätietoa henkilötietojen käsittelystä ja tietosuojasta Elisalla https://elisa.fi/tietosuoja Mer information om Elisas hantering av personuppgifter och dataskydd https://elisa.fi/tietosuoja More information on personal data management and data protection at Elisa https://elisa.com/dataprotection ********************************************************************************************* For Internal Use Only

3 2

danayzdanyyzdanydana@gmail.com
by دانا یزدانی 31 May '24

31 May '24

09392430244

1 0

New IPv6-wg co chair
by Raymond Jetten 10 May '24

10 May '24

Dear IPv6-wg list members and RIPE community. In response to our requests on the list to find a new co-chair we are glad to announce that we have 1 interested candidate: Nico Schottelius Jen Linkova, who has been one of the co-chairs of the IPv6 Working Group since RIPE 69 has announced she wishes to step down at the RIPE 88 meeting in Kraków, at the end of her term. The deadline for candidates has now passed, so we are glad to welcome Nico to the IPv6-wg He may send in his personal message to this list soon. The change of co-chair will be done at the ripe 88 meeting in Krakow during our session. Best regards, The IPv6 WG chairs. For Internal Use Only

4 3

IPv6 WG agenda for RIPE88
by Christian Seitz 17 Apr '24

17 Apr '24

Dear IPv6 working group, we found some great presenters for our next IPv6 WG session in Krakow and built an agenda. Our session will take place on Thursday 23 May 2024 from 11:00 - 12:30 CEST. The agenda will also be published in the RIPE88 meeting plan [1] soon. 1. Welcome ([5 min] * Opening and Welcome * Approval of RIPE 87 Minutes * Microphone Etiquette 2. Co-Chair-Change [10 min] 3. Operational issues discovered during IPv6-mostly migration [30 min incl. Q&A] Jen Linkova 4. IPv4-with-IPv6 Next-Hop [20 min incl. Q&A] Tobias Fiebig 5. IPv4-mapped IPv6 addresses [20 min incl. Q&A] Ondřej Caletka 6. Thanks, Wrap Up and Rate the Talks [5 min] If there are any changes to this agenda we will send an update and also update the meeting plan on the website [1]. [1] https://ripe88.ripe.net/programme/meeting-plan/ On behalf of the IPv6 WG co-chairs, Jen, Ray and Chris

1 0

IPv6 torrent and non-GUA addresses
by Marco Moock 14 Apr '24

14 Apr '24

Hello! I want to share some experience and ask if other people here also noticed that behavior. I operate an IPv6 torrent client (qbittorrent/libtorrent) and I noticed various things: The client itself sometimes uses non-GUA source addresses when connecting to GUA addresses in the default setting. When binding to the GUA address only, it uses only them. https://github.com/qbittorrent/qBittorrent/issues/19618 This seems to be not yet fixed. I also notice a reasonable amount of incoming traffic with non-GUA addresses like from 63ed:b73b::/32 or 485f:1207::/32, ac11:1::/32 etc. This also shows that some ISPs don't seem to prohibit their customers from sending such packages. Does anybody here also experienced that? Is there any monitoring at exchange points to find the source? -- kind regards Marco Send unsolicited bulk mail to 1711396344muell(a)cartoonies.org

2 3

No more Google IPv6 stats?
by Mat Ford 05 Apr '24

05 Apr '24

End of an era? https://www.google.com/intl/en/ipv6/statistics.html has no data since Feb 25th. The (lack of) growth over the last 9 months is hardly encouraging either.

2 1

We are still looking for co-chair candidates
by Raymond Jetten 03 Apr '24

03 Apr '24

Dear IPv6 Working Group, We are still looking for candidates to be a IPv6-WG co- chair. Are you interested? Drop us (the current chairs) a mail. ipv6-wg-chair(a)ripe.net<mailto:ipv6-wg-chair@ripe.net> Please do not send it to the list. Or do you know anyone who could be suitable and interested? Ask them to stand up and drop the co-chairs an email. Below is a copy of the earlier request: Jen Linkova, who has been one of the co-chairs of the IPv6 Working Group since RIPE 69 has announced she wishes to step down at the RIPE 88 meeting in Kraków, at the end of her term. Thus, we have a call for candidates. The term of a IPv6 WG co-chair is three years. A current co-chair may stand for re-selection at the end of their term or may resign voluntarily at any time. What is the IPv6 WG doing: The working group activities may be anything useful in helping people to deploy IPv6, and to manage IPv4/IPv6 co-existence. These activities include: Outreach Education Sharing deployment experiences Discussing and fixing operational issues The co-chairs also prepare the program for the IPv6 WG session at the ripe meetings. The working group will cooperate with operators and others, both inside and outside the networking industry, to share resources and combine efforts. The tasks and expectations of a WG co-chair are described here: https://www.ripe.net/publications/docs/ripe-692 A WG co-chair must comply with the Code of Conduct: https://www.ripe.net/publications/docs/ripe-766 If you feel you are interested in this or have any questions on this, you can drop the current co-chairs a note ipv6-wg-chair at ripe.net We kindly request you to respond at latest Friday 3-May-2024 midday CET (Amsterdam), when the call for candidates will be closed. After this we will announce the candidates on the list, and you can express your support or concerns. However the official selection will take place at the RIPE 88 Meeting in Kraków during the IPv6 Working Group session. On behalf of the IPv6 WG co-chairs, Jen, Christian & Ray RIPE IPv6 Working Group co-Chair To the co Chairs: ipv6-wg-chair at ripe.netmailto:ipv6-wg-chair at ripe.net<mailto:ipv6-wg-chair%20at%20ripe.net> To the mailing list: ipv6-wg at ripe.netmailto:ipv6-wg at ripe.net<mailto:ipv6-wg%20at%20ripe.net> For Internal Use Only

1 0

Re: [ipv6-wg] RIPE 88, presentations and a co chair change.....
by Thomas Schäfer 27 Mar '24

27 Mar '24

>> united by Postbank/Deutsche Bank, new relic, ns1, ibm, fastly and others To blame fastly wasn't right. That was my fault. Thank you Job Snijders for clarification. Regards, Thomas

1 0

RIPE 88, presentations and a co chair change.....
by Raymond Jetten 27 Mar '24

27 Mar '24

Dear IPv6 wg list members. In about 2 months, we will meet in Krakow, and ofcourse online. We still need presentations for the meeting, and we also need candidates to be our new collegue. For both you can send us (the chairs) your either presentation proposals or let us know that you are interested in becoming an IPv6-wg co chair. See our previous messages: Hello All, RIPE 88 will be held in Krakow, Poland from 20-24 May 2024, as well as online. For any participation form you can register here: https://ripe88.ripe.net/attend/register/ The IPv6 Working Group session is scheduled for Thursday 23 May from 11:00 . 12:30 (UTC+1) We are looking for presentations - please email : ipv6-wg-chair (at) ripe.net if you'd like to present. Please also state if you intend to be online or onsite, and the duration of your presentation, and a short description of it. Once we have decided on the agenda, we'll contact the presenters closer to the meeting. Hope to see as many of you as possible, On behalf of the IPv6-WG Christian, Jen, Ray And the co-chair position: Dear IPv6 Working Group, Jen Linkova, who has been one of the co-chairs of the IPv6 Working Group since RIPE 69 has announced she wishes to step down at the RIPE 88 meeting in Kraków, at the end of her term. Thus, we have a call for candidates. The term of a IPv6 WG co-chair is three years. A current co-chair may stand for re-selection at the end of their term or may resign voluntarily at any time. What is the IPv6 WG doing: The working group activities may be anything useful in helping people to deploy IPv6, and to manage IPv4/IPv6 co-existence. These activities include: Outreach Education Sharing deployment experiences Discussing and fixing operational issues The co-chairs also prepare the program for the IPv6 WG session at the ripe meetings. The working group will cooperate with operators and others, both inside and outside the networking industry, to share resources and combine efforts. The tasks and expectations of a WG co-chair are described here: https://www.ripe.net/publications/docs/ripe-692 A WG co-chair must comply with the Code of Conduct: https://www.ripe.net/publications/docs/ripe-766 If you feel you are interested in this or have any questions on this, you can drop the current co-chairs a note: ipv6-wg-chair at ripe.net We kindly request you to respond at latest Friday 3-May-2024 midday CET (Amsterdam), when the call for candidates will be closed. After this we will announce the candidates on the list, and you can express your support or concerns. However, the official selection will take place at the RIPE 88 Meeting in Kraków during the IPv6 Working Group session. On behalf of the IPv6 WG co-chairs, Christian, Jen, Raymond RIPE IPv6 Working Group co-Chair To the co Chairs: ipv6-wg-chair(a)ripe.net<mailto:ipv6-wg-chair@ripe.net> To the mailing list: ipv6-wg(a)ripe.net<mailto:ipv6-wg@ripe.net> For Internal Use Only

7 8