Re: [qmailtoaster] Re: qtp-newmodel issue RESOLVED

[Digital Instruments]

Thanks.
For sure having a subject marked with SOLVED (or resolved) and explained 
will help a lot, it should always be like that. :)


Il 11/02/2013 21:00, LHTek ha scritto:

Let me clarify that...

at the end of the install it came up with an error in updating a perl 
package


Package perl-NetAddr-IP-4.027-5.el5_6.i386

It came up with a 404 error so I just manually installed (yum install 
perl-NetAddr-IP) it afterwards.


So it wasn't a repo, it was indeed a package. Sorry for the confusion 
there.


ALSO, I found the issue with the ClamvLib error:

Apparently there was change to the clmav files the simscan wasn't 
aware of or wasn't set to handle.


I deleted the /usr/share/clamav/ directory, recreated it and then 
updated the ownership. This fixed the problem.


Hope this helps someone else.

Denny







*From:* Eric Shubert 
*To:* qmailtoaster-list@qmailtoaster.com
*Sent:* Sunday, February 10, 2013 10:38 AM
*Subject:* [qmailtoaster] Re: qtp-newmodel issue

On 02/09/2013 11:35 AM, LHTek wrote:
> It still had an issue with perl repo being installed near the
end but
> that didn't stop the update. so I just manually installed it.

Manually installed what specifically, please? I'm guessing you're
talking about some perl package, as I'm not aware of any perl repo.

-- -Eric 'shubes'

-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

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

Re: [qmailtoaster] Unable to change bounce processing with qmailadmin

[Casey James Price]

  
  
I've
experienced the same issue. Any ideas what might be causing
this?

  
  
  Casey James Price
  Operations/Technical Support
  
  
  www.smileglobal.com
  
  

  On 2/15/13 9:37 PM, Cecil Yother, Jr. wrote:

On
  02/15/2013 05:39 PM, Eric Shubert wrote:
  
  I'm running qmailadmin 1.2.16 (with
vpopmail 5.4.33), and when I click on an account's catchall
button or otherwise attempt to change the catchall status for
the domain, it simply returns a blank page without having
changed anything. The url appears to be properly formatted, and
I see what appears to be a normal message in the apache access
log. I'm running the same version on several hosts, and they all
have this problem.


Anyone else experiencing this? I'm guessing that the latest
upgrade broke something.


The permissions of the files all look ok. I've looked at the C
source code, and it appears that if there's a problem, it should
be showing a message somewhere. I'm wonder if perhaps it's not
getting to that point in the code.


Anyone have any input on this?


Thanks.


  
  Eric,
  
  
  I am experiencing the same problem here.  On the same machine I am
  having trouble with vadddomain
  
  
  CJ