Re: [qmailtoaster] Re: Mdadm Reinstall?

[Duncan Sterling]

Thanks Eric. I'll go ahead and reinstall the package and open a ticket.

--Duncan

Eric Shubert wrote:

Duncan Sterling wrote:

Greetings All,

I'd forgotten that the install script removes the mdadm package 
(which is fine if you don't need it, but we run software RAID).


I assume it's safe to add it back in once the scripts are done?

TIA,

--Duncan

- 



Sure, afaik. The install script probably shouldn't remove that 
package. Will you open a ticket on that?


It's best to run QMT on raid of some sort. I prefer soft raid-1 myself.




-
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

[qmailtoaster] Mdadm Reinstall?

[Duncan Sterling]

Greetings All,

I'd forgotten that the install script removes the mdadm package (which 
is fine if you don't need it, but we run software RAID).


I assume it's safe to add it back in once the scripts are done?

TIA,

--Duncan

-
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: Clamav Build Error?

[Duncan Sterling]

That did it--thanks Eric!

--Duncan

Eric Shubert wrote:

Duncan Sterling wrote:

Greetings,

Hopefully not re-running over old ground here--when I run 
qtp-newmodel on my (fully up to date) CentOS 5 toaster, it breaks at 
building the clamav package:


---

Building clamav-toaster-0.96.0-1.3.35 ...
error: unpacking of archive failed on file 
/usr/src/redhat/SOURCES/clamav-0.96.0.tar.bz2;4bcf89d1: cpio: read
error: 
/usr/src/qtp-upgrade/SRPMS/clamav-toaster-0.96.0-1.3.35.src.rpm 
cannot be installed
Installing 
/usr/src/qtp-upgrade/SRPMS/clamav-toaster-0.96.0-1.3.35.src.rpm



qtp-build-rpms - see 
/mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log for more 
details


Build failed, Exiting.



Any suggested fix(es)?

Thanks in advance,

--Duncan



Corrupt download. Remove the file from /usr/src/qtp-upgrade/SRPMS/, 
and try again. Use a fresh sandbox to be on the safe side.





-
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

[qmailtoaster] Clamav Build Error?

[Duncan Sterling]

Greetings,

Hopefully not re-running over old ground here--when I run qtp-newmodel 
on my (fully up to date) CentOS 5 toaster, it breaks at building the 
clamav package:


---

Building clamav-toaster-0.96.0-1.3.35 ...
error: unpacking of archive failed on file 
/usr/src/redhat/SOURCES/clamav-0.96.0.tar.bz2;4bcf89d1: cpio: read
error: /usr/src/qtp-upgrade/SRPMS/clamav-toaster-0.96.0-1.3.35.src.rpm 
cannot be installed

Installing /usr/src/qtp-upgrade/SRPMS/clamav-toaster-0.96.0-1.3.35.src.rpm


qtp-build-rpms - see 
/mnt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log for more details


Build failed, Exiting.



Any suggested fix(es)?

Thanks in advance,

--Duncan

-
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] CentOS 4 --> CentOS 5 Upgrade--Will The Toaster Survive?

[Duncan Sterling]

Thanks for the reply.

So this is a long shot, but I wonder: If I upgrade the OS, then do a 
QTP-newmodel, might I be able to "sneak" around my OS upgrade problems 
that way (since newmodel rebuilds all the packages)?


--Duncan

Lucian Cristian wrote:
if I remember I had problems because of mysql version change, and I 
had to recompile the packages


regards
Lucian

Duncan Sterling wrote:

Greetings All,

I've got to upgrade a CentOS 4 server (with a mostly up to date 
toaster installation) to CentOS 5.


How likely is the existing toaster install to survive the upgrade 
intact?


TIA,

--Duncan

- 

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







__ Information from ESET NOD32 Antivirus, version of virus 
signature database 4507 (20091014) __


The message was checked by ESET NOD32 Antivirus.

http://www.eset.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-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
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-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] CentOS 4 --> CentOS 5 Upgrade--Will The Toaster Survive?

[Duncan Sterling]

Greetings All,

I've got to upgrade a CentOS 4 server (with a mostly up to date toaster 
installation) to CentOS 5.


How likely is the existing toaster install to survive the upgrade intact?

TIA,

--Duncan

-
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] Invalid Message Content Error With .DOC Attachment?

[Duncan Sterling]

Jake Vickers wrote:

Duncan Sterling wrote:

Jake Vickers wrote:

Duncan Sterling wrote:

Greetings All,

A client is complaining that all of a sudden, a regular mailing he 
receives with a .doc (M$ Word attachment) is bouncing:


