On Fri, 2022-01-07 at 23:50 -0500, Dave McGuire wrote:

On 1/7/22 11:46 PM, Ken Wright wrote:

...

When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream returned no data”.  At least to me, that's not particularly informative.  Is it any more informative to anyone else?

   The last time I hit that, I'm pretty sure it was because I was going to port 80 instead of port 443 to reach Roundcube.

I'm using port 143 for receiving and 587 for sending; I didn't think 443 was for email. Am I mistaken? (Not at all unlikely!)

Ken

On Fri, 2022-01-07 at 23:59 -0500, Dave McGuire wrote:

On 1/7/22 11:58 PM, Ken Wright wrote:

...

...

...

When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream returned no data”.  At least to me, that's not particularly informative.  Is it any more informative to anyone else?

    The last time I hit that, I'm pretty sure it was because I was going to port 80 instead of port 443 to reach Roundcube.

I'm using port 143 for receiving and 587 for sending; I didn't think 443 was for email.  Am I mistaken?  (Not at all unlikely!)

   Nono, for your web browser's connection to Roundcube.  I could be barking up the wrong tree here, but I'm pretty sure that's the error I hit.

Thanks for the clarification. I just tried Roundcube again, and got the error "Connection to storage server failed." I also checked the nginx script for Roundcube and commented out the references to port 80, then restarted nginx. Same error. So I tend to think it's a server issue, not a client issue. Does that make any sense?

Ken

On 1/8/22 12:28 AM, Ken Wright wrote:

...

...

...

...

When I try to log in to my mail server (ubuntu 20.04, Postfix 3.4.13, Dovecot 2.3.7.2) I get a response saying "Source stream returned no data”.  At least to me, that's not particularly informative.  Is it any more informative to anyone else?

    The last time I hit that, I'm pretty sure it was because I was going to port 80 instead of port 443 to reach Roundcube.

I'm using port 143 for receiving and 587 for sending; I didn't think 443 was for email.  Am I mistaken?  (Not at all unlikely!)

   Nono, for your web browser's connection to Roundcube.  I could be barking up the wrong tree here, but I'm pretty sure that's the error I hit.

Thanks for the clarification. I just tried Roundcube again, and got the error "Connection to storage server failed." I also checked the nginx script for Roundcube and commented out the references to port 80, then restarted nginx. Same error. So I tend to think it's a server issue, not a client issue. Does that make any sense?

It makes sense, but that's a different error than the one you got before. This new error looks like a Roundcube configuration problem, having to do with either its connection to Dovecot or possibly a back-end database server. (MySQL?)

         -Dave

-- Dave McGuire, AK4HZ New Kensington, PA

On 1/8/22 11:27 AM, Ken Wright wrote:

MariaDB. Now it's time for me to clarify. The "source stream returned no data" error is in Evolution; the "connection to storage server failed" is in Roundcube. So I'm seeing similar errors in two different email clients trying to get to the same server.

I know there are any number of reasons for a failed connection to Dovecot, but I just don't have the experience to figure this one out.

Understood. There's enough expertise here to get you going.

First, ignore the superficial similarity of the errors and diagnose/address them individually. Get one mail client working via IMAP.

For Evolution's "source stream returned no data", ignore my previous suggestion about web browser SSL vs. non-SSL, as that's not relevant to Evolution. The error looked very familiar to me at first; it probably came from the same library as whatever I was working with when I hit that. (probably libssl) Go into the mail account configuration in Evolution and check the settings there. I don't use Evolution so I can't direct you more specifically, but what to pay attention to here is the connection settings and port numbers. I'm guessing (hazardously) that the port number or SSL method is incorrect. Make sure to distinguish between SSL and TLS (STARTTLS).

Concentrate on getting that working first; don't get distracted from it.

After that's working, then move on to Roundcube. Look in Roundcube's config.inc.php file. Where that file is located is system-dependend; mine is in /opt/local/etc/roundcube, which is specific to SmartOS. Parameter "$config['db_dsnw']" is the DSN for your database connection. This is the format of that configuration variable:

$config['db_dsnw'] = 'mysql://USERNAME:PASSWORD@SERVER/DATABASE';

You're running MariaDB, which is a fork of MySQL, so I'm guessing that Roundcube doesn't differentiate between the two, so the "mysql" above is probably correct. Check the docs if that fails. Obviously, the words in uppercase must be correct for your installation. "SERVER" might be "localhost" for you. (it isn't for me)

One quick thing to check: Did you issue a "flush privileges" command to MariaDB after creating the account for Roundcube to use?

See how far that gets you and report back.

         -Dave

-- Dave McGuire, AK4HZ New Kensington, PA

On 1/8/22 3:04 PM, William Edwards wrote:

...

  After that's working, then move on to Roundcube.  Look in Roundcube's config.inc.php file.  Where that file is located is system-dependend; mine is in /opt/local/etc/roundcube, which is specific to SmartOS. Parameter "$config['db_dsnw']" is the DSN for your database connection. This is the format of that configuration variable:

$config['db_dsnw'] = 'mysql://USERNAME:PASSWORD@SERVER/DATABASE';

  You're running MariaDB, which is a fork of MySQL, so I'm guessing that Roundcube doesn't differentiate between the two, so the "mysql" above is probably correct.  Check the docs if that fails.  Obviously, the words in uppercase must be correct for your installation. "SERVER" might be "localhost" for you. (it isn't for me)

AFAIK, the error "Connection to storage server failed" only occurs when Roundcube can't connect to IMAP (in this case, Dovecot). If there's a database issue, Roudcube should show the message "Unable to connect to the database!".

Rummaging through the source code, I see that you are indeed correct. Thank you for that clarification.

...

  One quick thing to check: Did you issue a "flush privileges" command to MariaDB after creating the account for Roundcube to use?

FWIW, that hasn't been needed for quite some time when not directly manipulating mysql.users (i.e. using CREATE USER).

I had heard that, but not knowing:

• what release of MySQL obviated that long-standing requirement
• when MariaDB forked from MySQL
• what release of anything the OP is running
• how the OP chose to manipulate the grant tables

...I chose to make the recommendation for the sake of safety, as it's cheap to try.

Now maybe we can get back to the OP's actual problems, which nobody else seems to be interested in today.

       -Dave

-- Dave McGuire, AK4HZ New Kensington, PA