A list owner account, which is also a recipient on their own and other lists, has been marked “unconfirmed” twice since May and our upgrade to v3.3.1, but the history on the owner/recipient account shows only bounces was to a different address (identical info on each below except date and subject):
Action: failed
Final-Recipient: rfc822;real_bounce@address.com
Status: 5.0.0
Remote-MTA: dns; mx10.positive-internet.com
Diagnostic-Code: smtp; 550-5.1.1 <real_bounce@address.com>: Recipient address rejected:
550 User unknown in virtual mailbox table
--1494887529-eximdsn-1976397181
Content-type: message/rfc822
Return-path: <bounces@ourgroup.org>
Received: from ourgroup by server.myserver.com with local (Exim 4.89)
(envelope-from <bounces@ourgroup.org>)
id 1dAOX8-0000py-NS
for real_bounce@address.com; Mon, 15 May 2017 18:32:06 -0400
To: real_bounce@address.com
Subject: **THIS FRIDAY--FUN FRIDAY HANGOUT**
X-PHP-Originating-Script: 508:class.phpmailer.php
Date: Mon, 15 May 2017 22:32:06 +0000
From: "owner_recipient@ourgroup.org" <owner_recipient@ourgroup.org>
Message-ID: <42ab8de686a4c8424f7f41dad03a427d@ourgroup.org>
X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
X-phpList-version: 3.3.1
Is this a bounce rule issue on my part? Where should I look to correct it?
Thank you for any assistance you can provide.
Peace,
Jo
It’s not clear from your description what’s going on.
You are sending from owner_recipient, and sending to real_bounce, and the bounce message says that the real_bounce address does not exist.
Yes. But, owner_recipient is the address being marked “unconfirmed” by bounce processing rather than real_bounce.
@jocraddock You didn’t show enough of the email headers in your first post. phplist uses the X-ListMember header to identify the subscriber.
You mentioned bounce rules. Is the unconfirmation being done by the consecutive bounces processing or by a bounce rule?
Also, so far as you can tell are other bounces being matched to the correct subscriber?
My apologies for not providing all needed; difficult to maintain privacy and know that I’m sending sufficient info. This is the first “issue” I’ve had with phpList. There follows the entire “header” box as shown in phpList.
The action to mark unconfirmed is a bounce rule: (User unknown|Unknown user|Unknown address|No such recipient|No such user|The email account that you tried to reach is disabled|Recipient not found|Recipient unknown|Invalid recipient|Address unknown|Recipient address rejected)
Other bounces are being processed correctly.
The only difference that is obvious to me with this situation issue is that the sender (the address being incorrectly changed to “unconfirmed”) is a list owner and a subscriber. The only two times the owner_recipient address has been incorrectly changed both resulted when a campaign was initiated by me (admin), putting the owner_recipient address in the from line (as requested/needed for situation) so that the campaign could be sent to two lists, one owned by admin and one owned by owner_recipient.
Return-Path: <>
Delivered-To: bounces@ourgroup.org
Received: from server.myserver.com
by server.myserver.com (Dovecot) with LMTP id Ec8XNpl4Wll2FQAA6S2kpg
for <bounces@ourgroup.org>; Mon, 03 Jul 2017 13:02:17 -0400
Return-path: <>
Envelope-to: bounces@ourgroup.org
Delivery-date: Mon, 03 Jul 2017 13:02:17 -0400
Received: from mailnull by server.myserver.com with local (Exim 4.89)
id 1dS4jp-0004ES-RP
for bounces@ourgroup.org; Mon, 03 Jul 2017 13:02:17 -0400
X-Failed-Recipients: real_bounce@address.com
Auto-Submitted: auto-replied
From: Mail Delivery System <Mailer-Daemon@server.myserver.com>
To: bounces@ourgroup.org
Content-Type: multipart/report; report-type=delivery-status; boundary=1499101337-eximdsn-523866005
MIME-Version: 1.0
Subject: Mail delivery failed: returning message to sender
Message-Id: <E1dS4jp-0004ES-RP@server.myserver.com>
Date: Mon, 03 Jul 2017 13:02:17 -0400
Thank you for your attention.
Peace,
Jo
@jocraddock In your first post, you didn’t appear to show all of the headers of the original email - the X-ListMember header is the one used to identify the subscriber. Can you confirm that the bounce does contain that?
You are right; I’m using a different interface (the “new” one) at one office, but not at the other. I copied the info from the body section.
My message of earlier today included the “entire header” section of the phpList interface regarding the bounce. I’m attaching an image. The circled area contains the address that bounced (it is an invalid address; I’ve since removed it from our list), but it was the address in the “from” line of the email that was marked as “unconfirmed.” I see that address is nowhere in the header section shown.
Thanks, and
Peace,
Jo
@jocraddock You are still misunderstanding. I will try once more only. In your first post you showed headers of the orginal email that bounced. The headers stop with “X-phpList-version”. Is that literally all that are present, as there should be others specifically X-ListMember.
Yes, I can confirm that.
…
Message-ID: 42ab8de686a4c8424f7f41dad03a427d@ourgroup.org
X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
X-phpList-version: 3.3.1
X-MessageID: 251
X-ListMember: real_bounce@address.com
Precedence: bulk
Bounces-To: bounces@ourgroup.org
…
@jocraddock phplist uses the X-ListMember header to find the subscriber. It appears that it cannot find that header. Then it tries to find anything that looks like an email address and is also a subscriber and uses that for the subscriber.
Possibly there is something odd about the structure of that particular bounce which is causing this.
