Re: POP3 connection failed - server now TLS 1.2 ?

From: "Justin John justin@PROTECTED [Dada Mail Developers]" <dadadev@PROTECTED>
Subject: Re: POP3 connection failed - server now TLS 1.2 ?
In-Reply-To: (no subject)
Date: June 21st 2021
Hmm - in the SMTP connection/mail test, I ping the server before trying to connect to it to send a message - we could do something similar for POP3 and IMAP connections. I’ll add that as a feature request: 


Justin J: Lead Dadaist
email:    justin@PROTECTED
twitter:  @dadamail

Dada Mail Announcements: 

On Jun 18, 2021, at 11:30 AM, Chris Holt chris.holt@PROTECTED [Dada Mail Developers] <dadadev@PROTECTED> wrote:


From: chris.holt@PROTECTED

Hello again

A short epilogue in case something similar happens to others. I went ahead and added setting the SSL_version to explicity include TLS 1.2 but it made no difference. I tried setting NET_POP3 => 1 in the config CPAN_DEBUG_SETTINGS but the debug messages only started turning up in the error log after the problem had been cured. What did help was trying to telnet to the mail server from the 'jailed shell' I have access to on the server where Dada Mail is installed. This showed that, while the port to the SMTP server was open, both the SSL and the unencrypted ports to the POP3 server were blocked. As they were blocked, there was no communication from them at all - hence the 'Content failed to load' when testing from within Bridge and no POP3 debug messages.

As soon as port 995 was reopened, Dada Mail started working again. I have no idea why it had become blocked. Just one of the joys of shared hosting, I suppose.

Kind regards


On 12/06/2021 15:16, Chris Holt wrote:

Hello Justin and developers

My list has been running reliably since November 2019, with an update to 11.11.2 in September. However, the list has not sent out any messages since 21st May (apart from a message to me on 25th May saying a non-subscriber had tried to post).

The shared host error_log file has messages every five minutes that include "AH01220: Timeout waiting for output from CGI script/home/very_long_path/cgi-bin/dada/mail.cgi" and "Script timed out before returning headers: mail.cgi". My attention was drawn to these by the host support team, who were responding to our webmaster's queries about why our website, on the same host, was slow and giving 504 timeout errors.

When I tried to run the Dada Mail scheduled job from the command line(following the online documentation), mail.cgi took two or three minutes to respond, which explains the timeouts.  I have attached a redacted version of the verbose response eventually obtained. Much of it looks sensible. It also shows that the daily digests that are sent to me have not been sent since 21st May. The cause is shown as "no new messages" but several have been sent to the list in the interim.

The clue seems to be the "* Connection to '' wasn't successful", "* POP3 connection failed!" messages for the Bridge plugin and for the bounce handler.

From the administration control panel, Bridge page, I pressed the on screen button to test the POP3 connection. After a pause, there was a white box containing "This content failed to load". The adjacent manual check button had the same response.

I can log into the POP3 account via the shared host's webmail (using the usual username and password). I found seven email messages sent to the list: three from me on 29th May and 1st and 4th June, three from other subscribers on 10th June and one I sent as a test yesterday.Their presence is consistent with Dada Mail being unable to retrieve them.

Also, in .dada_files/.tmp, there is an mbox text file that seems to have every message since 2019 but finishes with the email received from the non-subscriber on 25th May. I've renamed it to see if it is re-created when the list starts working again.

Wondering why the POP3 access might have stopped, I have been searching through the shared host's support forum. In November 2020,users with Thunderbird were complaining that their client was now using TLS 1.2 by default while, the host's mail service, was still on TLS 1. There has since been an undated announcement that has changed to TLS 1.2 and that clients unable to use TLS 1.2 may have problems.

Since 2019, I have been using and IO:Socket:SSL v. 2.066.Should I try setting SSL_version to'SSLv23:!SSLv2:!SSLv3:!TLSv1_1:!TLSv1_2' in, as the metacpan documentation suggests?

Or am I barking up the wrong tree entirely and should I be looking for why the website and possibly the SQL databases are running slowly and causing timeouts, including for POP3 access?

The semaphore messages that I keep logged as a visible heartbeat for the list, mentioned in my November 2019 dadadev emails, changed after 23:40 26th May to "Couldn't create an exclusive semaphore file at line 229, line 1" without time stamps.

What could have happened near midnight on 26th May, to stop the list retrieving and sending out emails?

Kind regards



Dada Mail Developers

Post to: Dada Mail Developers ( dadadev@PROTECTED ) 
Manage Your Subscription 

  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)
  • Start a new thread, email:

This mailing list is to discuss the nerdy programming development of Dada Mail -

If you are just looking for support Dada Mail, consult the message boards at:

To post to this list, send a message to:

All subscribers of this list may post to the list itself.

Some on topic... topics include:

  • Positive Crits on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own internal needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.

Please, please please familiarize yourself with the documentation at:

Since no one wants to answer the same question twice.

Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.

NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.

Dada Mail Project