Hi Dan, Thank you for your explanation.
What would you advise. Do i need to purchase the certificate or create own for our domain. If need to purchase which provider is best support for me. I am concern about need to access the email in outlook 2016 only. Because it is not working outlook 2016 except all other email client. On Fri, Aug 17, 2018 at 1:34 AM, Andrew Swartz <awswa...@acsalaska.net> wrote: > Dan, > > I too noticed your mention of selinux. Do you have qmail running with > selinux? If so, I'd love to know how. I have stumbled across some > selinux contexts for qmail components, but I've never seen any clear > explanation or script for configuration. > > -Andy > > > On 8/16/2018 7:42 AM, Remo Mattei wrote: > > Not sure about this but qmail does not have selinux enabled. So your > > steps there may need to be reviewed. > > > > > > > >> On Aug 16, 2018, at 08:21, Dan McAllister - QMT DNS <q...@it4soho.com > >> <mailto:q...@it4soho.com>> wrote: > >> > >> So let’s explain the steps – some of which you may have already done: > >> a. ## 1. Generate an RSA key with keylength of 2K (2048) – this is > >> used to PROVE authorship > >> b. ## The output file is x.key > >> c. openssl genrsa -out x.key 2048 > >> d. > >> e. ## 2. Generate a Certificate Request – needed to create a > >> certificate later > >> f. ## The output file is x.csr > >> g. openssl req -new -key x.key -out x.csr > >> h. > >> i. ## 3. Create a self-signed certificate, using the KEY and REQUEST > >> you created above (a 10-year certificate in this case) > >> j. ## The output file is x.crt > >> k. openssl x509 -req -days 3650 -in x.csr -signkey x.key -out x.crt > >> l. > >> m. ## So now you have 3 files: the REQUEST file COULD have been sent > >> to a signing authority for them to create a CERTIFICATE for you that > >> is signed by them – thus, making it “valid” for anyone else who trusts > >> that signing authority – but in this case, you used it to create your > >> OWN (self-signed) certificate… no one will trust it, unless they trust > >> EVERYONE. > >> n. > >> o. ## 4. Next, you create the PEM file, which stores the KEY and the > >> CERTIFICATE in a single file > >> p. ## In the general case, this isn’t a good idea, but it’ll suffice > >> in this case > >> q. cat x.crt x.key > servercert.pem > >> r. > >> s. ## 5. Next you make the combined file readable by all (be careful > >> with ACLs and SE-Linux) > >> t. chmod 644 servercert.pem > >> u. > >> v. ## 6. Then you make the certificate (and key – combined file) > >> owned by root (the only user who can change it) and belong to the > >> qmail group – which doesn’t REALLY matter > >> w. chown root:qmail servercert.pem > >> x. > >> y. ## 7. Finally you copy (with permissions) the combined file into > >> your Qmail config folder > >> z. cp -p servercert.pem /var/qmail/control > >> > >> If you were to get a REAL certificate, you would replace Step 3 above > >> with the submission of your CSR file, along with the FQDNs you are > >> proposing to certify, to the chosen agency. THEY will return to you a > >> CRT file, along with an INTERMEDIATE certificate file. (DO NOT EVER > >> SEND THEM YOUR KEY FILE!) > >> Then, in Step 4, you would ADD their intermediate certificate to the > >> PEM file (just stick the filename in between your key filename and > >> your certificate filename). > >> > >> Once you think you have it, test it with the tools at > >> https://www.sslshopper.com/ssl-checker.html > >> To check your mail server, specify the mail server with the SSL > >> enabled port number, e.g.: mail.x.com:465 > >> <http://mail.x.com:465/> or mail.x.com:993 > >> <http://mail.x.com:993/> for your imaps server > >> > >> One last comment – your instructions show you doing this as root – > >> only steps 6 & 7 require elevation: 6 to chown to root, and 7 to write > >> into the Qmail control folder. YOU REALLY SHOULDN’T PLAY IN YOUR > >> SYSTEMS (or work, if you must) AS THE ROOT USER! > >> > >> I hope this helps…. > >> > >> Dan > >> > >> > >> > >> > >> *From:* ChandranManikandan <kand...@gmail.com <mailto:kand...@gmail.com > >> > >> *Sent:* Thursday, August 16, 2018 3:54 AM > >> *To:* qmailtoaster-list@qmailtoaster.com > >> <mailto:qmailtoaster-list@qmailtoaster.com> > >> *Subject:* Re: [qmailtoaster] Asking the password frequently > >> > >> Hi Eric, > >> > >> I have one doubt regard the create certificate. > >> > >> I have gone through this link https://www.qmailtoaster.org/ssl.html > >> > >> It was showing the six steps. > >> Do i need to complete all the six steps or just use only the below > >> second steps only for my server COS 6 & 7 32 and 64 bit. > >> Please help me. > >> > >> > >> 1. Application: Self-Signed Certificate > >> > >> a. # openssl genrsa -out x.key 2048 > >> b. # openssl req -new -key x.key -out x.csr > >> c. # openssl x509 -req -days 3650 -in x.csr -signkey x.key -out x.crt > >> d. # cat x.crt x.key > servercert.pem > >> e. # chmod 644 servercert.pem > >> f. # chown root:qmail servercert.pem > >> g. # cp -p servercert.pem /var/qmail/control > >> > >> > >> > >> > >> On Tue, Aug 14, 2018 at 11:03 AM, ChandranManikandan > >> <kand...@gmail.com <mailto:kand...@gmail.com>> wrote: > >>> Hi Eric, > >>> > >>> Thank you, Let me try it and update here. > >>> > >>> On Tue, Aug 14, 2018 at 10:54 AM, Eric Broch <ebr...@whitehorsetc.com > >>> <mailto:ebr...@whitehorsetc.com>> wrote: > >>>> I've installed certificates on both CentOS 6 & 7 using GoDaddy and > >>>> LetsEncrypt. > >>>> > >>>> On 8/12/2018 9:12 PM, ChandranManikandan wrote: > >>>>> Hi Eric, > >>>>> > >>>>> I think i already installed the certificate which was 512 and got > >>>>> expired on the server. > >>>>> > >>>>> Can i try to install the certificate which you advised and sent > >>>>> link earlier. > >>>>> > >>>>> I just want to make sure, the problem will not come after install > >>>>> this in the production server. > >>>>> Have you tried in COS6 32 and 64 bit server. > >>>>> Because am running both the version in different server. > >>>>> > >>>>> > >>>>> > >>>>> On Fri, Aug 10, 2018 at 2:03 PM, Eric Broch > >>>>> <ebr...@whitehorsetc.com <mailto:ebr...@whitehorsetc.com>> wrote: > >>>>>> Office 365 my require a signed certificate from a Certificate > >>>>>> Authority. > >>>>>> > >>>>>> On 8/9/2018 10:23 PM, ChandranManikandan wrote: > >>>>>>> Hi Eric, > >>>>>>> > >>>>>>> I think the certificate was expired and the date is in > >>>>>>> server -rw-r--r-- 1 root qmail 1.7K Mar 22 2013 servercert.pem > >>>>>>> > >>>>>>> I have checked the certificate validity in outlook while opening. > >>>>>>> > >>>>>>> FYR. PFA > >>>>>>> > >>>>>>> On Wed, Aug 8, 2018 at 9:58 PM, Eric Broch > >>>>>>> <ebr...@whitehorsetc.com <mailto:ebr...@whitehorsetc.com>> wrote: > >>>>>>>> Is the current cert self signed or is it expired? > >>>>>>>> > >>>>>>>> On 8/7/2018 10:30 PM, ChandranManikandan wrote: > >>>>>>>>> Hi Friends, > >>>>>>>>> > >>>>>>>>> Thank you for your support. > >>>>>>>>> > >>>>>>>>> I have solved the Thunderbird issue in Ubuntu 18 version. > >>>>>>>>> > >>>>>>>>> Just open the folder of imap and removed cert8.db and > >>>>>>>>> certoverride.txt then reconfigured the email. > >>>>>>>>> It was successfully configured with accept the confirm security > >>>>>>>>> exception message. > >>>>>>>>> > >>>>>>>>> But am unable to configure in outlook 2016. > >>>>>>>>> I have created new profile in outlook and tried also, the same > >>>>>>>>> issue is happening. > >>>>>>>>> > >>>>>>>>> Outlook 2010 is working fine. > >>>>>>>>> > >>>>>>>>> Hi Eric, > >>>>>>>>> > >>>>>>>>> Do i need to reinstall the ssl certificate on COS6 32 bit as > >>>>>>>>> you given the url. > >>>>>>>>> Can i follow the instruction to do that. > >>>>>>>>> Because this is production server that's what worried. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Tue, Aug 7, 2018 at 2:18 AM, Rodrigo Cortes > >>>>>>>>> <rap...@gmail.com <mailto:rap...@gmail.com>> wrote: > >>>>>>>>>> Work fine in all modern devices and browser and a simple > >>>>>>>>>> script can do the work for renew :) > >>>>>>>>>> > >>>>>>>>>> El El lun, 6 de ago. de 2018 a las 14:16, Remo Mattei > >>>>>>>>>> <r...@mattei.org <mailto:r...@mattei.org>> escribió: > >>>>>>>>>>> The only thing I do not like about let’s encrypt is that > >>>>>>>>>>> every 90 days my iPhone, was complaining about the cert.. > >>>>>>>>>>> etc.. so for 12 dollars 2years.. it’s all worth it. > >>>>>>>>>>> > >>>>>>>>>>> Remo > >>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>>>>> On Aug 6, 2018, at 11:09, Rodrigo Cortes <rap...@gmail.com > >>>>>>>>>>>> <mailto:rap...@gmail.com>> wrote: > >>>>>>>>>>>> > >>>>>>>>>>>> Hi! > >>>>>>>>>>>> > >>>>>>>>>>>> Use letenscrypt is free :) > >>>>>>>>>>>> > >>>>>>>>>>>> And work fine > >>>>>>>>>>>> > >>>>>>>>>>>> El El lun, 6 de ago. de 2018 a las 12:28, Remo Mattei > >>>>>>>>>>>> <r...@mattei.org <mailto:r...@mattei.org>> escribió: > >>>>>>>>>>>>> https://www.ssls.com <https://www.ssls.com/> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>> > >>>>>>>>>>>>>> On Aug 6, 2018, at 09:26, Eric Broch > >>>>>>>>>>>>>> <ebr...@whitehorsetc.com <mailto:ebr...@whitehorsetc.com>> > >>>>>>>>>>>>>> wrote: > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> Where'd you get this certificate? > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> On 8/6/2018 8:46 AM, Remo Mattei wrote: > >>>>>>>>>>>>>>> I just bought a two year valid cert fro 11.98 or so less > >>>>>>>>>>>>>>> than $12 > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> *dal mio iPhone X* > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>> Il giorno 06 ago 2018, alle ore 07:20, Eric Broch > >>>>>>>>>>>>>>> <ebr...@whitehorsetc.com > >>>>>>>>>>>>>>> <mailto:ebr...@whitehorsetc.com>> ha scritto: > >>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> A signed certificate (not self-signed) may be required > >>>>>>>>>>>>>>>> by Outlook365. If you use LetsEncrypt it won't cost a > >>>>>>>>>>>>>>>> thing. If I remember correctly Outlook for my tablet > >>>>>>>>>>>>>>>> required a signed certificate. > >>>>>>>>>>>>>>>> https://www.qmailtoaster.org/ssl.html > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> On 8/6/2018 2:12 AM, ChandranManikandan wrote: > >>>>>>>>>>>>>>>>> Hi Peter, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> We are using office 365 latest version 2016 and office > >>>>>>>>>>>>>>>>> 2010. > >>>>>>>>>>>>>>>>> Office 2010 is working perfect without any issue but > >>>>>>>>>>>>>>>>> the latest version outlook 2016 (Office 365) is having > >>>>>>>>>>>>>>>>> the problem. > >>>>>>>>>>>>>>>>> Even unable to configure the new IMAP email account. > >>>>>>>>>>>>>>>>> Am always getting this certificate warning message > >>>>>>>>>>>>>>>>> whenever opening outlook or configure outlook. > >>>>>>>>>>>>>>>>> Is it required? PFA warning message. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> My toaster config is below and cache config is in > >>>>>>>>>>>>>>>>> passdb in my toaster.conf. What would you advise it. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> # Settings for 'stock' qmail-toaster > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> auth_cache_size = 32M > >>>>>>>>>>>>>>>>> #auth_mechanisms = plain login digest-md5 cram-md5 > >>>>>>>>>>>>>>>>> auth_mechanisms = plain login digest-md5 > >>>>>>>>>>>>>>>>> auth_username_format = %Lu > >>>>>>>>>>>>>>>>> first_valid_uid = 89 > >>>>>>>>>>>>>>>>> #first_valid_gid = 89 > >>>>>>>>>>>>>>>>> log_path = /var/log/dovecot.log > >>>>>>>>>>>>>>>>> login_greeting = Dovecot toaster ready. > >>>>>>>>>>>>>>>>> #mail_plugins = $mail_plugins quota > >>>>>>>>>>>>>>>>> plugin/quota = maildir > >>>>>>>>>>>>>>>>> protocols = imap > >>>>>>>>>>>>>>>>> ssl_cert = </var/qmail/control/servercert.pem > >>>>>>>>>>>>>>>>> ssl_key = </var/qmail/control/servercert.pem > >>>>>>>>>>>>>>>>> # the following will likely be the default at some point > >>>>>>>>>>>>>>>>> ssl_dh_parameters_length = 2048 > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> namespace { > >>>>>>>>>>>>>>>>> inbox = yes > >>>>>>>>>>>>>>>>> location = > >>>>>>>>>>>>>>>>> # prefix = > >>>>>>>>>>>>>>>>> prefix = INBOX. > >>>>>>>>>>>>>>>>> # Use 'prefix = INBOX.' for Courier-IMAP compatible > >>>>>>>>>>>>>>>>> transparent migration. > >>>>>>>>>>>>>>>>> # This forces all client apps to create subfolders > >>>>>>>>>>>>>>>>> underneath/within > >>>>>>>>>>>>>>>>> # the inbox instead of adjacent to it. It's not > >>>>>>>>>>>>>>>>> necessary to be that way. > >>>>>>>>>>>>>>>>> # FWIW, shubes thinks this setting is > >>>>>>>>>>>>>>>>> annoying/rediculous/retarded. > >>>>>>>>>>>>>>>>> # As a practical example, having no prefix allows > >>>>>>>>>>>>>>>>> mobile users to select > >>>>>>>>>>>>>>>>> # which folders get synchronized. Otherwise their whole > >>>>>>>>>>>>>>>>> mailbox is > >>>>>>>>>>>>>>>>> # synchronized, and they have no way to choose which > >>>>>>>>>>>>>>>>> folders they want sync'd. > >>>>>>>>>>>>>>>>> separator = . > >>>>>>>>>>>>>>>>> type = private > >>>>>>>>>>>>>>>>> } > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> passdb { > >>>>>>>>>>>>>>>>> args = cache_key=%u webmail=127.0.0.1 > >>>>>>>>>>>>>>>>> driver = vpopmail > >>>>>>>>>>>>>>>>> } > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> #protocol imap { > >>>>>>>>>>>>>>>>> # imap_client_workarounds = "delay-newmail" > >>>>>>>>>>>>>>>>> # mail_plugins = $mail_plugins imap_quota > >>>>>>>>>>>>>>>>> # mail_max_userip_connections = 500 > >>>>>>>>>>>>>>>>> #} > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> #protocol pop3 { > >>>>>>>>>>>>>>>>> # pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > >>>>>>>>>>>>>>>>> # pop3_fast_size_lookups = yes > >>>>>>>>>>>>>>>>> # pop3_lock_session = yes > >>>>>>>>>>>>>>>>> # pop3_uidl_format = UID%u-%v > >>>>>>>>>>>>>>>>> #} > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> userdb { > >>>>>>>>>>>>>>>>> args = cache_key=%u > >>>>>>>>>>>>>>>>> quota_template=quota_rule=*:backend=%q > >>>>>>>>>>>>>>>>> driver = vpopmail > >>>>>>>>>>>>>>>>> } > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> plugin { > >>>>>>>>>>>>>>>>> quota = maildir:ignore=Trash > >>>>>>>>>>>>>>>>> quota_rule = ?:storage=0 > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> Hi Eric, > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> I have tried to click Confirm security for store but no > >>>>>>>>>>>>>>>>> process happened. means the screen is idle it couldn't > >>>>>>>>>>>>>>>>> happened anything. > >>>>>>>>>>>>>>>>> All other systems are configured old thunderbird > >>>>>>>>>>>>>>>>> version in ubuntu and all showing the same message and > >>>>>>>>>>>>>>>>> able to store it. > >>>>>>>>>>>>>>>>> But the newer version unable to store it. > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> On Mon, Aug 6, 2018 at 2:57 PM, Peter Peltonen > >>>>>>>>>>>>>>>>> <peter.pelto...@gmail.com > >>>>>>>>>>>>>>>>> <mailto:peter.pelto...@gmail.com>> wrote: > >>>>>>>>>>>>>>>>>> Not sure if this relates to any of your problems: > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> I had a few days ago problem with a Outlook 2016 > >>>>>>>>>>>>>>>>>> stopping receiving > >>>>>>>>>>>>>>>>>> email suddenly. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> I chased this down to Outlook claming the server did > >>>>>>>>>>>>>>>>>> not support the > >>>>>>>>>>>>>>>>>> correct authentication method, which was strange as > >>>>>>>>>>>>>>>>>> nothing had > >>>>>>>>>>>>>>>>>> changed on the server side for a while. The same > >>>>>>>>>>>>>>>>>> user's iPhone with > >>>>>>>>>>>>>>>>>> the same username/password was working at the same > >>>>>>>>>>>>>>>>>> time correctly. > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> What I think it was Dovecot caching credentials > >>>>>>>>>>>>>>>>>> somehow wrong: > >>>>>>>>>>>>>>>>>> differet caching for iPhone and Outlook causing the > >>>>>>>>>>>>>>>>>> problem. I solved > >>>>>>>>>>>>>>>>>> it by changing > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> cache_key=%u > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> entries to > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> cache_key=%u%r > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> in /etc/dovecot/toaster.conf > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> so Outlook connecting from different IP got cached > >>>>>>>>>>>>>>>>>> differently than > >>>>>>>>>>>>>>>>>> the iPhone. Don't know what will happen when they > >>>>>>>>>>>>>>>>>> appear in the same > >>>>>>>>>>>>>>>>>> WLAN though... > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Why did this not happen before, I don't know, perhaps > >>>>>>>>>>>>>>>>>> Outlook has been > >>>>>>>>>>>>>>>>>> updated and uses now some other auth by default than > >>>>>>>>>>>>>>>>>> before? > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Not sure if this relates to your problem at all, as I > >>>>>>>>>>>>>>>>>> am running > >>>>>>>>>>>>>>>>>> pretty old Dovecot... > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> Best, > >>>>>>>>>>>>>>>>>> Peter > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> On Mon, Aug 6, 2018 at 9:19 AM, ChandranManikandan > >>>>>>>>>>>>>>>>>> <kand...@gmail.com <mailto:kand...@gmail.com>> wrote: > >>>>>>>>>>>>>>>>>> > Hi Eric, > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > Yes, we are using Ubuntu latest 64 bit version, > >>>>>>>>>>>>>>>>>> > We tried to configure the imap email and we got the > >>>>>>>>>>>>>>>>>> attached message and > >>>>>>>>>>>>>>>>>> > couldn't configure it. > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > Any one face the same issue. > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > Please help me to resolve the issue. > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > As well the same issue on Outlook 2016 unable to > >>>>>>>>>>>>>>>>>> receive emails. > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > Everything work well before but latest version > >>>>>>>>>>>>>>>>>> having the issue. > >>>>>>>>>>>>>>>>>> > Is it need to install any certificate on our server. > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > Am using COS 6 32 bit , Qmailtoaster. > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > On Mon, Aug 6, 2018 at 1:22 PM, ChandranManikandan > >>>>>>>>>>>>>>>>>> <kand...@gmail.com <mailto:kand...@gmail.com>> > >>>>>>>>>>>>>>>>>> > wrote: > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> Hi Eric, > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> Yes, we are using Ubuntu latest 64 bit version, > >>>>>>>>>>>>>>>>>> >> We tried to configure the imap email and we got the > >>>>>>>>>>>>>>>>>> attached message and > >>>>>>>>>>>>>>>>>> >> couldn't configure it. > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> Any one face the same issue. > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> Please help me to resolve the issue. > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> As well the same issue on Outlook 2016 unable to > >>>>>>>>>>>>>>>>>> receive emails. > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> Everything work well before but latest version > >>>>>>>>>>>>>>>>>> having the issue. > >>>>>>>>>>>>>>>>>> >> Is it need to install any certificate on our server. > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> Am using COS 6 32 bit , Qmailtoaster. > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> On Mon, Aug 6, 2018 at 5:59 AM, Eric Broch > >>>>>>>>>>>>>>>>>> <ebr...@whitehorsetc.com <mailto:ebroch@whitehorsetc. > com>> > >>>>>>>>>>>>>>>>>> >> wrote: > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> Just an FYI. > >>>>>>>>>>>>>>>>>> >>> If your client is using Ubuntu 18.04 there is an > >>>>>>>>>>>>>>>>>> issue with the network > >>>>>>>>>>>>>>>>>> >>> stopping on the local pc. > >>>>>>>>>>>>>>>>>> >>> To test get your client to use the GUI network > >>>>>>>>>>>>>>>>>> manager and disconnect > >>>>>>>>>>>>>>>>>> >>> wait > >>>>>>>>>>>>>>>>>> >>> a few seconds then reconnect. > >>>>>>>>>>>>>>>>>> >>> We are chasing a similar issue now for a client. > >>>>>>>>>>>>>>>>>> >>> To see if this is the issue either try pinging out > >>>>>>>>>>>>>>>>>> of the network or > >>>>>>>>>>>>>>>>>> >>> loading a web page. > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> best wishes > >>>>>>>>>>>>>>>>>> >>> Tony White > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> On 03/08/18 01:16, Eric Broch wrote: > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> Can you check if the password for the account is > >>>>>>>>>>>>>>>>>> saved in Thunderbird on > >>>>>>>>>>>>>>>>>> >>> the Ubuntu desktop? > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> In Thunderbird go to > >>>>>>>>>>>>>>>>>> Tools->Options->Security->Saved Passwords > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> On 8/2/2018 4:52 AM, ChandranManikandan wrote: > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> Hi Friends, > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> One of our user getting disconnected frequently > >>>>>>>>>>>>>>>>>> from thunderbird (Asking > >>>>>>>>>>>>>>>>>> >>> passwords) and webmail also not opening. > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> After restart the dovecot service it will working > >>>>>>>>>>>>>>>>>> again. > >>>>>>>>>>>>>>>>>> >>> But the password is asking frequently. > >>>>>>>>>>>>>>>>>> >>> I have restarted the dovecot service frequently. > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> This problem for only one user rest of other users > >>>>>>>>>>>>>>>>>> not an issue. > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> I couldn't trace the logs in /var/log/maillog and > >>>>>>>>>>>>>>>>>> /var/log/dovecot.log > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> Anyone face the same issue . > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> Could anyone help me to resolve this issue. > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> Note: User is using Ubuntu Desktop with Thunderbird. > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> -- > >>>>>>>>>>>>>>>>>> >>> Thanks & Best Regards, > >>>>>>>>>>>>>>>>>> >>> Manikandan.C > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> -- > >>>>>>>>>>>>>>>>>> >>> Eric Broch > >>>>>>>>>>>>>>>>>> >>> White Horse Technical Consulting (WHTC) > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >>> > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> > >>>>>>>>>>>>>>>>>> >> -- > >>>>>>>>>>>>>>>>>> >> Thanks & Best Regards, > >>>>>>>>>>>>>>>>>> >> Manikandan.C > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > -- > >>>>>>>>>>>>>>>>>> > Thanks & Best Regards, > >>>>>>>>>>>>>>>>>> > Manikandan.C > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> > > >>>>>>>>>>>>>>>>>> ------------------------------ > --------------------------------------- > >>>>>>>>>>>>>>>>>> > To unsubscribe, > >>>>>>>>>>>>>>>>>> e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com > >>>>>>>>>>>>>>>>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> > >>>>>>>>>>>>>>>>>> > For additional commands, > >>>>>>>>>>>>>>>>>> e-mail: qmailtoaster-list-h...@qmailtoaster.com > >>>>>>>>>>>>>>>>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>>> ------------------------------ > --------------------------------------- > >>>>>>>>>>>>>>>>>> To unsubscribe, > >>>>>>>>>>>>>>>>>> e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com > >>>>>>>>>>>>>>>>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> > >>>>>>>>>>>>>>>>>> For additional commands, > >>>>>>>>>>>>>>>>>> e-mail: qmailtoaster-list-h...@qmailtoaster.com > >>>>>>>>>>>>>>>>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com> > >>>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>>> /*Thanks & Best Regards,*/*/ > >>>>>>>>>>>>>>>>> /Manikandan.C//* > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>>> ------------------------------ > --------------------------------------- > >>>>>>>>>>>>>>>>> To unsubscribe, e-mail: qmailtoaster-list-unsubscribe@ > qmailtoaster.com > >>>>>>>>>>>>>>>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> > >>>>>>>>>>>>>>>>> For additional commands, e-mail: qmailtoaster-list-help@ > qmailtoaster.com > >>>>>>>>>>>>>>>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> > >>>>>>>>>>>>>>>> -- > >>>>>>>>>>>>>>>> Eric Broch > >>>>>>>>>>>>>>>> White Horse Technical Consulting (WHTC) > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> > >>>>>>>>>>>>>> -- > >>>>>>>>>>>>>> Eric Broch > >>>>>>>>>>>>>> White Horse Technical Consulting (WHTC) > >>>>>>>>>>>>> > >>>>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> /*Thanks & Best Regards,*/*/ > >>>>>>>>> /Manikandan.C//* > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> Eric Broch > >>>>>>>> White Horse Technical Consulting (WHTC) > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> -- > >>>>>>> /*Thanks & Best Regards,*/*/ > >>>>>>> /Manikandan.C//* > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> ------------------------------------------------------------ > --------- > >>>>>>> To unsubscribe, e-mail: qmailtoaster-list-unsubscribe@ > qmailtoaster.com > >>>>>>> <mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com> > >>>>>>> For additional commands, e-mail: qmailtoaster-list-help@ > qmailtoaster.com > >>>>>>> <mailto:qmailtoaster-list-h...@qmailtoaster.com> > >>>>>> > >>>>>> > >>>>>> -- > >>>>>> Eric Broch > >>>>>> White Horse Technical Consulting (WHTC) > >>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> /*Thanks & Best Regards,*/*/ > >>>>> /Manikandan.C//* > >>>> > >>>> > >>>> -- > >>>> Eric Broch > >>>> White Horse Technical Consulting (WHTC) > >>> > >>> > >>> > >>> -- > >>> /*Thanks & Best Regards,*/*/ > >>> /Manikandan.C//* > >> > >> > >> > >> -- > >> /*Thanks & Best Regards,*/*/ > >> /Manikandan.C//* > >> > >> > >> ------------------------------------------------------------ > ------------ > >> Avast logo <https://www.avast.com/antivirus> > >> > >> This email has been checked for viruses by Avast antivirus software. > >> www.avast.com <https://www.avast.com/antivirus> > >> > >> > >> <x-msg://22/#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> > >> > > > > -- *Thanks & Best Regards,Manikandan.C*