[mailop] Outlook misinterpreting the Sender field ?
Hello list, this is my frst time posting here but I really need to share this weird behaviour. So I'm one of the administrator of a big mailing lists server. One of our user complained that when the subscribers to her list wrote to the list, only she received the message. Which is not possible, due to the very mechanisms of the Sympa mailing list software that we're using. I noticed, by one of her reports, that the users did not send a message to the list, but to the list owners. This is the almost the same address. If a list has the address, "myl...@mydomain.com", then the owners have the address "mylist-requ...@mydomain.com". But why did they write to this address? It's only when I had a videoconference with my user that I could see that, in her Outlook client, when displaying a message from the list, it read something like "mylist-requ...@mydomain.com ". And hen clicking on it, the "-request" address was emphatized. It is therefore very easy to copy this address and paste it in a new message. The "-request" address only appears in the "Sender" field. As per RFC 2822 : "The "From:" field specifies the author(s) of the message, that is, the mailbox(es) of the person(s) or system(s) responsible for the writing of the message. The "Sender:" field specifies the mailbox of the agent responsible for the actual transmission of the message." Absolutely no reason to display it to end user as the actual mail originator. It makes sense to give it as information, but displaying the way it is to end users is totally misleading. In order to stop mayhem in those lists, I had to make Sympa remove the "Sender" header from outgoing emails. But who knows what side effect will this change have for deliverability ? Do you know if there is an actual rationale behind this behaviour (which looks like it appeared recently) ? Best regards, David -- "À un certain niveau, le sport n'a plus rien à voir avec le fair-play. Il met en jeu la haine, la jalousie, la forfanterie, le mépris de toutes les règles et le plaisir sadique que procure le spectacle de la violence. En d'autres termes : c'est la guerre, les fusils en moins." - Georges Orwell David Verdin La Fabrique Direction des Services Applicatifs RENATER - Rennes smime.p7s Description: Signature cryptographique S/MIME ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Still Don't understand Google's relaying systems.. Duplicate Return-Path, and other things..
Not to be 'snide' Atro, but that part is pretty obvious.. It was the technical details I was searching for, on HOW it is able to relay from those IPs.. please review the original post again.. I thought I was clear on that.. This doesn't appear to be the standard relay path/source/methods.. On 2023-10-25 12:45, Atro Tossavainen via mailop wrote: Maybe Brandon can weigh in on or off list, but is there a a way for spammers to simply relay out Gmail servers if they are Google Cloud? $ host -t txt sredplus.com sredplus.com descriptive text "google-site-verification=gyoD4DWS9XSrAmz9s5Pc9OBLvvowksBJtB0Oi-DAlsQ" sredplus.com descriptive text "v=spf1 mx include:_spf.google.com include:24145163.spf02.hubspotemail.net include:sendgrid.net -all" $ host -t mx sredplus.com sredplus.com mail is handled by 10 alt3.aspmx.l.google.com. sredplus.com mail is handled by 5 alt2.aspmx.l.google.com. sredplus.com mail is handled by 5 alt1.aspmx.l.google.com. sredplus.com mail is handled by 1 aspmx.l.google.com. sredplus.com mail is handled by 10 alt4.aspmx.l.google.com. I guess those two tell you everything you need to know: their email infrastructure is Google, they're just using it for cold email^W^W spam in addition to their regular stuff. This is really commonplace these days. -- "Catch the Magic of Linux..." Michael Peddemors, President/CEO LinuxMagic Inc. Visit us at http://www.linuxmagic.com @linuxmagic A Wizard IT Company - For More Info http://www.wizard.ca "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd. 604-682-0300 Beautiful British Columbia, Canada This email and any electronic data contained are confidential and intended solely for the use of the individual or entity to which they are addressed. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- "Catch the Magic of Linux..." Michael Peddemors, President/CEO LinuxMagic Inc. Visit us at http://www.linuxmagic.com @linuxmagic A Wizard IT Company - For More Info http://www.wizard.ca "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd. 604-682-0300 Beautiful British Columbia, Canada This email and any electronic data contained are confidential and intended solely for the use of the individual or entity to which they are addressed. Please note that any views or opinions presented in this email are solely those of the author and are not intended to represent those of the company. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Still Don't understand Google's relaying systems.. Duplicate Return-Path, and other things..
On Thu, Oct 26, 2023 at 10:07:30AM -0700, Michael Peddemors via mailop wrote: > Not to be 'snide' Atro, but that part is pretty obvious.. You would have thought so - I would have thought so too. Which is why I reacted that way to your asking about it. > It was the technical details I was searching for, on HOW it is able > to relay from those IPs.. please review the original post again.. I > thought I was clear on that.. They're a legit Google customer. What's there to marvel at? -- Atro Tossavainen, Founder, Partner Koli-Lõks OÜ (reg. no. 12815457, VAT ID EE101811635) Tallinn, Estonia tel. +372-5883-4269, https://www.koliloks.eu/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
[mailop] Need Help with Google Deliverability Issue
I have recently migrated one of our customers from Google to Office365 and have been encountering deliverability issues when sending to Google-related domains. All other domains are perfectly fine and haven't seen any issues. Listed below are the headers for a bounced email to a Gmail account: ARC-Seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=IUdOSeOS2v8fBqFRT+2+ob/64xDWHCrxU6br11+L6Gjlytj2kEMHoVq7TCpkgY1uKHg/IxVBQh1bpLReem8wfvKVM4ncibBVmls1IAmgt/fFxBThm7Vgfc3HZUlmk0NYy+0ifABUO8cVWXE9nz0/XyjTXfmI2lo0CX4Ysgk+mN5FxmFHz1yCDYJomM0k8Naxr7+nO8d9TC7TQ/U2QlH6aHfa2I+kHP/vxNAYPumA6At7aBtXh7o5ULqNt3LDrW/tTJua/8M6Z5KZccU2GHa/wlEaaEH4g9/cLSPGn28kDx5bj1j5jMdl7zXjnETZYymGCEKFJwJMOFecCl3kI4YX7g== 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=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; b=MveUHC2brc6+/jbu/Q1RrDABPlHSagEN1omoqqUmP04RPTk60M+AZtFEC2tF2LImub4A1RvvL/w9FjP+lysSfftGpywNPazJHaPgGiW44cqS2S84sGkJFDgHCivhnSfBKYBKHFGvAZhjYe16CXWERd//M0u/yGtTRPoG8J/OSKUcugiMpsburQ6ffOHOmRLERu+w8fBKn7A+4rwIDoKP2/efhZNJ7xQWk/Z6MAB32UXmxWPYOY+/kUMRyQ1Z5Sf2ZAT9MoRnVldID4W9HeGMA75Ticxl8Dt0e/Q+XoD4f7BEHKpwoznNEr9HSLNQXkQSbSuPharKncn3fZEyIbQh6A== ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 198.154.181.224) smtp.rcpttodomain=gmail.com smtp.mailfrom=richmond.bbb.org; dmarc=pass (p=none sp=none pct=100) action=none header.from=richmond.bbb.org; dkim=pass (signature was verified) header.d=richmond.bbb.org; dkim=pass (signature was verified) header.d=mail-dkim-us-west-2.prod.hydra.sophos.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=richmond.bbb.org] dkim=[1,1,header.d=richmond.bbb.org] dmarc=[1,1,header.from=richmond.bbb.org]) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=richmond.bbb.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; b=IBp6WddL0tAEtjsUg9TLjHYmU5nmyIqGMASfttCAkZzzJQLOspzOwgifiLEXyz3lfCwmIC89UkBptAT4Z0p5sFvDUNDTtWkMoK5nPxNpjJAZenjDXSrwRfwcj0WOjcLV7VaIvVYyEs2Db+8tikyWrR2VJ2I9iNAYJkIWqwP50u9jcPYUj3FHKR44B7cxTz1VXeegS2RPjZ968HuIvKsGx6gKSgtWobvcPsYgNA3apo1BZ/Y+i3h7cGx1cdJJPED5uyyeIj8dZ/l28DoMSETkT29DVqCcKvgbVQUyM2URBFUgvksANuYRRjFcE119QOlQSsyGyl1ligENnsozK5MyYQ== Received: from DM6PR07CA0095.namprd07.prod.outlook.com (2603:10b6:5:337::28) by CO6PR04MB8329.namprd04.prod.outlook.com (2603:10b6:303:134::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.22; Thu, 26 Oct 2023 19:00:26 + Received: from DS1PEPF0001708E.namprd03.prod.outlook.com (2603:10b6:5:337:cafe::30) by DM6PR07CA0095.outlook.office365.com (2603:10b6:5:337::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.19 via Frontend Transport; Thu, 26 Oct 2023 19:00:25 + X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 198.154.181.224) smtp.mailfrom=richmond.bbb.org; dkim=pass (signature was verified) header.d=richmond.bbb.org;dmarc=pass action=none header.from=richmond.bbb.org; Received-SPF: Pass (protection.outlook.com: domain of richmond.bbb.org designates 198.154.181.224 as permitted sender) receiver=protection.outlook.com; client-ip=198.154.181.224; helo=mfod-usw2.prod.hydra.sophos.com; pr=C Received: from mfod-usw2.prod.hydra.sophos.com (198.154.181.224) by DS1PEPF0001708E.mail.protection.outlook.com (10.167.17.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.18 via Frontend Transport; Thu, 26 Oct 2023 19:00:25 + Received: from ip-172-17-2-248.us-west-2.compute.internal (ip-172-17-2-248.us-west-2.compute.internal [127.0.0.1]) by mfod-usw2.prod.hydra.sophos.com (Postfix) with ESMTP id 4SGZqr6KmBzdZMC for mailto:markwstanley2...@gmail.com>>; Thu, 26 Oct 2023 19:00:24 + (UTC) X-Sophos-Product-Type: Mailflow X-Sophos-Email-ID: 331699fdd3364172b148bf658ab8ad0a Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12lp2169.outbound.protection.outlook.com [104.47.59.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mf-outbound-usu-west-2.prod.hydra.sophos.com (Postfix) with ESMTPS id 4SGZqq1wzhzRhQn for mailto:markwstanley2...@gmail.com>>; Thu, 26 Oct 2023 19:00:23 + (UTC) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kJDl3l74RdoxT1QOA0ix5VgwvFhYhqzcUgGkZr0vhcxIyulP8EGiqJBMBBHFnEBAvzwYh6Wl3yoAV1RR5U6jCUuNWAHYG6lqhXMRycSJXMZCbJGY+k8DMwhMVOY48VMec+GZ8SzQOfjzIzoZ3eF6eLKvgc9ZVRyIP4y5EV3oOxn1SXnNP4uXC9Y6X+FLUW00R/RTiHFPlytHt4hhEktZ/5bGIMHknGHbLhcfsulVbFAfDPxCuI0lqwkpTOrlX4EjOEI09nEXghzxBhAOUmLX4eFJBcRfzMlUDlriv6gyYniTKeOVNuwn7eOb6Smy4W7STqkRth8Z48BmFYVCce
Re: [mailop] Still Don't understand Google's relaying systems.. Duplicate Return-Path, and other things..
> They're a legit Google customer. What's there to marvel at? https://developers.google.com/gmail/api/guides <- have a look. -- Atro Tossavainen, Founder, Partner Koli-Lõks OÜ (reg. no. 12815457, VAT ID EE101811635) Tallinn, Estonia tel. +372-5883-4269, https://www.koliloks.eu/ ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] [External] Need Help with Google Deliverability Issue
Mark, was there a bounce message with any information? Send a message to raptorloopb...@raptoremailsecurity.com and that will tell you what that spam scanner sees to check your SPF, DKIM, DMARC, etc. Regards, KAM On 10/26/2023 3:13 PM, Mark Stanley via mailop wrote: I have recently migrated one of our customers from Google to Office365 and have been encountering deliverability issues when sending to Google Raptor Remark: Please be careful! This email is from an EXTERNAL sender. Be aware of impersonation and credential theft. I have recently migrated one of our customers from Google to Office365 and have been encountering deliverability issues when sending to Google-related domains. All other domains are perfectly fine and haven’t seen any issues. Listed below are the headers for a bounced email to a Gmail account: ARC-Seal: i=2; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=pass; b=IUdOSeOS2v8fBqFRT+2+ob/64xDWHCrxU6br11+L6Gjlytj2kEMHoVq7TCpkgY1uKHg/IxVBQh1bpLReem8wfvKVM4ncibBVmls1IAmgt/fFxBThm7Vgfc3HZUlmk0NYy+0ifABUO8cVWXE9nz0/XyjTXfmI2lo0CX4Ysgk+mN5FxmFHz1yCDYJomM0k8Naxr7+nO8d9TC7TQ/U2QlH6aHfa2I+kHP/vxNAYPumA6At7aBtXh7o5ULqNt3LDrW/tTJua/8M6Z5KZccU2GHa/wlEaaEH4g9/cLSPGn28kDx5bj1j5jMdl7zXjnETZYymGCEKFJwJMOFecCl3kI4YX7g== 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=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; b=MveUHC2brc6+/jbu/Q1RrDABPlHSagEN1omoqqUmP04RPTk60M+AZtFEC2tF2LImub4A1RvvL/w9FjP+lysSfftGpywNPazJHaPgGiW44cqS2S84sGkJFDgHCivhnSfBKYBKHFGvAZhjYe16CXWERd//M0u/yGtTRPoG8J/OSKUcugiMpsburQ6ffOHOmRLERu+w8fBKn7A+4rwIDoKP2/efhZNJ7xQWk/Z6MAB32UXmxWPYOY+/kUMRyQ1Z5Sf2ZAT9MoRnVldID4W9HeGMA75Ticxl8Dt0e/Q+XoD4f7BEHKpwoznNEr9HSLNQXkQSbSuPharKncn3fZEyIbQh6A== ARC-Authentication-Results: i=2; mx.microsoft.com 1; spf=pass (sender ip is 198.154.181.224) smtp.rcpttodomain=gmail.com smtp.mailfrom=richmond.bbb.org; dmarc=pass (p=none sp=none pct=100) action=none header.from=richmond.bbb.org; dkim=pass (signature was verified) header.d=richmond.bbb.org; dkim=pass (signature was verified) header.d=mail-dkim-us-west-2.prod.hydra.sophos.com; arc=pass (0 oda=1 ltdi=1 spf=[1,1,smtp.mailfrom=richmond.bbb.org] dkim=[1,1,header.d=richmond.bbb.org] dmarc=[1,1,header.from=richmond.bbb.org]) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=richmond.bbb.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; b=IBp6WddL0tAEtjsUg9TLjHYmU5nmyIqGMASfttCAkZzzJQLOspzOwgifiLEXyz3lfCwmIC89UkBptAT4Z0p5sFvDUNDTtWkMoK5nPxNpjJAZenjDXSrwRfwcj0WOjcLV7VaIvVYyEs2Db+8tikyWrR2VJ2I9iNAYJkIWqwP50u9jcPYUj3FHKR44B7cxTz1VXeegS2RPjZ968HuIvKsGx6gKSgtWobvcPsYgNA3apo1BZ/Y+i3h7cGx1cdJJPED5uyyeIj8dZ/l28DoMSETkT29DVqCcKvgbVQUyM2URBFUgvksANuYRRjFcE119QOlQSsyGyl1ligENnsozK5MyYQ== Received: from DM6PR07CA0095.namprd07.prod.outlook.com (2603:10b6:5:337::28) by CO6PR04MB8329.namprd04.prod.outlook.com (2603:10b6:303:134::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.22; Thu, 26 Oct 2023 19:00:26 + Received: from DS1PEPF0001708E.namprd03.prod.outlook.com (2603:10b6:5:337:cafe::30) by DM6PR07CA0095.outlook.office365.com (2603:10b6:5:337::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.19 via Frontend Transport; Thu, 26 Oct 2023 19:00:25 + X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 198.154.181.224) smtp.mailfrom=richmond.bbb.org; dkim=pass (signature was verified) header.d=richmond.bbb.org;dmarc=pass action=none header.from=richmond.bbb.org; Received-SPF: Pass (protection.outlook.com: domain of richmond.bbb.org designates 198.154.181.224 as permitted sender) receiver=protection.outlook.com; client-ip=198.154.181.224; helo=mfod-usw2.prod.hydra.sophos.com; pr=C Received: from mfod-usw2.prod.hydra.sophos.com (198.154.181.224) by DS1PEPF0001708E.mail.protection.outlook.com (10.167.17.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.18 via Frontend Transport; Thu, 26 Oct 2023 19:00:25 + Received: from ip-172-17-2-248.us-west-2.compute.internal (ip-172-17-2-248.us-west-2.compute.internal [127.0.0.1]) by mfod-usw2.prod.hydra.sophos.com (Postfix) with ESMTP id 4SGZqr6KmBzdZMC for ; Thu, 26 Oct 2023 19:00:24 + (UTC) X-Sophos-Product-Type: Mailflow X-Sophos-Email-ID: 331699fdd3364172b148bf658ab8ad0a Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12lp2169.outbound.protection.outlook.com [104.47.59.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requeste
Re: [mailop] [SUSPECTED SPAM] mailop Digest, Vol 39, Issue 48
gc9ZVRyIP4y5EV3oOxn1SXnNP4uXC9Y6X+FLUW00R/RTiHFPlytHt4hhEktZ/5bGIMHknGHbLhcfsulVbFAfDPxCuI0lqwkpTOrlX4EjOEI09nEXghzxBhAOUmLX4eFJBcRfzMlUDlriv6gyYniTKeOVNuwn7eOb6Smy4W7STqkRth8Z48BmFYVCcexKMw== > > 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=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; > > b=j2oLsbNnA/8EGoq5tIM6WVMrAI8PefNYnRWMOmg9EoJTFxXNOViT1vcYZ1Tv80gLv/WICsLnQTBQrxDExEwVBZ636+WRwdjj9vOo0Mh6+O/mt8PDPxGLP+DfAxi0O000rB7d0hsQ6gugFt17fTwmrY7shWwVS94HM1SYFtcwpAJgeWLMJhgBrFCvWl1NzFtK7kLcmEzZL2RKCY+jy2MzFQMBJIcwM1G9pImeuxXM8evpuih/Q7GTnBivqS7Al2c4W0JnJCFoLopkJGYcTDddHPbg5PpopBWjR6UrbNXHvlCZeMsXXFQThIv9ZCcQnVgCHJZ4Ou84eskjk6eyRyQnbQ== > > ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass > > smtp.mailfrom=richmond.bbb.org; dmarc=pass action=none > > header.from=richmond.bbb.org; dkim=pass header.d=richmond.bbb.org; > arc=none > > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=richmond.bbb.org; > > s=selector1; > > h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; > > bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; > > b=IBp6WddL0tAEtjsUg9TLjHYmU5nmyIqGMASfttCAkZzzJQLOspzOwgifiLEXyz3lfCwmIC89UkBptAT4Z0p5sFvDUNDTtWkMoK5nPxNpjJAZenjDXSrwRfwcj0WOjcLV7VaIvVYyEs2Db+8tikyWrR2VJ2I9iNAYJkIWqwP50u9jcPYUj3FHKR44B7cxTz1VXeegS2RPjZ968HuIvKsGx6gKSgtWobvcPsYgNA3apo1BZ/Y+i3h7cGx1cdJJPED5uyyeIj8dZ/l28DoMSETkT29DVqCcKvgbVQUyM2URBFUgvksANuYRRjFcE119QOlQSsyGyl1ligENnsozK5MyYQ== > > DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; > t=1698346819; > > s=v1; d=mail-dkim-us-west-2.prod.hydra.sophos.com; > > h=Content-Type:Date:Subject:To:From; > > bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; > > b=jcJw6d6HDGLRjPmeM/Ye+DF43hHJMaao4by5+Jfi6F45SAggkc4D41+8pFSpNk2t > > Qx7LNQOyPjHyJ4K1AqYgL973657era/YNEniTZsHKZS5CIyFqjxQBu73Uk0YkrXzw3W > > L6oNeNo4Bp/kKYZXG8aKNFFBTUkea06TysmByIp4T+AiSUca1JkVpcciwzviaqhoc18 > > lP9L/2U/ORZUDEzh037Jmx0CKYP30w9Ry3fp9cYmfkGUSvY0lIu2fwa5mDodB65OWjp > > uoIFFVzDGfpi28usziso1gO89Ih7n0MMIj6TTrGJx0ZzuxKXZilwUIg9zKNr8ey1Gka > > LtUlmxEqag== > > Received: from BY5PR04MB6706.namprd04.prod.outlook.com > (2603:10b6:a03:22e::24) > > by MN2PR04MB7134.namprd04.prod.outlook.com (2603:10b6:208:1e3::24) > > with Microsoft SMTP Server (version=TLS1_2, > > cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.19; Thu, > 26 Oct > > 2023 19:00:20 + > > Received: from BY5PR04MB6706.namprd04.prod.outlook.com > > ([fe80::4324:9275:a4f7:113c]) by BY5PR04MB6706.namprd04.prod.outlook.com > > ([fe80::4324:9275:a4f7:113c%3]) with mapi id 15.20.6933.019; Thu, 26 > Oct 2023 > > 19:00:19 + > > Any insight into this is greatly appreciated. We have getting bounce > backs for several days now, but experienced a brief period where > Google domains were able to be reached. > > *Mark W. Stanley, Managed Services Engineer* > > Richweb, Inc. / mstan...@corp.richweb.com > > O: 804-368-0421 X 120 > > richweb.com / hvens.com > > > RAPTOR REMARK: Alert! Please be careful! This email is from an EXTERNAL > sender. Be aware of impersonation and credential theft. > > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop -- next part -- An HTML attachment was scrubbed... URL: <https://list.mailop.org/private/mailop/attachments/20231026/96d95649/attachment.htm> -- Subject: Digest Footer ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- End of mailop Digest, Vol 39, Issue 48 ** ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] [SUSPECTED SPAM] mailop Digest, Vol 39, Issue 48
igENnsozK5MyYQ== > > DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; > t=1698346819; > > s=v1; d=mail-dkim-us-west-2.prod.hydra.sophos.com; > > h=Content-Type:Date:Subject:To:From; > > bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; > > b=jcJw6d6HDGLRjPmeM/Ye+DF43hHJMaao4by5+Jfi6F45SAggkc4D41+8pFSpNk2t > > Qx7LNQOyPjHyJ4K1AqYgL973657era/YNEniTZsHKZS5CIyFqjxQBu73Uk0YkrXzw3W > > L6oNeNo4Bp/kKYZXG8aKNFFBTUkea06TysmByIp4T+AiSUca1JkVpcciwzviaqhoc18 > > lP9L/2U/ORZUDEzh037Jmx0CKYP30w9Ry3fp9cYmfkGUSvY0lIu2fwa5mDodB65OWjp > > uoIFFVzDGfpi28usziso1gO89Ih7n0MMIj6TTrGJx0ZzuxKXZilwUIg9zKNr8ey1Gka > > LtUlmxEqag== > > Received: from BY5PR04MB6706.namprd04.prod.outlook.com > (2603:10b6:a03:22e::24) > > by MN2PR04MB7134.namprd04.prod.outlook.com (2603:10b6:208:1e3::24) > > with Microsoft SMTP Server (version=TLS1_2, > > cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.19; Thu, > 26 Oct > > 2023 19:00:20 + > > Received: from BY5PR04MB6706.namprd04.prod.outlook.com > > ([fe80::4324:9275:a4f7:113c]) by BY5PR04MB6706.namprd04.prod.outlook.com > > ([fe80::4324:9275:a4f7:113c%3]) with mapi id 15.20.6933.019; Thu, 26 > Oct 2023 > > 19:00:19 + > > Any insight into this is greatly appreciated. We have getting bounce > backs for several days now, but experienced a brief period where > Google domains were able to be reached. > > *Mark W. Stanley, Managed Services Engineer* > > Richweb, Inc. / mstan...@corp.richweb.com > > O: 804-368-0421 X 120 > > richweb.com / hvens.com > > > RAPTOR REMARK: Alert! Please be careful! This email is from an EXTERNAL > sender. Be aware of impersonation and credential theft. > > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop -- next part -- An HTML attachment was scrubbed... URL: <https://list.mailop.org/private/mailop/attachments/20231026/96d95649/attachment.htm> -- Subject: Digest Footer ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- End of mailop Digest, Vol 39, Issue 48 ** ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
[mailop] gmail deliverability issue was mailop Digest, Vol 39, Issue 48
ith ESMTPS id 4SGZqq1wzhzRhQn for ; Thu, 26 Oct 2023 19:00:23 + (UTC) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kJDl3l74RdoxT1QOA0ix5VgwvFhYhqzcUgGkZr0vhcxIyulP8EGiqJBMBBHFnEBAvzwYh6Wl3yoAV1RR5U6jCUuNWAHYG6lqhXMRycSJXMZCbJGY+k8DMwhMVOY48VMec+GZ8SzQOfjzIzoZ3eF6eLKvgc9ZVRyIP4y5EV3oOxn1SXnNP4uXC9Y6X+FLUW00R/RTiHFPlytHt4hhEktZ/5bGIMHknGHbLhcfsulVbFAfDPxCuI0lqwkpTOrlX4EjOEI09nEXghzxBhAOUmLX4eFJBcRfzMlUDlriv6gyYniTKeOVNuwn7eOb6Smy4W7STqkRth8Z48BmFYVCcexKMw== 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=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; b=j2oLsbNnA/8EGoq5tIM6WVMrAI8PefNYnRWMOmg9EoJTFxXNOViT1vcYZ1Tv80gLv/WICsLnQTBQrxDExEwVBZ636+WRwdjj9vOo0Mh6+O/mt8PDPxGLP+DfAxi0O000rB7d0hsQ6gugFt17fTwmrY7shWwVS94HM1SYFtcwpAJgeWLMJhgBrFCvWl1NzFtK7kLcmEzZL2RKCY+jy2MzFQMBJIcwM1G9pImeuxXM8evpuih/Q7GTnBivqS7Al2c4W0JnJCFoLopkJGYcTDddHPbg5PpopBWjR6UrbNXHvlCZeMsXXFQThIv9ZCcQnVgCHJZ4Ou84eskjk6eyRyQnbQ== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=richmond.bbb.org; dmarc=pass action=none header.from=richmond.bbb.org; dkim=pass header.d=richmond.bbb.org; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=richmond.bbb.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; b=IBp6WddL0tAEtjsUg9TLjHYmU5nmyIqGMASfttCAkZzzJQLOspzOwgifiLEXyz3lfCwmIC89UkBptAT4Z0p5sFvDUNDTtWkMoK5nPxNpjJAZenjDXSrwRfwcj0WOjcLV7VaIvVYyEs2Db+8tikyWrR2VJ2I9iNAYJkIWqwP50u9jcPYUj3FHKR44B7cxTz1VXeegS2RPjZ968HuIvKsGx6gKSgtWobvcPsYgNA3apo1BZ/Y+i3h7cGx1cdJJPED5uyyeIj8dZ/l28DoMSETkT29DVqCcKvgbVQUyM2URBFUgvksANuYRRjFcE119QOlQSsyGyl1ligENnsozK5MyYQ== DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1698346819; s=v1; d=mail-dkim-us-west-2.prod.hydra.sophos.com; h=Content-Type:Date:Subject:To:From; bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; b=jcJw6d6HDGLRjPmeM/Ye+DF43hHJMaao4by5+Jfi6F45SAggkc4D41+8pFSpNk2t Qx7LNQOyPjHyJ4K1AqYgL973657era/YNEniTZsHKZS5CIyFqjxQBu73Uk0YkrXzw3W L6oNeNo4Bp/kKYZXG8aKNFFBTUkea06TysmByIp4T+AiSUca1JkVpcciwzviaqhoc18 lP9L/2U/ORZUDEzh037Jmx0CKYP30w9Ry3fp9cYmfkGUSvY0lIu2fwa5mDodB65OWjp uoIFFVzDGfpi28usziso1gO89Ih7n0MMIj6TTrGJx0ZzuxKXZilwUIg9zKNr8ey1Gka LtUlmxEqag== Received: from BY5PR04MB6706.namprd04.prod.outlook.com (2603:10b6:a03:22e::24) by MN2PR04MB7134.namprd04.prod.outlook.com (2603:10b6:208:1e3::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.19; Thu, 26 Oct 2023 19:00:20 + Received: from BY5PR04MB6706.namprd04.prod.outlook.com ([fe80::4324:9275:a4f7:113c]) by BY5PR04MB6706.namprd04.prod.outlook.com ([fe80::4324:9275:a4f7:113c%3]) with mapi id 15.20.6933.019; Thu, 26 Oct 2023 19:00:19 + Any insight into this is greatly appreciated. We have getting bounce backs for several days now, but experienced a brief period where Google domains were able to be reached. *Mark W. Stanley, Managed Services Engineer* Richweb, Inc. / mstan...@corp.richweb.com O: 804-368-0421 X 120 richweb.com / hvens.com RAPTOR REMARK: Alert! Please be careful! This email is from an EXTERNAL sender. Be aware of impersonation and credential theft. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- next part -- An HTML attachment was scrubbed... URL: <https://list.mailop.org/private/mailop/attachments/20231026/96d95649/attachment.htm> -- Subject: Digest Footer ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop -- End of mailop Digest, Vol 39, Issue 48 ** ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] gmail deliverability issue was mailop Digest, Vol 39, Issue 48
RRUmQy20bmFrzeFdm+z8xjlDhQo=; >> >> b=IBp6WddL0tAEtjsUg9TLjHYmU5nmyIqGMASfttCAkZzzJQLOspzOwgifiLEXyz3lfCw >> mIC89UkBptAT4Z0p5sFvDUNDTtWkMoK5nPxNpjJAZenjDXSrwRfwcj0WOjcLV7VaIvVYy >> Es2Db+8tikyWrR2VJ2I9iNAYJkIWqwP50u9jcPYUj3FHKR44B7cxTz1VXeegS2RPjZ968 >> HuIvKsGx6gKSgtWobvcPsYgNA3apo1BZ/Y+i3h7cGx1cdJJPED5uyyeIj8dZ/l28DoMSE >> TkT29DVqCcKvgbVQUyM2URBFUgvksANuYRRjFcE119QOlQSsyGyl1ligENnsozK5MyYQ= >> = >> >> DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; >> t=1698346819; >> >> s=v1; d=mail-dkim-us-west-2.prod.hydra.sophos.com; >> >> h=Content-Type:Date:Subject:To:From; >> >> bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; >> >> b=jcJw6d6HDGLRjPmeM/Ye+DF43hHJMaao4by5+Jfi6F45SAggkc4D41+8pFSpNk2t >> >> Qx7LNQOyPjHyJ4K1AqYgL973657era/YNEniTZsHKZS5CIyFqjxQBu73Uk0YkrXzw3W >> >> L6oNeNo4Bp/kKYZXG8aKNFFBTUkea06TysmByIp4T+AiSUca1JkVpcciwzviaqhoc18 >> >> lP9L/2U/ORZUDEzh037Jmx0CKYP30w9Ry3fp9cYmfkGUSvY0lIu2fwa5mDodB65OWjp >> >> uoIFFVzDGfpi28usziso1gO89Ih7n0MMIj6TTrGJx0ZzuxKXZilwUIg9zKNr8ey1Gka >> >> LtUlmxEqag== >> >> Received: from BY5PR04MB6706.namprd04.prod.outlook.com >> (2603:10b6:a03:22e::24) >> >> by MN2PR04MB7134.namprd04.prod.outlook.com (2603:10b6:208:1e3::24) >> >> with Microsoft SMTP Server (version=TLS1_2, >> >> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.19; Thu, >> 26 Oct >> >> 2023 19:00:20 + >> >> Received: from BY5PR04MB6706.namprd04.prod.outlook.com >> >> ([fe80::4324:9275:a4f7:113c]) by >> BY5PR04MB6706.namprd04.prod.outlook.com >> >> ([fe80::4324:9275:a4f7:113c%3]) with mapi id 15.20.6933.019; Thu, 26 >> Oct 2023 >> >> 19:00:19 + >> >> Any insight into this is greatly appreciated. We have getting bounce >> backs for several days now, but experienced a brief period where >> Google domains were able to be reached. >> >> *Mark W. Stanley, Managed Services Engineer* >> >> Richweb, Inc. / mstan...@corp.richweb.com >> >> O: 804-368-0421 X 120 >> >> richweb.com / hvens.com >> >> >> RAPTOR REMARK: Alert! Please be careful! This email is from an EXTERNAL >> sender. Be aware of impersonation and credential theft. >> >> ___ >> mailop mailing list >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop > -- next part -- An HTML attachment was > scrubbed... > URL: > <https://list.mailop.org/private/mailop/attachments/20231026/96d95649/ > attachment.htm> > > -- > > Subject: Digest Footer > > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop > > > -- > > End of mailop Digest, Vol 39, Issue 48 > ** > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
[mailop] Contact for Cox.net
Hello All, Do we have folks from Cox.net on this distro? Or, does anyone knows how to reach out to them? -Tarun ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Contact for Cox.net
Responded off list. Sent from my iPad > On Oct 26, 2023, at 8:09 PM, Tarun Singh via mailop wrote: > > Hello All, > > Do we have folks from Cox.net on this distro? Or, does anyone knows how to > reach out to them? > > -Tarun > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] gmail deliverability issue was mailop Digest, Vol 39, Issue 48
wzhzRhQn >>> >>> for ; Thu, 26 Oct 2023 19:00:23 + >>> (UTC) >>> >>> ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; >>> cv=none; >>> >>> b=kJDl3l74RdoxT1QOA0ix5VgwvFhYhqzcUgGkZr0vhcxIyulP8EGiqJBMBBHFnEBAvzw >>> Yh6Wl3yoAV1RR5U6jCUuNWAHYG6lqhXMRycSJXMZCbJGY+k8DMwhMVOY48VMec+GZ8SzQ >>> OfjzIzoZ3eF6eLKvgc9ZVRyIP4y5EV3oOxn1SXnNP4uXC9Y6X+FLUW00R/RTiHFPlytHt >>> 4hhEktZ/5bGIMHknGHbLhcfsulVbFAfDPxCuI0lqwkpTOrlX4EjOEI09nEXghzxBhAOUm >>> LX4eFJBcRfzMlUDlriv6gyYniTKeOVNuwn7eOb6Smy4W7STqkRth8Z48BmFYVCcexKMw= >>> = >>> >>> 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-Exchang >>> e-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData- >>> 0:X-MS-Exchange-AntiSpam-MessageData-1; >>> >>> bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; >>> >>> b=j2oLsbNnA/8EGoq5tIM6WVMrAI8PefNYnRWMOmg9EoJTFxXNOViT1vcYZ1Tv80gLv/W >>> ICsLnQTBQrxDExEwVBZ636+WRwdjj9vOo0Mh6+O/mt8PDPxGLP+DfAxi0O000rB7d0hsQ >>> 6gugFt17fTwmrY7shWwVS94HM1SYFtcwpAJgeWLMJhgBrFCvWl1NzFtK7kLcmEzZL2RKC >>> Y+jy2MzFQMBJIcwM1G9pImeuxXM8evpuih/Q7GTnBivqS7Al2c4W0JnJCFoLopkJGYcTD >>> ddHPbg5PpopBWjR6UrbNXHvlCZeMsXXFQThIv9ZCcQnVgCHJZ4Ou84eskjk6eyRyQnbQ= >>> = >>> >>> ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass >>> >>> smtp.mailfrom=richmond.bbb.org; dmarc=pass action=none >>> >>> header.from=richmond.bbb.org; dkim=pass header.d=richmond.bbb.org; >>> arc=none >>> >>> DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; >>> d=richmond.bbb.org; >>> >>> s=selector1; >>> >>> h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchang >>> e-SenderADCheck; >>> >>> bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; >>> >>> b=IBp6WddL0tAEtjsUg9TLjHYmU5nmyIqGMASfttCAkZzzJQLOspzOwgifiLEXyz3lfCw >>> mIC89UkBptAT4Z0p5sFvDUNDTtWkMoK5nPxNpjJAZenjDXSrwRfwcj0WOjcLV7VaIvVYy >>> Es2Db+8tikyWrR2VJ2I9iNAYJkIWqwP50u9jcPYUj3FHKR44B7cxTz1VXeegS2RPjZ968 >>> HuIvKsGx6gKSgtWobvcPsYgNA3apo1BZ/Y+i3h7cGx1cdJJPED5uyyeIj8dZ/l28DoMSE >>> TkT29DVqCcKvgbVQUyM2URBFUgvksANuYRRjFcE119QOlQSsyGyl1ligENnsozK5MyYQ= >>> = >>> >>> DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; >>> t=1698346819; >>> >>> s=v1; d=mail-dkim-us-west-2.prod.hydra.sophos.com; >>> >>> h=Content-Type:Date:Subject:To:From; >>> >>> bh=U1XPevLPW3kgepb4RRUmQy20bmFrzeFdm+z8xjlDhQo=; >>> >>> b=jcJw6d6HDGLRjPmeM/Ye+DF43hHJMaao4by5+Jfi6F45SAggkc4D41+8pFSpNk2t >>> >>> Qx7LNQOyPjHyJ4K1AqYgL973657era/YNEniTZsHKZS5CIyFqjxQBu73Uk0YkrXzw3W >>> >>> L6oNeNo4Bp/kKYZXG8aKNFFBTUkea06TysmByIp4T+AiSUca1JkVpcciwzviaqhoc18 >>> >>> lP9L/2U/ORZUDEzh037Jmx0CKYP30w9Ry3fp9cYmfkGUSvY0lIu2fwa5mDodB65OWjp >>> >>> uoIFFVzDGfpi28usziso1gO89Ih7n0MMIj6TTrGJx0ZzuxKXZilwUIg9zKNr8ey1Gka >>> >>> LtUlmxEqag== >>> >>> Received: from BY5PR04MB6706.namprd04.prod.outlook.com >>> (2603:10b6:a03:22e::24) >>> >>> by MN2PR04MB7134.namprd04.prod.outlook.com (2603:10b6:208:1e3::24) >>> >>> with Microsoft SMTP Server (version=TLS1_2, >>> >>> cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6933.19; Thu, >>> 26 Oct >>> >>> 2023 19:00:20 + >>> >>> Received: from BY5PR04MB6706.namprd04.prod.outlook.com >>> >>> ([fe80::4324:9275:a4f7:113c]) by >>> BY5PR04MB6706.namprd04.prod.outlook.com >>> >>> ([fe80::4324:9275:a4f7:113c%3]) with mapi id 15.20.6933.019; Thu, 26 >>> Oct 2023 >>> >>> 19:00:19 + >>> >>> Any insight into this is greatly appreciated. We have getting bounce >>> backs for several days now, but experienced a brief period where >>> Google domains were able to be reached. >>> >>> *Mark W. Stanley, Managed Services Engineer* >>> >>> Richweb, Inc. / mstan...@corp.richweb.com >>> >>> O: 804-368-0421 X 120 >>> >>> richweb.com / hvens.com >>> >>> >>> RAPTOR REMARK: Alert! Please be careful! This email is from an EXTERNAL >>> sender. Be aware of impersonation and credential theft. >>> >>> ___ >>> mailop mailing list >>> mailop@mailop.org >>> https://list.mailop.org/listinfo/mailop >> -- next part -- An HTML attachment was >> scrubbed... >> URL: >> <https://list.mailop.org/private/mailop/attachments/20231026/96d95649/ >> attachment.htm> >> >> -- >> >> Subject: Digest Footer >> >> ___ >> mailop mailing list >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop >> >> >> -- >> >> End of mailop Digest, Vol 39, Issue 48 >> ** >> ___ >> mailop mailing list >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop > ___ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
