[qmailtoaster] Re: vpopmail --disable-many-domains option
On 06/07/2011 12:02 AM, Jake Vickers wrote: On 05/29/2011 03:32 AM, Martin Waschbüsch IT-Dienstleistungen wrote: Hi Jake, Am 28.05.2011 um 17:19 schrieb Jake Vickers: So I'm still curious as to what you think the benefits are. Segregating your data into multiple tables was always the way I learned to obtain performance. The nature of the requests from QMT are probably not those that would require any performance tuning - the only one I've ever run into is the default number of connections. So I'm willing to table that point if there are other mitigating factors. So what are the advantages/benefits you are thinking will be gained from a single table? I agree with Eric that it probably will not make much of a difference with regards to performance. However, a lot of applications that might want to have access to the email user database are not all that flexible and do not support having different domains in different tables. E.g. using courier-auth with mysql or SOGo with mysql-backend, etc. There are other examples. For my own use, I have written an accounting backend that also cycles through domains and users, etc. to produce detail-information to be attached to invoices and that, too, is just way easier when having all in one table. Granted, that may be simplistic design on the parts of those programs, but hey, it works and it is way easier to recompile vpopmail to achieve compatibility than patch those programs. Also, whenever there is any database schema change in order for vpopmail to be upgraded, it is much easier to upgrade that one table than to find all the tables that hold domains and path those. Last but not least, mysql (and other databases) have length-limitations for domain names. I always wondered, but never tried, what would happen if I added a domain with a name longer than 'max-table-name-length' to the database? I think the current limit for mysql is 32 chars and domain names can be longer. I have never tried a FQDN longer than 32 chars - RFC 1035 implies (if I'm reading it correctly) of 255 chars: 2.3.4. Size limits Various objects and parameters in the DNS have size limits. They are listed below. Some could be easily changed, others are more fundamental. labels 63 octets or less names 255 octets or less TTL positive values of a signed 32 bit number. UDP messages 512 octets or less 3. DOMAIN NAME SPACE AND RR DEFINITIONS 3.1. Name space definitions Domain names in messages are expressed in terms of a sequence of labels. Each label is represented as a one octet length field followed by that number of octets. Since every domain name ends with the null label of the root, a domain name is terminated by a length byte of zero. The high order two bits of every length octet must be zero, and the remaining six bits of the length field limit the label to 63 octets or less. To simplify implementations, the total length of a domain name (i.e., label octets and label length octets) is restricted to 255 octets or less. Although labels can contain any 8 bit values in octets that make up a label, it is strongly recommended that labels follow the preferred syntax described elsewhere in this memo, which is compatible with existing host naming conventions. Name servers and resolvers must compare labels in a case-insensitive manner (i.e., A=a), assuming ASCII with zero parity. Non-alphabetic codes must match exactly. Should be easy enough to change in 2.x. Thanks for the app examples for the vpopmail DB schema. So the change seems to hinge around opinion and interop with other applications. I went back over the "helper apps" and can't find anywhere in the code where a change may make something currently supplied stop working, so I'll roll the change into the 2.x test and we'll see what shakes loose. - Thanks Jake. This database conversion may be a little tricky to automate entirely. I'm thinking there'd need to be a list of some sort identifying each database table that needs to be converted/consolidated. Might be able to write a query of database tables (metadata) to determine them all. Do we have any MySQL experts here that can assist with such automation? -- -Eric 'shubes' - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: qmail-smtpd: qq soft reject
in log file /var/log/clamav/unofficial-sigs.log I have: INFO - Next SecuriteInfo check will be performed in approximately 2 hour(s), 4 minute(s) Jun 07 09:33:51 INFO - Checking for MalwarePatrol updates... Jun 07 09:33:52 INFO - Testing updated database file: mbl.ndb Jun 07 09:33:52 INFO - Clamscan reports Sanesecurity mbl.ndb database integrity tested good Jun 07 09:33:52 INFO - Successfully updated MalwarePatrol production database file: mbl.ndb Jun 07 09:33:52 INFO - Update(s) detected, reloaded ClamAV databases these times also correlate to the log file /var/log/qmail/clamd/current: Waiting for all threads to finish 2011-06-07 09:33:53.164200500 Shutting down the main socket. 2011-06-07 09:33:53.164416500 --- Stopped at Tue Jun 7 09:33:53 2011 2011-06-07 09:33:53.164440500 Closing the main socket. 2011-06-07 09:33:53.164485500 Socket file removed. 2011-06-07 09:33:53.632970500 LibClamAV Warning: Detected duplicate databases /usr/share/clamav/main.cvd and /usr/share/clamav/main.cld, please manually remove one of them 2011-06-07 09:33:57.103557500 Limits: Global size limit set to 104857600 bytes. 2011-06-07 09:33:57.103559500 Limits: File size limit set to 26214400 bytes. 2011-06-07 09:33:57.103560500 Limits: Recursion level limit set to 16. 2011-06-07 09:33:57.103560500 Limits: Files limit set to 1. 2011-06-07 09:33:57.103561500 Limits: Core-dump limit is 0. 2011-06-07 09:33:57.103561500 Archive support enabled. 2011-06-07 09:33:57.103562500 Algorithmic detection enabled. 2011-06-07 09:33:57.103562500 Portable Executable support enabled. 2011-06-07 09:33:57.103563500 ELF support enabled. 2011-06-07 09:33:57.103602500 Mail files support enabled. 2011-06-07 09:33:57.103603500 OLE2 support enabled. 2011-06-07 09:33:57.103612500 PDF support enabled. 2011-06-07 09:33:57.103612500 HTML support enabled. 2011-06-07 09:33:57.103613500 Self checking every 600 seconds. 2011-06-07 09:33:57.103613500 Listening daemon: PID: 19474 2011-06-07 09:33:57.103614500 MaxQueue set to: 100 I also have found /etc/cron.d/clamav-unofficial-sigs-cron I believe this file is what is updateing some of the clam sigs and causing clam to restart. The problem is that clam takes 4 to 5 seconds to restart, which is not a lot but I am unlucky enough to have customers sending email at those times causing the soft reject errors. is anyone else having these problems? Thanks -- Aaron Powell IT Manager S&T Communications Office: 785-460-7300 Fax: 785-460-7301 Quoting Jake Vickers : On 05/18/2011 01:35 PM, apow...@st-tel.net wrote: sorry. I am using the sanesecurity updates. Thanks Is the system underpowered? I've seen this when clamav is restarted and the system will return qq rejects until it can scan the databases for integrity. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com -- BEGIN-ANTISPAM-VOTING-LINKS -- Teach CanIt if this mail (ID 04EJvk4oe) is spam: Spam: http://spam.st-tel.net/canit/b.php?i=04EJvk4oe&m=e26d4b99f9e7&t=20110519&c=s Not spam: http://spam.st-tel.net/canit/b.php?i=04EJvk4oe&m=e26d4b99f9e7&t=20110519&c=n Forget vote: http://spam.st-tel.net/canit/b.php?i=04EJvk4oe&m=e26d4b99f9e7&t=20110519&c=f -- END-ANTISPAM-VOTING-LINKS - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] deferral: ezmlm-send:_fatal:_unable_to_obtain_
in /var/log/messages I get: kernel: lockd: server 10.2.1.165 not responding, timed out (10.2.1.165 is the nfs server) the mailstores are still accessable. I have been running this setup for a long time, but we just recently started using the mailing lists. Thanks -- Aaron Powell IT Manager S&T Communications Office: 785-460-7300 Fax: 785-460-7301 Quoting Jake Vickers : On 06/01/2011 12:12 PM, apow...@st-tel.net wrote: I am occasionally getting emails stuck in queue. I am getting deferral: ezmlm-send:_fatal:_unable_to_obtain_ in our /var/log/qmail/send/current log. we do have /home/vpopmail/domains on an nfs server. any ideas? Thanks Any more of the log to share? Are the mailstores still accessable when ezmlm-send is generating this error? When did it start? I assume you've been running it a while and only recently started to see an issue. Upstream update maybe? - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com -- BEGIN-ANTISPAM-VOTING-LINKS -- Teach CanIt if this mail (ID 02EQT5Mio) is spam: Spam: http://spam.st-tel.net/canit/b.php?i=02EQT5Mio&m=6e2b6e244ff9&t=20110607&c=s Not spam: http://spam.st-tel.net/canit/b.php?i=02EQT5Mio&m=6e2b6e244ff9&t=20110607&c=n Forget vote: http://spam.st-tel.net/canit/b.php?i=02EQT5Mio&m=6e2b6e244ff9&t=20110607&c=f -- END-ANTISPAM-VOTING-LINKS - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] Re: Lost 1 folder in IMAP account
On 06/06/2011 09:00 PM, Eric Shubert wrote: I'm no mysql expert, but I'd google "mysql error 28 from storage engine" and see what that code means. Or see if you can find the meaning of code 28 somewhere. I expect it means something specific. I would think that this would only effect the mysqldump portion of the qtp-backup tarball. IIRC, the folders/files in the /home/vpopmail/domains/ folder are in a separate tarball. Have you looked for that particular tarball to recover the lost folder? The mailstore is indeed in a different tarball, so if the folder existed previously it should be in one of those backups. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] deferral: ezmlm-send:_fatal:_unable_to_obtain_
On 06/01/2011 12:12 PM, apow...@st-tel.net wrote: I am occasionally getting emails stuck in queue. I am getting deferral: ezmlm-send:_fatal:_unable_to_obtain_ in our /var/log/qmail/send/current log. we do have /home/vpopmail/domains on an nfs server. any ideas? Thanks Any more of the log to share? Are the mailstores still accessable when ezmlm-send is generating this error? When did it start? I assume you've been running it a while and only recently started to see an issue. Upstream update maybe? - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
Re: [qmailtoaster] vpopmail --disable-many-domains option
On 05/29/2011 03:32 AM, Martin Waschbüsch IT-Dienstleistungen wrote: Hi Jake, Am 28.05.2011 um 17:19 schrieb Jake Vickers: So I'm still curious as to what you think the benefits are. Segregating your data into multiple tables was always the way I learned to obtain performance. The nature of the requests from QMT are probably not those that would require any performance tuning - the only one I've ever run into is the default number of connections. So I'm willing to table that point if there are other mitigating factors. So what are the advantages/benefits you are thinking will be gained from a single table? I agree with Eric that it probably will not make much of a difference with regards to performance. However, a lot of applications that might want to have access to the email user database are not all that flexible and do not support having different domains in different tables. E.g. using courier-auth with mysql or SOGo with mysql-backend, etc. There are other examples. For my own use, I have written an accounting backend that also cycles through domains and users, etc. to produce detail-information to be attached to invoices and that, too, is just way easier when having all in one table. Granted, that may be simplistic design on the parts of those programs, but hey, it works and it is way easier to recompile vpopmail to achieve compatibility than patch those programs. Also, whenever there is any database schema change in order for vpopmail to be upgraded, it is much easier to upgrade that one table than to find all the tables that hold domains and path those. Last but not least, mysql (and other databases) have length-limitations for domain names. I always wondered, but never tried, what would happen if I added a domain with a name longer than 'max-table-name-length' to the database? I think the current limit for mysql is 32 chars and domain names can be longer. I have never tried a FQDN longer than 32 chars - RFC 1035 implies (if I'm reading it correctly) of 255 chars: 2.3.4. Size limits Various objects and parameters in the DNS have size limits. They are listed below. Some could be easily changed, others are more fundamental. labels 63 octets or less names 255 octets or less TTL positive values of a signed 32 bit number. UDP messages512 octets or less 3. DOMAIN NAME SPACE AND RR DEFINITIONS 3.1. Name space definitions Domain names in messages are expressed in terms of a sequence of labels. Each label is represented as a one octet length field followed by that number of octets. Since every domain name ends with the null label of the root, a domain name is terminated by a length byte of zero. The high order two bits of every length octet must be zero, and the remaining six bits of the length field limit the label to 63 octets or less. To simplify implementations, the total length of a domain name (i.e., label octets and label length octets) is restricted to 255 octets or less. Although labels can contain any 8 bit values in octets that make up a label, it is strongly recommended that labels follow the preferred syntax described elsewhere in this memo, which is compatible with existing host naming conventions. Name servers and resolvers must compare labels in a case-insensitive manner (i.e., A=a), assuming ASCII with zero parity. Non-alphabetic codes must match exactly. Should be easy enough to change in 2.x. Thanks for the app examples for the vpopmail DB schema. So the change seems to hinge around opinion and interop with other applications. I went back over the "helper apps" and can't find anywhere in the code where a change may make something currently supplied stop working, so I'll roll the change into the 2.x test and we'll see what shakes loose. - Qmailtoaster is sponsored by Vickers Consulting Group (www.vickersconsulting.com) Vickers Consulting Group offers Qmailtoaster support and installations. If you need professional help with your setup, contact them today! - Please visit qmailtoaster.com for the latest news, updates, and packages. To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
