Hi Jules and Michael,

There was an update today morning when I came in (not sure if it was released prior). I have been able to install it and works fine. Contact me and let me know if you are still having issues.

Jules: Should you need to extend your trial, let me know by email.

Thanks!
Sean M

I'm sorry to say that I'm now very confused.....

I had a version of DD (let's call it Iteration 1) which was installed into my System Preferences.

That was replaced by another version (called Iteration 2 ) which was an application and came with instructions to manually delete the Iteration 1 preference files.

Following the most recent response here I downloaded the most recent version of DD from your site (let's call this one Iteration 3). This came with an installer which (wait for it), installed itself into the System Preferences again.

How confusing; did it remove Iteration 2?

In fact; No.

And when I try to run Iteration 2 the application advises me there's an update (beta6?) which it then downloads (Iteration 4) and once restarted still claims that the database version is too low.

So I now have both the 'Preferences version and the application version and no idea (and less confidence) that I have any idea what is going on and whether any of this good for the overall health of my OS installation.

Suggestions?

JiF

Hi Jules,

You have to uninstall the old preference pane to run the new dedicated app (if you installed that to begin with):
1) Go to System Preferences -> Daylite Delivery and *stop* the (delivery) server
2) Go to HD -> Library -> PreferencePanes and delete Daylite Delivery.prefPane
3) Go to HD -> Library -> LaunchDaemons and delete daylite.plist

Once you download the new app, put it in your /Applications folder and add it to you launch items (Delivery menu -> Starts at Launch is a convenience)

Okay, stopped the service, removed the three root items (the two files you mentioned, plus a com.marketcircle preference) and the ~/library/preferences preference too.

Restarted the DD application and having provided an email address again (deleted along with the preference) I'm told my DB version is "..too low.." again.

So, no change there then.

I even downloaded the installer and ran it to solely update the database engine.

So who knows; permissions, preferences, an Openbase issue; I give up.

JiF

Ahh.. The reason for that is you need the newer version of Daylite (I didn't realize this). You can get Daylite 3.7.3 by signing up to the Daylite Beta LIst.

April 17th was is the latest build (Beta 3 build 1574).

Hope this helps.

Aly D.

...then I was right to give up...

Actually we're relaxed those requirements with Beta 9 (come out late yesterday).

Grab the latest beta by going to Delivery -> Menu -> Updates -> Check for Updates...

(you can download, install and restart in one step).

I'm afraid to say that with the tendency of developers to "publish and be damned" (a beta a day keeps the users at bay) my attitude has become one of "..if at first I don't succeed, give up".

This beta at least runs, which is a start. Spoke too soon....

I can send the test message. When I ask it for a Users report (whatever that is) I get a cryptic message (a sub-routine has run successfully?) but no report. I'm assuming that because it is at the top of the reports list the Users Report will always generate a value and hence always test the system?

Suggestions?

This message has been edited. Last edited by: Jules,

Make sure you have reports scheduled in Daylite (go to the Preferences -> Daylite Delivery). For each schedule, make sure you have a valid email address.

The logs (DeliveryCore.log) will tell you which report was send to which email address (and at what time).

///////////CORE LOG////////////

2008-04-23 23:52:17 +0200 ====== Daylite Delivery, Copyright (C) Marketcircle Inc. All Rights Reserved
2008-04-23 23:52:17 +0200 ====== Licenses: 5 Database: JPSWork SMTP Server: smtp.xxxxxx.fr
2008-04-23 23:52:22 +0200 ERROR: mail delivery to:xxxxxxx@mac.com subject:Users failed with exception:
Traceback (most recent call last):
File "/Applications/Daylite Delivery.app/Contents/Frameworks/MCMailer.framework/Resources/MCMailer.py", line 67, in <module>
smtp.sendmail(strFrom, strTo, message.getvalue())
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/smtplib.py", line 695, in sendmail
smtplib.SMTPRecipientsRefused: {'xxxxxxx@mac.com': (554, '<xxxxxxx@mac.com>: Relay access denied')}

2008-04-23 23:52:22 +0200 Incomplete Delivery: Users.dlreport
2008-04-23 23:52:22 +0200 Addressed Yet To Receive Report: xxxxxxx@mac.com

///////////CORE LOG////////////

The email address is fine and the smtp server is my ISP and needs no user-name/password. The rest of it is crypto-speak.

Is it possible that I need my ISP "dislikes" bulk-mailers; maybe I need to route traffic through DirectMail's bulk-friendly smtp server?

Tkx/JiF

That's because, according to the server, you are pretending to be someone else. You are using your .fr server to relay a message from a someone at mac.com.

That's a common technique spammer use, so servers disallow that. Use your .mac smtp thing or use your .fr email address.

So, when we set up DD we offer to it an smtp server to relay email and an email address to send email FROM.

When we test DD it sends an email from the FROM address, via the smtp relay, to the FROM address. When I send Test Email from my .Mac address to my .Mac address, via my ISP's smtp server that works; likewise when I send FROM my ISP address to my ISP address via my ISP's smtp server that works too. [hint, this appears to be testing something different and the self congratulatory email message is therefore fallacious].

However when DD attempts to send a Report from my .Mac address to my .Mac address via my ISP's smtp server it does NOT work. The only difference between these two scenarios is how DD handles the FROM and TOO addresses for the test, versus how DD handles the FROM and TO addresses for reports.

Similarly when I try to send a Report from my ISP's email address to my .Mac address that too fails (see CORE LOG).

Therefore I cannot agree with your last reply. Nor with your observation about spam protection; my ISP does not allow the use of other smtp (even secure smtp traffic) so ALL outgoing email irrespective of the sender address is carried via his relays. My guess is that the challenge lies with sendmail()

///////////////CORE LOG//////////////////

2008-04-24 08:23:26 +0200 ====== Daylite Delivery, Copyright (C) Marketcircle Inc. All Rights Reserved
2008-04-24 08:23:26 +0200 ====== Licenses: 5 Database: JPSWork SMTP Server: smtp.xxxxxxxxx.fr
2008-04-24 08:23:33 +0200 ERROR: mail delivery to:xxxxxxxxx@mac.com subject:Users failed with exception:
Traceback (most recent call last):
File "/Applications/Daylite Delivery.app/Contents/Frameworks/MCMailer.framework/Resources/MCMailer.py", line 67, in <module>
smtp.sendmail(strFrom, strTo, message.getvalue())
File "/System/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/smtplib.py", line 695, in sendmail
smtplib.SMTPRecipientsRefused: {'xxxxxxxxx@mac.com': (554, '<xxxxxxxxx@mac.com>: Relay access denied')}

2008-04-24 08:23:33 +0200 Incomplete Delivery: Users.dlreport
2008-04-24 08:23:33 +0200 Addressed Yet To Receive Report: xxxxxxxxx@mac.com

///////////////CORE LOG//////////////////

This message has been edited. Last edited by: Jules,

I'm a little confused from your last message. Are you saying that when you send a test email it works but when you send a report it does *not* work?

Correct.

"This email was sent to you from Daylite Delivery as a test. If you received it in your inbox, then it would seem that you have correctly set your mail server settings.

Congratulations."

We added the ability to use Apple Mail as a delivery method. There are a couple cases where we just can't explain why it is not working. In those cases, one could just use Apple Mail.

We've posted a new beta. You can get it by going to the Main Menu -> Daylite Delivery -> Updates -> Check for Updates...

Give that a try and let me know.
Thx.