I created a new email server and was following the instructions on
http://www.qmailtoaster.com/migrate.html
My issue that I am having is that Dovecot is not my server and doesn't seem
to be working after the migration. Webmail works, but none of my clients
will login to imap.
Help.
When I updated using the command
- yum --enablerepo=qmt-devel update
It updated qmailAdmin ... and it looks like this !
Is that intended ?
[image: image.png]
David Bray
0418 745334
2 ∞ & <
I think my issue was just that, it seems to have gone away since I updated
to latest version
On Thu, 30 Apr 2020 at 2:19 am, Eric Broch wrote:
> Has anyone experienced timeouts on incoming connections from outlook.com?
>
>
> -
I just tested and all normal on my side.
Remo
> On Apr 29, 2020, at 09:18, Eric Broch wrote:
>
> Has anyone experienced timeouts on incoming connections from outlook.com?
>
>
> -
> To unsubscribe, e-mail:
Has anyone experienced timeouts on incoming connections from outlook.com?
-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
I meant "spamdyke" rather than "spamassassin".
-Andy
On 4/29/2020 7:10 AM, Andrew Swartz wrote:
Letsencrypt certificates are fine for email servers, I've been using
them for several years.
I initially had this same problem.
Spamassassin/qmail starts a new instance with each new SMTP
Letsencrypt certificates are fine for email servers, I've been using
them for several years.
I initially had this same problem.
Spamassassin/qmail starts a new instance with each new SMTP connection,
so when a new cert is saved it starts getting used on the next SMTP
connection.
However,
Hmmm
Only difference between those versions is the spam throttle patch.
On 4/29/2020 5:31 AM, David Bray wrote:
Just an update on this
all seems to have resolved itself now
I'm not sure exactly what the differential was
1. I ran the update - /yum --enablerepo=qmt-devel update/
*
You need to create the right cert for the toaster from the
renewed cert from letsencrypt.
Something like this:
cat
/etc/letsencrypt/live/mail.yourdomain.com/{cert,chain,fullchain,privkey}.pem
> /var/qmail/control/servercert.pem
Just an update on this
all seems to have resolved itself now
I'm not sure exactly what the differential was
1. I ran the update - *yum --enablerepo=qmt-devel update*
- before : qmail-1.03-3.1.1.qt.el7.x86_64
- after : qmail-1.03-3.2.qt.el7.x86_64
I did some other things, but
I make up a composite certificate and
include lets-encrypt-x3-cross-signed.pem.txt
https://letsencrypt.org/certificates/
I'm not sure if I still need to, but I must have at some stage
David Bray
0418 745334
2 ∞ & <
On Wed, 29 Apr 2020 at 19:38, ChandranManikandan wrote:
> Hi Friends,
>
> It
Hi,
Are the dovecot and qmail services restarted?
Regarts,
Peter
Solo schreef op 29 april 2020 11:42:10 CEST:
>
>Hi.
>
>I think Letsencrypt are for websites/servers and not for the specifik
>email which require another type of certificate than Letsencrypt issues
>
>- usually that is set up
Hi.
I think Letsencrypt are for websites/servers and not for the specifik
email which require another type of certificate than Letsencrypt issues
- usually that is set up when qmail is installed (openssl) and placed
/var/qmail/
/Finn vB
Den 29-04-2020 kl. 10:52 skrev
Hi Friends,
It was working well before after getting the renewal date only the issue is
happened.
Anyone having the same issue?
Appreciate your help.
On Wed, Apr 29, 2020 at 4:52 PM ChandranManikandan
wrote:
> Hi Remo,
>
> FYI
> ssl_cert = ssl_key = # the following will likely be the default
Hi Remo,
FYI
ssl_cert = wrote:
> You need to check the /etc/dovecot/toaster.conf file that’s where the cert
> for outlook and thunder lives.
>
> Remo
>
> On Apr 28, 2020, at 20:38, ChandranManikandan wrote:
>
> Hi Friends,
>
> certbot renew command showing below message
> Saving debug log to
15 matches
Mail list logo