> >>> DATA
> <<< 554 invalid message content  (#5.3.2)
> 554 5.0.0 Service unavailable

Any suggestions as to what my trigger this?

I found references to PDFs having this problem via googling/etc, 
but not word documents...




Look in your spam logs (/var/log/qmail/spamd) and your clamav log 
(/var/log/qmail/clamd) and see what is causing it to bounce.
Are you running an older version that still has the badmimetypes and 
badloadertypes that may be catching it?
Hmm. No apparent trace in either log. Yes, I've still got 
badmimetype/loadertypes.


The strange thing is, our clients regularly receive .doc and .pdf 
attachments without issue...


Right, but those signatures you see there get matched by any part of 
the message, including the MIME. Try commenting them all out, cdb'ing, 
and seeing if it will allow that file then. I used to get false 
positives with PDF files a long time ago. Check the archives and 
you'll see a thread on it.


That fixed it, many thanks Jake.

--Duncan


-
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] Invalid Message Content Error With .DOC Attachment?

[Duncan Sterling]

Thanks--only blocking .src, .bat, and .pif there...

--Duncan

Anil Aliyan wrote:

and also check your /var/qmail/control/simcontrolfile.

Regards,

Anil Aliyan

- Original Message - From: "Jake Vickers" 
To: 
Sent: Wednesday, May 06, 2009 5:57 AM
Subject: Re: [qmailtoaster] Invalid Message Content Error With .DOC 
Attachment?




Duncan Sterling wrote:

Greetings All,

A client is complaining that all of a sudden, a regular mailing he 
receives with a .doc (M$ Word attachment) is bouncing:


> >>> DATA
> <<< 554 invalid message content  (#5.3.2)
> 554 5.0.0 Service unavailable

Any suggestions as to what my trigger this?

I found references to PDFs having this problem via googling/etc, but 
not word documents...




Look in your spam logs (/var/log/qmail/spamd) and your clamav log 
(/var/log/qmail/clamd) and see what is causing it to bounce.
Are you running an older version that still has the badmimetypes and 
badloadertypes that may be catching it?



- 


Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours 
today!


Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)


Please visit qmailtoaster.com for the latest news, updates, and 
packages.



 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com







- 


Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)


Please visit qmailtoaster.com for the latest news, updates, and 
packages.



 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-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: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com

Re: [qmailtoaster] Invalid Message Content Error With .DOC Attachment?

[Duncan Sterling]

Jake Vickers wrote:

Duncan Sterling wrote:

Greetings All,

A client is complaining that all of a sudden, a regular mailing he 
receives with a .doc (M$ Word attachment) is bouncing:


