Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

> On Jun 10, 2016, at 1:09 PM, Eric wrote: > > Mine is twice that: 12800 That’s what I set mine to just now; I also set the submission softlimit back to that. Now I know better how to track the segfaults, if they occur, so we’ll see how they both go over the

Re: [qmailtoaster] Webmail Imap Login Failure

Awesome. Thank you. Ed On 6/10/2016 9:56 AM, Eric wrote: Also, Dovecot keeps an old password in memory. Restarting Dovecot can sometimes solve issues like this. On 6/10/2016 10:53 AM, Eric wrote: Hi Ed, Next time just change the password at the CLI (vpasswd), it has worked in the past

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Mine is twice that: 12800 On 6/10/2016 11:07 AM, Steve Linberg wrote: On Jun 10, 2016, at 12:49 PM, Eric > wrote: Steve, I think 19152 of vchkpw[19152] is the process id. Can you look through the log file in /var/log/qmail/smtp,

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

> On Jun 10, 2016, at 12:49 PM, Eric wrote: > > Steve, > > I think 19152 of vchkpw[19152] is the process id. Can you look through the > log file in /var/log/qmail/smtp, /var/log/qmail/send, and > /var/log/qmail/submission for such a process? Ah - I should have

Re: [qmailtoaster] Webmail Imap Login Failure

Also, Dovecot keeps an old password in memory. Restarting Dovecot can sometimes solve issues like this. On 6/10/2016 10:53 AM, Eric wrote: Hi Ed, Next time just change the password at the CLI (vpasswd), it has worked in the past when I had similar problems and saves recreating an account.

Re: [qmailtoaster] Webmail Imap Login Failure

Hi Ed, Next time just change the password at the CLI (vpasswd), it has worked in the past when I had similar problems and saves recreating an account. Eric On 6/10/2016 10:29 AM, Ed Morrison wrote: Hi Eric: It was just 1 account not all accounts within the domain. I deleted and recreated

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Hi Steve, Steve, I think 19152 of vchkpw[19152] is the process id. Can you look through the log file in /var/log/qmail/smtp, /var/log/qmail/send, and /var/log/qmail/submission for such a process? Also look in the dovecot log for error at the specified time. Eric On 6/10/2016 10:14 AM,

RE: [qmailtoaster] vchkpw segfaults and spamdyke errors

Those are from 2013 and 2014, could be present if the OS is really old, but I believe Steve is running centos7. -Original Message- From: Noriyuki Hayashi [mailto:nhaya...@wats.gr.jp] Sent: Friday, June 10, 2016 9:23 AM To: qmailtoaster-list@qmailtoaster.com Subject: Re: [qmailtoaster]

RE: [qmailtoaster] vchkpw segfaults and spamdyke errors

Don’t assume it is submission – unless you have a good reason to know you are sending emails at those times. ‘Submission’ only runs when a client connects on 587 to send email. if it is only you then you will know when you are sending. I think it can be imap4, imap4ssl, pop, etc., i.e. the

Re: [qmailtoaster] Webmail Imap Login Failure

Hi Eric: It was just 1 account not all accounts within the domain. I deleted and recreated the account a couple of times now it appears to be ok. Thanks for your support. Ed On 6/10/2016 9:07 AM, Eric wrote: What I mean is, all accounts in the second domain. On 6/10/2016 9:45 AM, Ed

RE: [qmailtoaster] vchkpw segfaults and spamdyke errors

Check you imap log and corresponding run file for raising softlimit. Was your client open overnight (any client, phone, pc, etc.) and checking for email? that also needs authorization. To echo, what log file do you find the segfault in? -Original Message- From: Eric

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Hi, I found some Bug 986427 - segfault error 4 at libc-2.17.so https://bugzilla.redhat.com/show_bug.cgi?id=986427 http://lists.arthurdejong.org/nss-pam-ldapd-users/2014/msg00136.html Does libc-2.17.so has bug? Regards, Nori On Mon, 6 Jun 2016 11:12:08 -0400 Steve Linberg

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

