Configuration FAQ

• How can I set up my system to allow access from the internet?
• Why does po not send any mails?
• How can I customize DynField Permissions?
• Whats the meaning of 'Database will allow full access to all data...'   

­How can I set up my system to allow access from the internet? ­

Please see: Configuration steps to allow external internet access to a po VM

Why does ]po[ not send any mails?­

C­heck ]po[ mail queue

OpenACS manages its own mail queue. From table  acs_mail_queue_outgoing mails will be forwarded to a local MTA. Check its content to see if mail will be sent out.

C­heck system mail queue

Run

         mailq -v

If there are still mail messages pending, this command should show you why. For example, you might see something like "Deferred: Connection refused by <some SMTP server>"
[Terrance Crow]

Check if you local MTA is running and accepting mail

]po[ uses by default the postfix  MTA. To check if postfix is running use:

ps waux | grep postfix

Check log file

Have a look at the log file (default location: var/log/mail)  

Check local DNS server for MX Record

In case mail is only send out to "external" recipients, but not to local recipients, check the MX record of your local DNS server.

Check your resolv.conf

Check your DNS server entries in /etc/resolv.conf.  Please check that the DNS servers are working. Be aware that mydns is not able to resolve external domains, so you will have to enter a DNS server that is capable of resolving external domains too.
[ref]

Check if your ISP requires valid bounce addresses

Some ISP (and everyday more) do exhaustive validation checks before accepting email. In some case providers check for a valid bounce address.
In OpenACS package acs-mail-­lite builds random system email addresses to manage bounces instead of real addresses. Validation checks performed by ISP's would fail. 

If your email doesn't get delivered, please adjust function 'bounce_address'­ of /packages/acs-mail-lite/tcl/bounce-procs.tcl accordingly.
The easiest way would be to simply return a valid email address.

(Thanks to Frank Diekhoff, Pentamino GmbH for evaluating this)

How can I customize DynField Permissions?

­When I try add additional fields to the Helpdesk Tickets, the system won't let me edit them.

You have to configure several layers of permissions when adding a new DynField: 

• ]project-open[ V3.4.0.7.5:
  Please make sure you have updated at least to this version of ]po[. There are known issues with earlier versions.
  
  
• Read/Write Permission per Profile:
  Please go to Admin -> DynFields -> Object Type -> Ticket -> Attribute Types.
  Here you can set permissions per user group.
  Please make sure that "Employees" have "RW" (capital and bold letters) permissions for all [DynFields].
  
  
• Read/Write Permissions per Object Subtype:
  Please go to Admin -> DynFields -> Object Type -> Ticket -> Attribute-Type-Map.
  Here you can set permissions per Ticket Type (or: Project Type, Absence Type, ...).
  Please make sure that all radio boxes are in the rightmost E=Edit position.
  
  
• Appear/Disappear per Layout Page:
  Please got to Admin -> DynFields -> Object Type -> Ticket -> DynField Layout -> default
  This feature isn't used much in ]po[ V3.4. In future versions this feature will become a kind of "formular editor".
  Please click on "Add attribute" and create new attributes while the Attribute drop-down box contains values. Please use Y-Pos=10 and Label-Style=plain.
  
  

What is the actual meaning of: "In this configuration, the database will allow full access ..."

­What is the actual meaning of :

In this configuration, the database will allow full access to all data for all local users of the server computer while blocking the access for anybody not working locally on the computer. 

This setup is very convenient for our ]po[ demo server where we can’t  predict the name of the local users. However, you may want to change  these settings for a productive installation.
Please see http://www.postgresql.org/docs/7.3/static/client-authentication.html and the PO-Configuration-Guide for details.
The basic configuration allows all users of your local computer access to all of your data. Is that right for you? In general yes.
However, there are configurations where normal users have the right to log onto your server computer. That is the case for example if you use Windows Terminal Server. In this case you will have to modify your PostgreSQL security configuration.