Hi again, thanks for the help! I just checked the users and groups as you suggested, and the user vpopmail seems to be defined correctly, but I don't have a group vchkuser apparently. Instead, I have this defined for the group id 89: vchkpw:x:89: Maybe it's a thing of my Kloxo installation?
And about the files in /var/qmail/bin, they seem to be a bit different I think: -rwxrwxrwx 1 root qmail 9152 May 13 2009 bouncesaying -rwxrwxrwx 1 root qmail 26328 May 13 2009 condredirect -rwxrwxrwx 1 root qmail 1087 May 13 2009 config-fast -rwxrwxrwx 1 root qmail 126 May 13 2009 datemail -rwxrwxrwx 1 root qmail 929 May 13 2009 dh_key -rwxrwxrwx 1 root qmail 114 May 13 2009 elq -rwxrwxrwx 1 root qmail 9028 May 13 2009 except -rwxrwxrwx 1 root qmail 26320 May 13 2009 forward -rwxrwxrwx 1 root qmail 24540 May 13 2009 instcheck -rwxrwxrwx 1 root qmail 20252 May 13 2009 maildir2mbox -rwxrwxrwx 1 root qmail 8736 May 13 2009 maildirmake -rwxrwxrwx 1 root qmail 18324 May 13 2009 maildirwatch -rwxrwxrwx 1 root qmail 179 May 13 2009 mailsubj -rwxrwxrwx 1 root qmail 115 May 13 2009 pinq -rwxrwxrwx 1 root qmail 13972 May 13 2009 predate -rwxrwxrwx 1 root qmail 13976 May 13 2009 preline -rwxrwxrwx 1 root qmail 115 May 13 2009 qail -rwxrwxrwx 1 root qmail 12344 May 13 2009 qbiff -rwxrwxrwx 1 root qmail 14316 May 13 2009 qmail-badloadertypes -rwxrwxrwx 1 root qmail 14304 May 13 2009 qmail-badmimetypes -rwxrwxrwx 1 root qmail 10532 May 13 2009 qmail-clean -rw---x--x 1 qmailq qmail 49972 May 13 2009 qmail-dk -rwxrwxrwx 1 root qmail 5832 May 13 2009 qmail-getpw -rwxrwxrwx 1 root qmail 46840 May 13 2009 qmail-inject -rwxrwxrwx 1 root qmail 53308 May 13 2009 qmail-local -rwxrwxrwx 1 root qmail 18116 May 13 2009 qmail-lspawn -rwxrwxrwx 1 root qmail 14496 May 13 2009 qmail-newmrh -rwxrwxrwx 1 root qmail 13932 May 13 2009 qmail-newu -rwxrwxrwx 1 root qmail 18100 May 13 2009 qmail-pw2u -rwxrwxrwx 1 root qmail 14896 May 13 2009 qmail-qmqpc -rwxrwxrwx 1 root qmail 18064 May 13 2009 qmail-qmqpd -rwxrwxrwx 1 root qmail 26272 May 13 2009 qmail-qmtpd -rwxrwxrwx 1 root qmail 18040 May 13 2009 qmail-qread -rwxrwxrwx 1 root qmail 371 May 13 2009 qmail-qstat *lrwxrwxrwx 1 root root 23 Feb 21 08:52 qmail-queue -> /var/qmail/bin/qmail-dk -rwxrwxrwx 1 qmailq qmail 24780 May 13 2009 qmail-queue.orig* -rw---x--x 1 root qmail 44964 May 13 2009 qmail-remote -rwxrwxrwx 1 root qmail 13992 May 13 2009 qmail-rspawn -rwxrwxrwx 1 root qmail 51236 May 13 2009 qmail-send -rwxrwxrwx 1 root qmail 19420 May 13 2009 qmail-showctl -rwxrwxrwx 1 root qmail 146632 May 13 2009 qmail-smtpd -rwxrwxrwx 1 root qmail 5988 May 13 2009 qmail-start -rwxrwxrwx 1 root qmail 9804 May 13 2009 qmail-tcpok -rwxrwxrwx 1 root qmail 10452 May 13 2009 qmail-tcpto -rwxrwxrwx 1 root qmail 26288 May 13 2009 qreceipt -rwxrwxrwx 1 root qmail 11960 May 13 2009 qsmhook -rwxrwxrwx 1 root qmail 10584 May 13 2009 sendmail -rwxrwxrwx 1 clamav root 57709 Apr 28 2010 simscan -rwxrwxrwx 1 root root 18988 Apr 28 2010 simscanmk -rwxrwxrwx 1 root qmail 30596 May 13 2009 spfquery -rwxrwxrwx 1 root qmail 6976 May 13 2009 splogger -rwxrwxrwx 1 root qmail 26320 May 13 2009 srsfilter -rwxrwxrwx 1 root qmail 22152 May 13 2009 tcp-env Regards. On Wed, May 2, 2012 at 9:19 PM, Eric Shubert <e...@shubes.net> wrote: > This sounds like a user/group id problem now. Is the vpopmail user defined > as 89, and vchkuser as group 89? These need to be there exactly. > > Also, check /var/qmail/bin/ for: > lrwxrwxrwx 1 root root 16 Apr 1 20:22 qmail-queue -> > qmail-queue.orig > -rws--x--x 1 qmailq qmail 24776 Mar 29 10:19 qmail-queue.orig > > Note the sticky bit. If qmail-queue links to qmail-queue.dk, that file > should be the same as qmail-queue.orig. > > Just a guess at this point. > > -- > -Eric 'shubes' > > > On 05/02/2012 04:24 PM, Haru wrote: > >> Thanks for the quick reply! >> >> I did what you suggested and downloaded the qmailtoaster-plus package to >> run the queue repair tool. Effectively there were some problems with >> some missing directories and permissions that were fixed with the repair >> mode, so I think now the directories should be fine now, but I'm still >> getting some kind of error if I try to rerun the repair script: >> queue/intd/3/142674293 is mode 644, should be 600 >> changed queue/intd/3/142674293 mode to 600 >> queue/intd/5/142674295 is mode 644, should be 600 >> changed queue/intd/5/142674295 mode to 600 >> I get like 30 of these each run for files in different queue subfolders, >> some times it says it's changing permissions from mode 644 to 600, other >> times it is from 600 to 644. >> > > I think that's ok. I've seen this sort of thing too, but haven't had a > problem as a result. > > Anyways, now with this script I'm getting the incoming and outcoming >> mails to appear in the mail queue, but apparently they are all stuck >> there. I tried to send 3 mails from sendmail and and using a roundcube, >> the later told me that the mail couldn't be send, but I can see it in >> the queue, and 2 of the 3 mails from sendmail are in the queue, the >> other one oddly enough was delivered correctly, even though it was the >> same as the others. >> >> In the logs now I'm getting a lot of "deferral: >> Sorry,_message_has_wrong_**owner._(#4.3.5)/" and "warning: unable to stat >> mess/19/19" kind of messages that weren't there before, so maybe there >> are still some problems with the directories, or maybe there is another >> issue... Here is a part of the logs: >> >> maillog: >> May 3 03:06:25 nanofate qmail: 1335999985.037690 warning: unable to >> stat mess/19/19 >> May 3 03:06:25 nanofate qmail: 1335999985.046517 warning: unable to >> stat mess/5/5 >> May 3 03:06:25 nanofate qmail: 1335999985.063536 warning: unable to >> stat mess/7/7 >> May 3 03:06:25 nanofate qmail: 1335999985.082109 delivery 8: deferral: >> Sorry,_message_has_wrong_**owner._(#4.3.5)/ >> May 3 03:06:25 nanofate qmail: 1335999985.082595 status: local 0/10 >> remote 0/60 >> May 3 03:06:25 nanofate vpopmail[26432]: vchkpw-smtp: vpopmail user not >> found t...@nanofate.us:220.199.70.**244 >> May 3 03:06:35 nanofate qmail: 1335999995.982086 starting delivery 9: >> msg 142674505 to remote bph...@gmail.com <mailto:bph...@gmail.com> >> >> May 3 03:06:35 nanofate qmail: 1335999995.982215 status: local 0/10 >> remote 1/60 >> May 3 03:06:35 nanofate qmail: 1335999995.982308 delivery 9: deferral: >> Sorry,_message_has_wrong_**owner._(#4.3.5)/ >> May 3 03:06:35 nanofate qmail: 1335999995.982367 status: local 0/10 >> remote 0/60 >> May 3 03:07:03 nanofate qmail: 1336000023.870200 warning: unable to >> stat mess/17/17 >> May 3 03:07:03 nanofate qmail: 1336000023.870234 warning: unable to >> stat mess/1/1 >> May 3 03:07:03 nanofate qmail: 1336000023.870250 warning: unable to >> stat mess/15/15 >> May 3 03:07:03 nanofate qmail: 1336000023.870264 warning: unable to >> stat mess/12/12 >> May 3 03:07:03 nanofate qmail: 1336000023.870278 warning: unable to >> stat mess/14/14 >> May 3 03:07:03 nanofate qmail: 1336000023.870292 warning: unable to >> stat mess/4/4 >> May 3 03:07:03 nanofate qmail: 1336000023.870307 warning: unable to >> stat mess/16/16 >> May 3 03:07:03 nanofate qmail: 1336000023.870319 new msg 142674511 >> May 3 03:07:03 nanofate qmail: 1336000023.870336 info msg 142674511: >> bytes 1385 from <cd_bl...@hotmail.com <mailto:cd_bl...@hotmail.com>> qp >> >> 27714 uid 0 >> May 3 03:07:03 nanofate qmail: 1336000023.945473 starting delivery 10: >> msg 142674511 to local nanofate.u...@nanofate.us >> <mailto:nanofate.us-a@**nanofate.us <nanofate.u...@nanofate.us>> >> >> May 3 03:07:03 nanofate qmail: 1336000023.945502 status: local 1/10 >> remote 0/60 >> May 3 03:07:03 nanofate qmail: 1336000023.945518 warning: unable to >> stat mess/9/9 >> May 3 03:07:03 nanofate qmail: 1336000023.945531 warning: unable to >> stat mess/3/3 >> May 3 03:07:03 nanofate qmail: 1336000023.945546 warning: unable to >> stat mess/13/13 >> May 3 03:07:03 nanofate qmail: 1336000023.945559 warning: unable to >> stat mess/8/8 >> May 3 03:07:04 nanofate qmail: 1336000024.617415 warning: unable to >> stat mess/21/21 >> May 3 03:07:05 nanofate qmail: 1336000025.508587 warning: unable to >> stat mess/22/22 >> May 3 03:07:05 nanofate qmail: 1336000025.876071 warning: unable to >> stat mess/6/6 >> May 3 03:07:05 nanofate qmail: 1336000025.927003 warning: unable to >> stat mess/18/18 >> May 3 03:07:05 nanofate qmail: 1336000025.943867 warning: unable to >> stat mess/20/20 >> May 3 03:07:05 nanofate qmail: 1336000025.965421 warning: unable to >> stat mess/11/11 >> May 3 03:07:05 nanofate qmail: 1336000025.981071 warning: unable to >> stat mess/10/10 >> May 3 03:07:05 nanofate qmail: 1336000025.986292 warning: unable to >> stat mess/2/2 >> May 3 03:07:06 nanofate qmail: 1336000026.001581 warning: unable to >> stat mess/0/0 >> May 3 03:07:06 nanofate qmail: 1336000026.026589 warning: unable to >> stat mess/19/19 >> May 3 03:07:06 nanofate qmail: 1336000026.032288 warning: unable to >> stat mess/5/5 >> May 3 03:07:06 nanofate qmail: 1336000026.044130 warning: unable to >> stat mess/7/7 >> May 3 03:07:06 nanofate qmail: 1336000026.053075 warning: unable to >> stat mess/17/17 >> May 3 03:07:06 nanofate qmail: 1336000026.063087 warning: unable to >> stat mess/1/1 >> May 3 03:07:06 nanofate qmail: 1336000026.075012 warning: unable to >> stat mess/15/15 >> May 3 03:07:06 nanofate qmail: 1336000026.156921 warning: unable to >> stat mess/12/12 >> May 3 03:07:06 nanofate qmail: 1336000026.882570 warning: unable to >> stat mess/14/14 >> May 3 03:07:06 nanofate qmail: 1336000026.895672 warning: unable to >> stat mess/4/4 >> May 3 03:07:06 nanofate qmail: 1336000026.900550 warning: unable to >> stat mess/16/16 >> May 3 03:07:06 nanofate qmail: 1336000026.994569 warning: unable to >> stat mess/9/9 >> May 3 03:07:07 nanofate qmail: 1336000027.052632 warning: unable to >> stat mess/3/3 >> May 3 03:07:07 nanofate qmail: 1336000027.066380 warning: unable to >> stat mess/13/13 >> May 3 03:07:07 nanofate qmail: 1336000027.083732 warning: unable to >> stat mess/8/8 >> May 3 03:07:07 nanofate qmail: 1336000027.100545 warning: unable to >> stat mess/21/21 >> May 3 03:07:07 nanofate qmail: 1336000027.109735 warning: unable to >> stat mess/22/22 >> May 3 03:07:07 nanofate qmail: 1336000027.123859 warning: unable to >> stat mess/6/6 >> May 3 03:07:07 nanofate qmail: 1336000027.134544 warning: unable to >> stat mess/18/18 >> May 3 03:07:07 nanofate qmail: 1336000027.137171 warning: unable to >> stat mess/20/20 >> May 3 03:07:07 nanofate qmail: 1336000027.144549 warning: unable to >> stat mess/11/11 >> May 3 03:07:07 nanofate qmail: 1336000027.156179 warning: unable to >> stat mess/10/10 >> May 3 03:07:07 nanofate qmail: 1336000027.170765 warning: unable to >> stat mess/2/2 >> May 3 03:07:07 nanofate qmail: 1336000027.191070 warning: unable to >> stat mess/0/0 >> May 3 03:07:07 nanofate qmail: 1336000027.244561 warning: unable to >> stat mess/19/19 >> May 3 03:07:07 nanofate qmail: 1336000027.266708 warning: unable to >> stat mess/5/5 >> May 3 03:07:07 nanofate qmail: 1336000027.377792 warning: unable to >> stat mess/7/7 >> May 3 03:07:07 nanofate qmail: 1336000027.385268 delivery 10: deferral: >> Sorry,_message_has_wrong_**owner._(#4.3.5)/ >> May 3 03:07:07 nanofate qmail: 1336000027.402026 status: local 0/10 >> remote 0/60 >> May 3 03:07:10 nanofate vpopmail[27753]: vchkpw-smtp: vpopmail user not >> found t...@nanofate.us:222.218.130.**138 >> May 3 03:07:15 nanofate vpopmail[27772]: vchkpw-smtp: vpopmail user not >> found t...@nanofate.us:220.199.70.**244 >> >> >> smtp.log (I think this looks normal now...?): >> 1335997754 2012-May-03 02:29 __lxlabs_marker >> CHKUSER accepted rcpt: from <cd_bl...@hotmail.com::> remote >> <:blu0-omc1-s15.blu0.hotmail.**com:65.55.116.26> rcpt <a...@nanofate.us >> <mailto:a...@nanofate.us>> : found existing recipient >> CHKUSER accepted rcpt: from <lax...@163.com::> remote >> <m12-72.163.com:mx.mail.163.**split.netease.com:220.181.12.**72> rcpt >> <t...@nanofate.us <mailto:t...@nanofate.us>> : found existing recipient >> >> 1335998054 2012-May-03 02:34 __lxlabs_marker >> 1335998186 2012-May-03 02:36 __lxlabs_marker >> 1335998486 2012-May-03 02:41 __lxlabs_marker >> 1335998786 2012-May-03 02:46 __lxlabs_marker >> 1335999086 2012-May-03 02:51 __lxlabs_marker >> CHKUSER accepted rcpt: from <fdjy...@163.com::> remote >> <:m12-51.163.com:220.181.12.**51> rcpt <t...@nanofate.us >> <mailto:t...@nanofate.us>> : found existing recipient >> >> 1335999386 2012-May-03 02:56 __lxlabs_marker >> 1335999686 2012-May-03 03:01 __lxlabs_marker >> CHKUSER accepted rcpt: from <bph...@gmail.com::> remote >> <:mail-ob0-f175.google.com:209**.85.214.175> rcpt <a...@nanofate.us >> <mailto:a...@nanofate.us>> : found existing recipient >> 1335999987 2012-May-03 03:06 __lxlabs_marker >> CHKUSER accepted rcpt: from <cd_bl...@hotmail.com::> remote >> <:blu0-omc1-s24.blu0.hotmail.**com:65.55.116.35> rcpt <a...@nanofate.us >> <mailto:a...@nanofate.us>> : found existing recipient >> >> Regards. >> >> On Wed, May 2, 2012 at 5:53 PM, Eric Shubert <e...@shubes.net >> <mailto:e...@shubes.net>> wrote: >> >> On 05/02/2012 02:02 PM, Haru wrote: >> >> Hi, >> >> I'm running a website in a vps that has installed Kloxo with >> qmailtoaster. We were having some problems with our mails being >> reported >> as spam, and when I logged into our control panel to check this >> noticed >> that we had thousands of mails in our mail queue (that >> apparently were >> being sent from a test account that I made with a "test" >> password... bad >> idea). I tried deleting the queue from the Kloxo interface, but >> it was >> pointless since I could only delete about 320 mails by step, so >> without >> much thinking I deleted the /var/qmail/queue folder. After that I >> noticed that the mail queue list was indeed empty now, but that I >> couldn't send or receive mails. >> >> >> Ouch. Bad idea all right. >> >> >> I ran this script to rebuild the subdirectories that I deleted by >> mistake >> http://support.godaddy.com/__**help/246/how-do-i-rebuild-__** >> qmails-queue-if-it-is-damaged-**__or-consists-of-a-lot-of-** >> spam-__messages<http://support.godaddy.com/__help/246/how-do-i-rebuild-__qmails-queue-if-it-is-damaged-__or-consists-of-a-lot-of-spam-__messages> >> >> <http://support.godaddy.com/**help/246/how-do-i-rebuild-** >> qmails-queue-if-it-is-damaged-**or-consists-of-a-lot-of-spam-**messages<http://support.godaddy.com/help/246/how-do-i-rebuild-qmails-queue-if-it-is-damaged-or-consists-of-a-lot-of-spam-messages> >> > >> but after restating the server or changing everything to 777 >> nothing >> seems to work. I have been trying to solve this problem >> searching online >> for about 3 hours without any progress, so I'm recurring to this >> mailing >> list as my last hope. >> >> >> The qmailtoaster-plus package has a queue repair tool >> (http://qtp.qmailtoaster.com/_**_trac/wiki/Features#queue___** >> repair.py<http://qtp.qmailtoaster.com/__trac/wiki/Features#queue___repair.py> >> >> <http://qtp.qmailtoaster.com/**trac/wiki/Features#queue_**repair.py<http://qtp.qmailtoaster.com/trac/wiki/Features#queue_repair.py> >> >). >> >> I would give that a try. >> >> I deleted the logs after I deleted our queue, our current >> "smtp.log" >> file is full of lines like this from mail I'm trying to send to >> our website: >> CHKUSER accepted rcpt: from <cd_bl...@hotmail.com::> remote >> <:blu0-omc1-s27.blu0.hotmail._**_com:65.55.116.38> rcpt >> <a...@nanofate.us <mailto:a...@nanofate.us> >> <mailto:a...@nanofate.us <mailto:a...@nanofate.us>>> : found existing >> >> recipient >> >> qmail-smtpd: qq soft reject (qq trouble creating files in queue >> (#4.3.0)): MAILFROM:<cd_bl...@hotmail.com >> <mailto:cd_bl...@hotmail.com> <mailto:cd_bl...@hotmail.com >> >> <mailto:cd_bl...@hotmail.com>>**> >> RCPTTO:a...@nanofate.us <mailto:rcptto%...@nanofate.us**> >> <mailto:rcptto%...@nanofate.us >> <mailto:RCPTTO%253Aa@nanofate.**us<rcptto%2525...@nanofate.us> >> >__> >> >> >> CHKUSER accepted rcpt: from <cd_bl...@hotmail.com::> remote >> <:blu0-omc1-s11.blu0.hotmail._**_com:65.55.116.22> rcpt >> <a...@nanofate.us <mailto:a...@nanofate.us> >> <mailto:a...@nanofate.us <mailto:a...@nanofate.us>>> : found existing >> >> recipient >> >> qmail-dk:[3290]: Dying due to write operation error (disk full?). >> qmail-smtpd: qq soft reject (qq write error or disk full (#4.3.0)): >> MAILFROM:<cd_bl...@hotmail.com <mailto:cd_bl...@hotmail.com> >> <mailto:cd_bl...@hotmail.com <mailto:cd_bl...@hotmail.com>>**> >> RCPTTO:a...@nanofate.us <mailto:rcptto%...@nanofate.us**> >> <mailto:rcptto%...@nanofate.us >> <mailto:RCPTTO%253Aa@nanofate.**us<rcptto%2525...@nanofate.us> >> >__> >> >> >> CHKUSER accepted rcpt: from <cd_bl...@hotmail.com::> remote >> <:blu0-omc1-s23.blu0.hotmail._**_com:65.55.116.34> rcpt >> <a...@nanofate.us <mailto:a...@nanofate.us> >> <mailto:a...@nanofate.us <mailto:a...@nanofate.us>>> : found existing >> >> recipient >> >> qmail-smtpd: qq soft reject (qq trouble creating files in queue >> (#4.3.0)): MAILFROM:<cd_bl...@hotmail.com >> <mailto:cd_bl...@hotmail.com> <mailto:cd_bl...@hotmail.com >> >> <mailto:cd_bl...@hotmail.com>>**> >> RCPTTO:a...@nanofate.us <mailto:rcptto%...@nanofate.us**> >> <mailto:rcptto%...@nanofate.us >> <mailto:RCPTTO%253Aa@nanofate.**us<rcptto%2525...@nanofate.us> >> >__> >> >> >> >> This appears to be normal, given the circumstance (queues are hosed). >> >> >> "mailog" is filled with lines like this, I think they must be >> spam bots >> or something trying to send mail from the account I deleted: >> May 3 00:08:47 nanofate vpopmail[1760]: vchkpw-smtp: vpopmail >> user not >> found t...@nanofate.us:123.162.232._**_100 >> >> May 3 00:08:48 nanofate qmail: 1335989328.011946 alert: cannot >> start: >> unable to open mutex >> May 3 00:10:02 nanofate vpopmail[3171]: vchkpw-smtp: vpopmail >> user not >> found t...@nanofate.us:110.52.6.56 >> May 3 00:10:08 nanofate vpopmail[3188]: vchkpw-smtp: vpopmail >> user not >> found t...@nanofate.us:110.52.6.56 >> May 3 00:10:10 nanofate vpopmail[3198]: vchkpw-smtp: vpopmail >> user not >> found t...@nanofate.us:219.159.197._**_61 >> >> >> >> That appears to be correct. >> >> You might want to consider installing fail2ban. I think there are >> details for doing this on the wiki. >> >> >> Also, apparently we still have plenty of free space in our vps, so >> I >> think that shouldn't be the problem: >> df -h >> Filesystem Size Used Avail Use% Mounted on >> /dev/simfs 20G 6.4G 14G 32% / >> none 512M 4.0K 512M 1% /dev >> /dev/simfs 20G 6.4G 14G 32% >> /var/named/chroot/var/run/dbus >> >> >> Thanks in advance for your time. >> >> >> Certainly. >> >> -- >> -Eric 'shubes' >> >> >> ------------------------------**__----------------------------** >> --__--------------------- >> >> Qmailtoaster is sponsored by Vickers Consulting Group >> (www.vickersconsulting.com >> <http://www.vickersconsulting.**com<http://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 <http://qmailtoaster.com> for the >> >> latest news, updates, and packages. >> To unsubscribe, e-mail: >> qmailtoaster-list-unsubscribe@**__qmailtoaster.com >> >> <mailto:qmailtoaster-list-**unsubscr...@qmailtoaster.com<qmailtoaster-list-unsubscr...@qmailtoaster.com> >> > >> For additional commands, e-mail: >> qmailtoaster-list-help@__qmail**toaster.com <http://qmailtoaster.com> >> >> <mailto:qmailtoaster-list-**h...@qmailtoaster.com<qmailtoaster-list-h...@qmailtoaster.com> >> > >> >> >> >> > > > ------------------------------**------------------------------** > --------------------- > 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-unsubscribe@** > qmailtoaster.com <qmailtoaster-list-unsubscr...@qmailtoaster.com> > For additional commands, e-mail: qmailtoaster-list-help@** > qmailtoaster.com <qmailtoaster-list-h...@qmailtoaster.com> > > >