> >>> DATA
> <<< 554 invalid message content  (#5.3.2)
> 554 5.0.0 Service unavailable

Any suggestions as to what my trigger this?

I found references to PDFs having this problem via googling/etc, but 
not word documents...




Look in your spam logs (/var/log/qmail/spamd) and your clamav log 
(/var/log/qmail/clamd) and see what is causing it to bounce.
Are you running an older version that still has the badmimetypes and 
badloadertypes that may be catching it?
Hmm. No apparent trace in either log. Yes, I've still got 
badmimetype/loadertypes.


The strange thing is, our clients regularly receive .doc and .pdf 
attachments without issue...


--Duncan

-
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: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com

[qmailtoaster] Invalid Message Content Error With .DOC Attachment?

[Duncan Sterling]

Greetings All,

A client is complaining that all of a sudden, a regular mailing he 
receives with a .doc (M$ Word attachment) is bouncing:


> >>> DATA
> <<< 554 invalid message content  (#5.3.2)
> 554 5.0.0 Service unavailable

Any suggestions as to what my trigger this?

I found references to PDFs having this problem via googling/etc, but not 
word documents...


TIA,

--Duncan

-
Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

Please visit qmailtoaster.com for the latest news, updates, and packages.


 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com

Re: [qmailtoaster] Sandbox Upgrade Fail

[Duncan Sterling]

Eric Shubert wrote:

Duncan Sterling wrote:

Jake Vickers wrote:

Duncan Sterling wrote:

Greetings All,

I've just attempted to run qtp-newmodel on a CentOS 5.3 box.

All appeared to be going well until the build of 
'spamassassin-toaster':


On my console, I got:

-

Building spamassassin-toaster-3.2.5-1.3.15 ...
Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15
qtp-build-rpms - see 
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

Build failed, Exiting.


-

And from the build-recent.log, I got:

-

Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
error: Failed dependencies:
   perl(Archive::Tar) >= 1.23 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(HTTP::Date) is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(IO::Zlib) >= 1.04 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(LWP::UserAgent) is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686


-

Now I can build and install the missing perl modules separately, 
either by hand or via the CPAN system. But I seem to remember 
seeing something about CPAN built/installed modules creating a 
problem for the toaster.


Is there a preferred approach to resolving this dependency error?



What version of QTP are you running? There was a new version 
released a couple days ago that installs the perl packages using yum 
in a new way.


I was definitely a version back. I'll try the new QTP newmodel and 
see if that resolves the perl dependencies issue.


Thanks,

--Duncan




Let us know either way, as it should work nicely now, and I'll want to 
fix it if it still has a problem.




It only ran into one further problem--it failed on a dependency for 
ncurses-devel. I installed that via yum and then the build and upgrade 
completed successfully.


Thanks to both you and Jake for your help...

--Duncan

-
Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

Please visit qmailtoaster.com for the latest news, updates, and packages.


 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com

Re: [qmailtoaster] Sandbox Upgrade Fail

[Duncan Sterling]

Jake Vickers wrote:

Duncan Sterling wrote:

Greetings All,

I've just attempted to run qtp-newmodel on a CentOS 5.3 box.

All appeared to be going well until the build of 'spamassassin-toaster':

On my console, I got:

-

Building spamassassin-toaster-3.2.5-1.3.15 ...
Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15
qtp-build-rpms - see 
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

Build failed, Exiting.


-

And from the build-recent.log, I got:

-

Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
error: Failed dependencies:
   perl(Archive::Tar) >= 1.23 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(HTTP::Date) is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(IO::Zlib) >= 1.04 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(LWP::UserAgent) is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686


-

Now I can build and install the missing perl modules separately, 
either by hand or via the CPAN system. But I seem to remember seeing 
something about CPAN built/installed modules creating a problem for 
the toaster.


Is there a preferred approach to resolving this dependency error?



What version of QTP are you running? There was a new version released 
a couple days ago that installs the perl packages using yum in a new way.


I was definitely a version back. I'll try the new QTP newmodel and see 
if that resolves the perl dependencies issue.


Thanks,

--Duncan
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.285 / Virus Database: 270.11.47/2047 - Release Date: 04/08/09 
05:53:00

-
 Managed Qmailtoaster servers are now available
   Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

 Please visit qmailtoaster.com for the latest news, updates, and packages.


  To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: testing-h...@qmailtoaster.com

Re: [qmailtoaster] Sandbox Upgrade Fail

[Duncan Sterling]

Jake Vickers wrote:

Duncan Sterling wrote:

Greetings All,

I've just attempted to run qtp-newmodel on a CentOS 5.3 box.

All appeared to be going well until the build of 'spamassassin-toaster':

On my console, I got:

-

Building spamassassin-toaster-3.2.5-1.3.15 ...
Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15
qtp-build-rpms - see 
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

Build failed, Exiting.


-

And from the build-recent.log, I got:

-

Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
error: Failed dependencies:
   perl(Archive::Tar) >= 1.23 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(HTTP::Date) is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(IO::Zlib) >= 1.04 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(LWP::UserAgent) is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686


-

Now I can build and install the missing perl modules separately, 
either by hand or via the CPAN system. But I seem to remember seeing 
something about CPAN built/installed modules creating a problem for 
the toaster.


Is there a preferred approach to resolving this dependency error?



What version of QTP are you running? There was a new version released 
a couple days ago that installs the perl packages using yum in a new way.


qmailtoaster-plus-0.2.14-1.3.18

--Duncan
No virus found in this outgoing message.
Checked by AVG - www.avg.com
Version: 8.5.285 / Virus Database: 270.11.47/2047 - Release Date: 04/08/09 
05:53:00

-
 Managed Qmailtoaster servers are now available
   Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

 Please visit qmailtoaster.com for the latest news, updates, and packages.


  To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: testing-h...@qmailtoaster.com

Re: [qmailtoaster] Temporarily Hand Off/Ignore All Email For One Forward?

[Duncan Sterling]

Thanks for your reply, Jake.

We figured out what the problem was. One our less clueful users had done 
two things to make a bit of a mess:


1) Set up a forward that was directed to both a remote address *and* 
back to the forward itself(!)


and

2) Set up the same account as a 'catch-all' account.

Once these two conditions were corrected, the flood of SPAM stopped, we 
cleaned out the queue and all is well again.


Anway, thanks again for your help.

--Duncan


Jake Vickers wrote:

Duncan Sterling wrote:

Greetings All,

In the past 24 hours, I've had to fend off somewhere north of 50,000 
emails to one single forward in one of our vdomains.


In this vdomain are 4 regular accounts, several of which forward to a 
forward in the same vdomain, which in turn directs mail to another 
SMTP server. Most of the SPAM coming in is addressed to this single 
forward.



So, the questions is, other than the obvious move of disabling the 
forward until things quiet down, or smptforwarding the entire vdomain 
to the client's SMPT server, is it possible to selectively  
ignore/forward  only the  inbound emails addressed to the single 
troublesome forward in this vdomain?


