Feb 052015

1. Implement method to shut off wi-fi daily during sleeping hours.
 2. Create scripts to toggle power in APC master switch.
 3. Adapt scripts to webpage that can be accessed from mobile device with clickable controls.
 4. Learn to code.

- Posted using BlogPress from my iPhone

Location:Cottonwood St,Yarmouth Port,United States

 Posted by at 8:48 pm
Jan 222015

I’ve had to do a fair bit of updating Crystal Report syntax as of late.  As I had been told by the software integrators four years ago, Crystal is something you just have to fiddle with once you get past the basics.  Once you’ve figured out which tables your data is in, the rest is a sequence of trial and error until you become adept at knowing which tables to select and what formulas to use.  Most of the reports I’ve had to design thus far query invoices for sales figures.  Due to the nature in which the query is made, duplicate records are often returned.

While Google says that duplicate records can be filtered out by using section settings with a suppression formula that looks something like this:

I found that while the detail seemed to work as expected, a cross-tab report would often include data that should have been suppressed.  Also, depending on the nature and purpose of the report, the detail might exclude the first record processed in the query.

In writing a report that queried sales data from invoices based the preselected criteria of a particular set of items on the invoice, duplicate records had to be excluded where more than one item could appear on the same invoice and return a duplicate record.

After several variations of the suppression formula, I opted not to use one at all. By filtering the duplicates in the formula field itself, the problem of duplicates was solved.  The following syntax yielded the results I wanted, and returned accurate data for use in the cross-tab as well.


Dec 132014

I’ve been filtering my domain mail through a local mail server for a bit. This has cut down on the amount of spam that 1&1 forwards unfiltered, and ensures that I can send outbound mail when their servers are blacklisted.

I’ve been working with tweaking spamassassin performance for aggressive filtering for some time now. Due to the OSX server configuration (10.8 and 10.9), I’ve made most adjustments with amavisd (conf file). Some rules were not effective so I made further adjustments by altering the postfix queue to do additional header checks and redirect filtered messages to a catch all mailbox.

Later, I added blacklist and whitelist files to spamassassin which greatly improved frequency of false positives on inbound mail.

On my personal mail filter, I was having difficulty (again) getting amavisd to adjust spamassassin points for a specific alias that redirects to my mailbox.

After a few attempts, I was able to get the desired result by creating a custom spamassassin rule that is parsed during filtering. Along the way, I learned not to patch amavisd on the Apple specific builds. I’m hoping to have some time over the Christmas break to compare the source code of Apples configuration versus the corresponding open source build.