Ok, I found the answer to this.

I expected that Tiny itself was sending the initial emails to the sender and 
the  watchers, but now I have found that it is the mail-gateway.py and that it 
was simply a case of my email gateway not allowing relay for localhost.

As an aside, I have noticed that the Object Relationship Model processing seems 
a bit more draconian with 4.2.0.

The "name" field in the crm table is char var(64) and the crm.py module has 
this hardcoded in several places, and yet both postgres and the Tinyclient will 
accept longer length names.  I thought this was a hard restriction in postgres 
even for varying fields.

However, if the mail-gateway tries to create a case from an email with a 
subject line greater than 64 chars, it excepts.  I have changed this limit to 
128 wherever I can find it in crm.py and the db.  I don't really get why 
tinyerp-server doesn't get its field lengths from the database tables 
themselves, rather than having them hardcoded in the application - ultimately 
that is where they need to end up, and it would make maintenance far simpler.

------------------------
ServWise Advanced Web Hosting - Better, Faster, Smarter 
(http://www.servwise.com)





_______________________________________________
Tinyerp-users mailing list
http://tiny.be/mailman/listinfo/tinyerp-users

Reply via email to