Archive for September 27th, 2008

I recently upgraded a customer management software called ClientExec from a very old version (2.4.9__2.5beta4) to the latest stable version (ClientExec 3.1.4).  It had been a long time since the administration type settings had been updated but it was time to clean things up. One area lets you manage billing types which I was about to attempt. You can either delete or edit current entries or add a new entry. First I attempted to add a new entry and was greeted with the error below.

[quickcode:billingtype]
An error has occurred with the given operation

Type: User Error (256)
Description: QUERY: INSERT INTO billingtype (id, name, description, detail) VALUES(’2147483648′,’Test’,'Test’,'Test’) – ERROR: Duplicate entry ’2147483647′ for key 1
Request: POST /client/index.php?fuse=billing&action=AddBillingType
Script: client/newedge/classes/NE_Mysql.php
Line Number: 154
Stack:
client/modules/billing/models/BillingType.php (50) : ne_mysql::query
client/modules/billing/actions/AddBillingType.php (16) : billingtype::update
client/newedge/classes/NE_Controller.php (200) : addbillingtype::dispatch
client/newedge/front.php (74) : ne_controller::processaction
client/index.php (4) : unknown
[/quickcode]

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , ,

Comments No Comments »

I have a couple people who write articles from time to time sand after installing WP Block Admin they were unable to get to wp-admin anymore. Since we are only using three user levels on this site which are Admin, Author, and Subscriber. On install WP Block Admin is set to only allow Admin and Editor access to /wp-admin so you have to modify wp-content/plugins/wp-block-admin/wp-block-admin.php. Find the line like this:
[quickcode:noclick]
$wpba_required_capability = ‘edit_others_posts’;
[/quickcode]

Change it to this:

Read the rest of this entry »

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , , , ,

Comments 1 Comment »

This error was displayed in Apache’s error.log after an ISPConfig installation. Initially the problem was thought to be with perl’s DATE::FORMAT however that ended up not being the case. Somehow the httpd.conf file in /etc/httpd/conf/ got corrupted on the LogFormat line as shown below.

[quickcode:corrupt-httpd.conf]
LogFormat “%v||||%b|||||%h %l %u %t \”%r\” %>s %b \”%{Referer}i\” \”%{User-Agent}i\”" combined_ispconfig
CustomLog “|/root/ispconfig/cronolog –symlink=/var/log/httpd/ispconfig_access_log /var/log/httpd/ispconfig_access_log_%Y_%m_%d” combined_ispconfig
[/quickcode]

It should look like this:

[quickcode:httpd.conf]
LogFormat “%v %b %h %l %u %t \”%r\” %>s %b \”%{Referer}i\” \”%{User-Agent}i\”" combined_ispconfig
CustomLog “|/root/ispconfig/cronolog –symlink=/var/log/httpd/ispconfig_access_log /var/log/httpd/ispconfig_access_log_%Y_%m_%d” combined_ispconfig
[/quickcode]

So if you are seeing a similar error the problem is more than likely with the LogFormat statement in httpd.conf. Also make sure your vlogger is installed properly by typing “which vlogger”.

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , ,

Comments No Comments »

This article was written to create an easy step to add more SPAM protection to ISPConfig when you are running postfix. This not only will cut down on SPAM but it will also cut down on load by not sending as much SPAM to spamassassin. Below are some SPAM protection additions that can be made to postfix’s main configuration file and will stop most SPAM from even reaching spamassassin. The reject_rbl_client command is used to add SPAM blacklists for postfix to check against. You can research other blacklists and add them if you like.

Add the below to /etc/postfix/main.cf.
[quickcode:main.cf]
# SPAM Prevention Below
# Please make sure to keep blacklists up to date.
smtpd_helo_required = yes
non_fqdn_reject_code = 554
relay_domains_reject_code = 554
disable_vrfy_command = yes
strict_rfc821_envelopes = yes
invalid_hostname_reject_code = 554
multi_recipient_bounce_reject_code = 554
unknown_client_reject_code = 554
unknown_sender_reject_code = 554
unknown_address_reject_code = 554
unknown_hostname_reject_code = 554
unknown_virtual_alias_reject_code = 554
unknown_virtual_mailbox_reject_code = 554
unknown_local_recipient_reject_code = 554
unknown_relay_recipient_reject_code = 554
unverified_recipient_reject_code = 554
unverified_sender_reject_code = 554

smtpd_recipient_restrictions =
reject_invalid_hostname,
reject_unknown_recipient_domain,
reject_unauth_pipelining,
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_rbl_client multi.uribl.com,
reject_rbl_client zen.spamhaus.org,
reject_rbl_client dnsbl.njabl.org,
reject_rbl_client whois.rfc-ignorant.org,
reject_rbl_client combined.rbl.msrbl.net,
permit
[/quickcode]

Restart postfix by: /etc/init.d/postfix restart

You now have extra SPAM protection for postfix and your ISPConfig installation.

DeliciousStumbleUponDiggTwitterFacebookRedditLinkedInEmail
Tags: , , , , , ,

Comments 5 Comments »