TIA,



You could probably use badmailto and filter what you want that way. 
Just put the address you do not want to accept mail for in the file, 
if that's what you're asking. Otherwise I may be misinterpreting what 
you're trying to accomplish.








- 


Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)


Please visit qmailtoaster.com for the latest news, updates, and 
packages.



 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com




-
Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

Please visit qmailtoaster.com for the latest news, updates, and packages.


 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com

[qmailtoaster] Sandbox Upgrade Fail

[Duncan Sterling]

Greetings All,

I've just attempted to run qtp-newmodel on a CentOS 5.3 box.

All appeared to be going well until the build of 'spamassassin-toaster':

On my console, I got:

-

Building spamassassin-toaster-3.2.5-1.3.15 ...
Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
qtp-build-rpms - rpm -Uvh failed for spamassassin-toaster-3.2.5-1.3.15
qtp-build-rpms - see 
/opt/qtp-sandbox/usr/src/qtp-upgrade/log/build-recent.log

Build failed, Exiting.


-

And from the build-recent.log, I got:

-

Installing spamassassin-toaster-3.2.5-1.3.15 in the sandbox ...
error: Failed dependencies:
   perl(Archive::Tar) >= 1.23 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686

   perl(HTTP::Date) is needed by spamassassin-toaster-3.2.5-1.3.15.i686
   perl(IO::Zlib) >= 1.04 is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686
   perl(LWP::UserAgent) is needed by 
spamassassin-toaster-3.2.5-1.3.15.i686


-

Now I can build and install the missing perl modules separately, either 
by hand or via the CPAN system. But I seem to remember seeing something 
about CPAN built/installed modules creating a problem for the toaster.


Is there a preferred approach to resolving this dependency error?

TIA,

--Duncan

-
Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

Please visit qmailtoaster.com for the latest news, updates, and packages.


 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com

[qmailtoaster] Temporarily Hand Off/Ignore All Email For One Forward?

[Duncan Sterling]

Greetings All,

In the past 24 hours, I've had to fend off somewhere north of 50,000 
emails to one single forward in one of our vdomains.


In this vdomain are 4 regular accounts, several of which forward to a 
forward in the same vdomain, which in turn directs mail to another SMTP 
server. Most of the SPAM coming in is addressed to this single forward.



So, the questions is, other than the obvious move of disabling the 
forward until things quiet down, or smptforwarding the entire vdomain to 
the client's SMPT server, is it possible to selectively  ignore/forward  
only the  inbound emails addressed to the single troublesome forward in 
this vdomain?


TIA,

--Duncan

-
Managed Qmailtoaster servers are now available
  Visit http://qmailtoaster.com/QMTManaged.html to order yours today!

Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)

Please visit qmailtoaster.com for the latest news, updates, and packages.


 To unsubscribe, e-mail: testing-unsubscr...@qmailtoaster.com
For additional commands, e-mail: testing-h...@qmailtoaster.com

Re: [qmailtoaster] Two Toasters And A Backup Script?

[Duncan Sterling]

Jake Vickers wrote:

Duncan Sterling wrote:

Greetings All,

Quick question: in the interest of redundancy and quick disaster 
recovery, would it not make sense while running a production toaster to:


1) Build an identically configured backup toaster

2) Run (Jakes?) backup script daily on the production toaster, 
backing it up to the the backup toaster


Thereby allowing near instant recovery in the event of HW/sotware 
failure on the production box?




In the past, for ISPs, I've used some type of shared filesystem 
(usually NFS using 2 servers running DRBD and heartbeat) and then 
configured 2+ Qmail systems to act as front ends using the shared 
backend filesystem (most of the config files, and the mail store). 
Then you have 2 servers that you can DNS-round-robin, and it's trivial 
to plug more in as load increases.
Although what you're suggesting WOULD work. The biggest things is 
always sharing the mysql DB, but there's several ways to do that 
depending on your conditions.

Thanks for your reply, Jake.

I was thinking that perhaps the backup box's mysql could be slaved to 
the primary's as one possible solution?


--Duncan

-
QmailToaster hosted by: VR Hosted <http://www.vr.org>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[qmailtoaster] Two Toasters And A Backup Script?

[Duncan Sterling]

Greetings All,

Quick question: in the interest of redundancy and quick disaster 
recovery, would it not make sense while running a production toaster to:


1) Build an identically configured backup toaster

2) Run (Jakes?) backup script daily on the production toaster, backing 
it up to the the backup toaster


Thereby allowing near instant recovery in the event of HW/sotware 
failure on the production box?


Thoughts?

TIA,

--Duncan

-
QmailToaster hosted by: VR Hosted 
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]