> On Jun 10, 2016, at 11:27 AM, Eric wrote: > > I guess I'm confused. Which log file are you getting segfault in? Jeez, sorry, I referenced it incorrectly before. They’re in /var/log/messages, NOT /var/log/maillog. :( /var/log/messages:Jun 10 09:51:15 xxx kernel:

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Hi again Jaime, Have a look at this article: https://support.zend.com/hc/en-us/articles/203782516-ABRT-logs-messages-with-Package-packagename-isn-t-signed-with-proper-key- Eric On 6/10/2016 10:02 AM, Eric wrote: Hi Jamie, I had these as well on a client server about a month ago for a few

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Thanks for looking into this, Eric. The interesting thing is, the qmailmrtg segfaults didn't happen until I cleared up the vchkpw faults. I'm thinking they both might be related to memory and when I raised the limit for vchkpw it didn't leave enough memory for qmailmrtg to run sometimes. I'm

Re: [qmailtoaster] Webmail Imap Login Failure

What I mean is, all accounts in the second domain. On 6/10/2016 9:45 AM, Ed Morrison wrote: Hi Everyone: I have a qmailtoaster setup with two domains. When logging into the primary domain via webmail everything is fine. But when you try to log into the second domain via webmail I get this

Re: [qmailtoaster] Webmail Imap Login Failure

Is that all accounts? On 6/10/2016 9:45 AM, Ed Morrison wrote: Hi Everyone: I have a qmailtoaster setup with two domains. When logging into the primary domain via webmail everything is fine. But when you try to log into the second domain via webmail I get this error: *ERROR:**ERROR:

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Hi Jamie, I had these as well on a client server about a month ago for a few days and they went away. They showed up in the postmaster logwatch email. I traced them to the messages log. I ran the following command (with output): # cat messages* | grep -C 4 segfault May 18 09:25:02 mail

[qmailtoaster] Webmail Imap Login Failure

Hi Everyone: I have a qmailtoaster setup with two domains. When logging into the primary domain via webmail everything is fine. But when you try to log into the second domain via webmail I get this error: *ERROR:**ERROR: Connection dropped by IMAP server.* Query: LOGOUT Does anyone have

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Hi, I remember that spam is coming happen segmentation errors. Could you check the spam mail. I think this is very funny. But It useful signal. Regards, > Still working on the segfault problem; got dozens of them overnight when I > definitely wasn’t using any services. softlimit in >

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

I guess I'm confused. Which log file are you getting segfault in? On 6/10/2016 9:25 AM, Steve Linberg wrote: On Jun 10, 2016, at 11:14 AM, Eric > wrote: Look in /var/log/maillog and compare times with the occurrences in

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

> On Jun 10, 2016, at 11:14 AM, Eric wrote: > > Look in /var/log/maillog and compare times with the occurrences in > /var/log/qmail/submission/'any log'. Use tai64nlocal to convert time stamps* > in the qmail log. > > *cat /var/log/qmail/submission/'any log' |

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

I don't get segfaults from vchkpw anymore (not since raising my softlimit), but I get from 1-3 segfaults from qmailmrtg daily. I don't really need or want qmailmrtg, so if anyone can tell me how to turn it off, that would be great. :) Otherwise, it's not causing any problems for me since I don't

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Look in /var/log/maillog and compare times with the occurrences in /var/log/qmail/submission/'any log'. Use tai64nlocal to convert time stamps* in the qmail log. *cat /var/log/qmail/submission/'any log' | tai64nlocal | grep segfault > newfile.txt On 6/10/2016 8:48 AM, Steve Linberg wrote:

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Still working on the segfault problem; got dozens of them overnight when I definitely wasn’t using any services. softlimit in /var/qmail/supervise/submission/run is at 500 megs and rising, but I’m still having trouble believing it needs to be that high or higher. While I continue to push that: