• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Mailman and qmail -- bounces go to unrelated address and domain

DeanC@

Basic Pleskian
This is on a CentOS / Plesk 8.6 server but the problem has been occurring with earlier versions of Plesk.

Mailman is not properly deleting bouncing subscribers. I've tried numerous bounce settings on numerous lists on various domains.

That would be okay, I suppose, since the folks who run the lists do periodic "roll calls" to make sure subscribers are active.

However, the returned mail for Mailman lists (various domains) for some reason get sent to an address on a totally different domain that doesn't even use Mailman.

On that domain, the client uses ListMessenger (but has also used Dada, phplist, etc. -- same problem for all). Also, I've set the outgoing mail the for these programs to use php mail, smtp, and so on. Same thing happens no matter how the mail is sent.

Each time she sends out mail from ListMessenger, she gets a multitude of bounces for addresses on other domains' Mailman lists (and not subscribed to her list). And ... since the undeliverable Mailman messages sit in the mail queue for up to seven days, she gets scores upon scores of these bounce notifications -- one for every message sitting in the queue.

Other domains also use ListMessenger, Dada, phplist, etc. But they don't get these incorrect notices. Just this one domain.

Below is a sample of what I'm talking about. (I've changed the email addresses to protect the subscribers and client's confidentiality). Only the [email protected] (me) in the original message headers is subscribed to the list, and I received the message. All of the other addresses prior to the headers are not subscribed to her list -- never have been -- they are subscribed to various Mailman lists on other domains.

Begin forwarded message:

From: [email protected]
Date: February 15, 2009 7:01:36 PM PST
To: [email protected]
Subject: failure notice

Hi. This is the qmail-send program at server1.montereybusiness.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<[email protected]>:
216.39.53.1 failed after I sent the message.
Remote host said: 554 delivery error: dd Sorry your message to [email protected] cannot be delivered. This account has been disabled or discontinued [#102]. - mta108.mail.re4.yahoo.com

<[email protected]>:
209.85.201.114 does not like recipient.
Remote host said: 550-5.1.1 The email account that you tried to reach does not exist. Please
550-5.1.1 try double-checking the recipient's email address for typos
550-5.1.1 or unnecessary spaces. Learn more at
550 5.1.1 http://mail.google.com/support/bin/answer.py?answer=6596 24si19618598wff.22
Giving up on 209.85.201.114.

<[email protected]>:
65.55.37.72 does not like recipient.
Remote host said: 550 Requested action not taken: mailbox unavailable
Giving up on 65.55.37.72.

<[email protected]>:
66.196.97.250 failed after I sent the message.
Remote host said: 554 delivery error: dd Sorry your message to [email protected] cannot be delivered. This account has been disabled or discontinued [#102]. - mta195.mail.re3.yahoo.com

<[email protected]>:
65.55.37.72 does not like recipient.
Remote host said: 550 Requested action not taken: mailbox unavailable
Giving up on 65.55.37.72.

<[email protected]>:
65.54.244.168 does not like recipient.
Remote host said: 550 Requested action not taken: mailbox unavailable
Giving up on 65.54.244.168.

<[email protected]>:
65.55.37.88 does not like recipient.
Remote host said: 550 Requested action not taken: mailbox unavailable
Giving up on 65.55.37.88.

<[email protected]>:
216.39.53.1 failed after I sent the message.
Remote host said: 554 delivery error: dd This user doesn't have a yahoo.com account ([email protected]) [0] - mta404.mail.re4.yahoo.com

--- Below this line is a copy of the message.

Return-Path: <[email protected]>
Received: (qmail 22266 invoked from network); 15 Feb 2009 21:01:36 -0600
Received: from her.isp.com (204.212.38.2)
by server1.montereybusiness.net with SMTP; 15 Feb 2009 21:01:36 -0600
Received: from [10.0.1.2] (someone.herisp.com [207.181.14.10])
by her.isp.com (8.14.3/8.9.3) with ESMTP id n1G30gwS067736
for <[email protected]>; Sun, 15 Feb 2009 19:01:48 -0800 (PST)
Message-Id: <[email protected]>
From: [email protected]
To: Subscriber at ComPlanners <[email protected]>
Content-Type: multipart/alternative; boundary=Apple-Mail-213-895553499
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Fwd: failure notice
Date: Sun, 15 Feb 2009 19:01:47 -0800
References: <[email protected]>
X-Mailer: Apple Mail (2.930.3)

--Apple-Mail-213-895553499
Content-Type: text/plain;
charset=US-ASCII;
format=flowed;
delsp=yes
Content-Transfer-Encoding: 7bit

[body of message here -- deleted]

Any ideas?
 
Okay, alternatively, can anyone tell me where to file a bug report?

I see scores of places to give Parallels money to fix their own problems, but nowhere to file a bug report.
 
Great job, Parallels Team! Great job. Use that tough love. It's probably something so simple, you're laughing, thinking, oh, if this guy had a brain, he'd of figured it out himself by now. Well, I haven't. But I understand. Now that you own nearly all control panels, there's no incentive to help anyone. Just hang out and watch that money roll in.
 
Back
Top