ASSP Deluxe for cPanel

Status
Not open for further replies.

manokiss

Well-Known Member
Mar 31, 2002
576
1
318
As i said...you may have to check your settings....you made me work :) just limited one of my test accounts to only 5 emails per hour, then simply created a php file with a mail() function to send an email to one of my email accounts, reloaded that file 6-7 times after 5th i see the error message "Domain mydomain.info has exceeded the max emails per hour (5) allowed. Message discarded." in the exim logs.

Good luck!
 

manokiss

Well-Known Member
Mar 31, 2002
576
1
318
Also tested with a perl script using sendmail and i have the same result---> "Domain mydomain.info has exceeded the max emails per hour (5) allowed. Message discarded."
 

Frank Broughton

Active Member
Feb 8, 2006
32
0
156
Radio_Head, my ASSP install keeps restarting every three hours, since the last update of ASSP deluxe. Where to I look to begin to find a solution?
 

manokiss

Well-Known Member
Mar 31, 2002
576
1
318
Hi Frank,

Probably start looking in the logs at /usr/local/assp/maillog.txt is a good idea.

Good luck!
 

britsenigma

Well-Known Member
Dec 14, 2008
85
0
56
Also got this problem, getting restarts bang on cert hours, happening 3-5 times a day, for a while now, it doesn't effect the service as it restarts very quickly.

But, ASSP, EXIM and CLAMD are all restarting since a recent cpanel/assp update, and I've not had time to look into it as of yet.
 

John W

Member
Aug 24, 2007
16
0
51
Orlando
I don't know if you are aware of this but running spfdomainkey.php as shown ASSP Deluxe post installation steps ,FAQs and support. on version 11.32 fails because domain_keys_installer cannot be found. The changelog states
"/usr/local/cpanel/bin/domain_keys_installer and /usr/local/cpanel/bin/domain_keys_uninstaller were renamed to /usr/local/cpanel/bin/dkim_keys_installer and /usr/local/cpanel/bin/dkim_keys_uninstaller."
 

Radio_Head

Well-Known Member
Verifed Vendor
Feb 15, 2002
2,048
1
343
I am aware of this however thank you to report it . domain_keys will be removed (and possibly replaced with newer DKIM) next days with a new ASSP Deluxe update.
 

manokiss

Well-Known Member
Mar 31, 2002
576
1
318
Hi Radio, wondering if there is any changelog or details about what has been changed between ASSP 1.9.6.5 (0.0.05) and 1.9.7.0 (0.0.02) as i do not see any details in the changelog section in your site.

Thanx in advance!
 

Radio_Head

Well-Known Member
Verifed Vendor
Feb 15, 2002
2,048
1
343
Hello
1.9.7.0 (0.0.02) includes compatibility with any IO::Socket::SSL 1.7x (and it's the main reason of the upgrade) which was crashing all earlier ASSP versions (forcing the usage of older IO::Socket::SSL) . In your ASSP web interface you will find also new feature yesBayesian_local (Bayesian menu).
 

manokiss

Well-Known Member
Mar 31, 2002
576
1
318
Wondering if someone else is having this problem....from a week or so randomly the file securiteinfo.hdb which i guess is part of the sansecurity system in assp is being corrupted causing clamav keep failing until i remove that file and copy the same file from one of the other servers and restart exim.

1- Is someone else having this problem?
2- whch cron of assp do the daily sansecurity dbase update or specifically that file update?

Im thinking if perhaps the cron time it matches with something else that is corrupting the file.

Thanx in advance!
 

Radio_Head

Well-Known Member
Verifed Vendor
Feb 15, 2002
2,048
1
343
Wondering if someone else is having this problem....from a week or so randomly the file securiteinfo.hdb which i guess is part of the sansecurity system in assp is being corrupted causing clamav keep failing until i remove that file and copy the same file from one of the other servers and restart exim.

1- Is someone else having this problem?
2- whch cron of assp do the daily sansecurity dbase update or specifically that file update?

Im thinking if perhaps the cron time it matches with something else that is corrupting the file.

Thanx in advance!
Hello

The problem is not common; the sansecurity dbase (unofficial clamAV signature) is updated using the signatures.php cronjob.
If you do not want use it (sansecurity db) , you may

a) remove/uninstall all current unofficial clamAV signatures in this way
# /usr/local/cpanel/3rdparty/bin/php-cgi /usr/local/assp/deluxe/signatures.php dx=1

b) add sa=0 to your signatures.php cronjob to prevent the usage of sansecurity db
 

manokiss

Well-Known Member
Mar 31, 2002
576
1
318
Thanx Radio!

Well....the idea is not disable it but find the cause of the dbase corruption. Ill start changing the cron time to see if that change anything.

Thanx!
 

Radio_Head

Well-Known Member
Verifed Vendor
Feb 15, 2002
2,048
1
343
Rarely Sanesecurity (and other providers) may upload a corrupted dbase (with one or more rows not accepted by clamAV) . Usually the provider fixes it very soon when it happens. Unlucky clamAV (as of now) has no way to ignore/skip these corrupted rows (I'll post a request in clamAV dev mailing list) .
 

lloyd_tennison

Well-Known Member
Mar 12, 2004
697
1
168
Installed ASSP without a hitch - except for the fact that Mailman stopped working when sending a list. When an individual message is sent, say with the subject "help" the email goes through. When it is released from moderation, or even not moderated, it shows up in the List Archive, the vette log shows that it was held and released, but the smtp log and the smtp-failure log show nothing, and the email never gets sent.

Ran repairmailman, found nothing, checked mm_cfg.py, nothing except SMTPPORT changed (my setup also bypassed other spam filter, but still nothing. I know it is reaching exim, at least sometimes, as the help and subscribe/unsubscribe messages are going through. Nothing in qfiles, but in and out both directories show updated at the same time vette shows released.
 

lloyd_tennison

Well-Known Member
Mar 12, 2004
697
1
168
OK, another weird one that I cannot find in the logs, email was sent to me, but bounced back with

"Diagnostic-code 451 - (4.7.1 Please try again later)". Please check the recipient's email address for typos or unnecessary spaces and resend. Thank you.
 
Last edited:
Status
Not open for further replies.