[qmailtoaster] QMT vpopmail mysql table dir_control vadduser - vdeluser

2018-01-17 Thread Olaf
Hello I have a new installation of qmailtoaster on the centos 7 system I found a problem with vpopmail in the mysql database vpopmail in the dir_control table. when the user's input via "vadduser t...@domain.com -r" does not increase the number of cur_users. It's at "0". In "vdeluser

Re: [qmailtoaster] QMT - Problem with MessageID on Vacation Message Responses

2018-01-17 Thread Jeff Koch
The URL for GITHUB is: https://github.com/roffe/autorespond-2.0.6/blob/master/patch_2.0.5-2.0.6.patch Jeff On 1/17/2018 2:41 PM, Jeff Koch wrote: I have been testing the vacation message function on the moduser page in qmailadmin. The autoresponses generated by the vacation message option

[qmailtoaster] SOLVED - Re: [qmailtoaster] QMT - Problem with MessageID on Vacation Message Responses

2018-01-17 Thread Jeff Koch
There is a new version of autorespond on GITHUB - version 2.06 - patched April 2016 that fixes the MessageID. The original code in existence since 2001 creates the MessageID as follows: fprintf(fdm,"Date: %u %s %u %02u:%02u:%02u -\nMessage-ID: <%lu.%u.blah>\n"

RE: [qmailtoaster] Odd msg numbers in /var/log/qmail/send/current

2018-01-17 Thread Dan McAllister - QMT DNS Admin
There is nothing unusual about the message numbers: to essentially guarantee a unique number, Qmail uses the inode address (inode number) of the file as the message number. Your inodes are being used and released as normal, and there are blocks the get reused over and over Dan From:

[qmailtoaster] QMT - Problem with MessageID on Vacation Message Responses

2018-01-17 Thread Jeff Koch
I have been testing the vacation message function on the moduser page in qmailadmin. The autoresponses generated by the vacation message option end up in my spam folders because the Message ID generated by the autoresponder do not include a domain name and, as a result, violate RFC 2822.

[qmailtoaster] qq soft reject

2018-01-17 Thread Rajesh M
hi we are getting qq soft reject on one of our server on random basis this is a busy server around -- 6000 mails in 1 hour during peak hours we disabled both spam and clam ie set spam=no, clam=no but still the error continues till we disable the /var/qmail/simscan from the tcp.smtp