I keep getting emty Emails from SVNSpam on Mac OS X Server

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install SVNSpam on Mac OS X Server (10.6.2)
2. Configure Receipients in svnspam.conf
3. Leave all other configs as they are
3. Commit something

What is the expected output? What do you see instead?
Expected: An email that contains something besides the SVNspam 0.1 link... 
maybe the files committed, some additional data on the files, diffs, etc.
What I see instead: As Subject "[SVN]:" or just "[SVN]", and in the body: 
Just SVNspam 0.1 link, nothing else

What version of the product are you using? On what operating system?
latest Version ... did the checkout today (0.1), and installed it on Mac 
OS X Server v. 10.6.x

Please provide any additional information below.

Original issue reported on code.google.com by wassim.b...@gmail.com on 4 Dec 2009 at 3:55

[GoogleCodeExporter]

Please try the steps in http://code.google.com/p/svnspam/wiki/Troubleshooting

Also examine the /tmp/svnspam.log for clues.

Original comment by m...@foster.cc on 4 Dec 2009 at 11:34

• Changed state: Started

[GoogleCodeExporter]

Original comment by m...@foster.cc on 4 Dec 2009 at 11:35

• Changed state: New
• Added labels: OpSys-OSX, Priority-Low, Type-Other
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

Hi! 

Thank you very much for your hints. 
The svnlook command works fine when I enter it myself in the 
commandline: "svnlook /path/to/repos". This outputs the diff correctly. 
However, the svnspam.log file only contains "svnlook: Expected FS format '2'; 
found 
format '4'". This message appears once for each commit. 
I really don't know what the problem might be. 

Kind regards

Original comment by wassim.b...@gmail.com on 6 Dec 2009 at 6:38

[GoogleCodeExporter]

Please heck the responses at 
http://mikemason.ca/blog/2008/06/subversion-15-is-ready/
to see if it's a similar problem/solution e.g. differing versions.

Original comment by m...@foster.cc on 6 Dec 2009 at 6:43

[GoogleCodeExporter]

Ok, actually it was kind of the same problem.
Some heroes installed another svn version to another location. Just had to 
delete 
that version and everything worked. Thank you very much!

Original comment by wassim.b...@gmail.com on 8 Dec 2009 at 9:56

[GoogleCodeExporter]

Cool. Glad to hear it is solved.

Original comment by m...@foster.cc on 9 Dec 2009 at 2:48

• Changed state: Done