Custom Query (332 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (211 - 213 of 332)

Ticket Resolution Summary Owner Reporter
#263 fixed fetchmail and email2trac: run email2trac as www-data bas variofox@…
Description

I am running fetchmail on Ubuntu 8.04 with the following /etc/fetchmailrc

server mail.zzz.yy
proto pop3
user trac@somewhere.yy
pass mypassword
is www-data here
mda "email2trac"

Therefore, email2trac runs as user fetchmail.

Apache runs as www-data, the trac-directory is owend by www-data:wwwdata, ug+rwx.

As I expected, I get The user fetchmail requires read _and_ write permissions to the database file /yyy/trac/test/db/trac.db and the directory it is located in.

If I add the fetchmail-user to the www-data secondary group, tickets are created nicely. However, in the attachments directory, the subdirectories are owned by fetchmail:nogroup and as a result, I get Attachment ... not found errors.

Of course, I can "chown www-data -R /yyy/trac/" and then it works.

run_email2trac fails with an fetchmail: Query status=6 (IOERR) and is set to ---s--x--x 1 root root

How can I make email2trac run as www-data?

This is my /etc/email2trac.conf

[DEFAULT]
project: /yyy/trac/test
debug: 1
umask: 022
spam_level: 5
reply_all : 0
mailto_link: 0
umask: 022
email_header: 0
trac_version: 0.12
alternate_notify_template :
alternate_notify_template_update :
drop_spam : 0
verbatim_format: 1
strip_signature: 1
email_quote: >
strip_quotes: 0
ignore_trac_user_settings: 0
black_list: MAILER-DAEMON@
drop_alternative_html_version: 1
log_file: /tmp/email2trac.log
log_level: info
mta_user : fetchmail
trac_user : www-data

[test]
project: /yyy/trac/test
spam_level: 1
#71 fixed Feature Request: Picture in body not as Attachment bas anonymous
Description

Hi,

Is it possible to have the feature to have picture in the body of the ticket, not as attachment.

The case is that emails will contain screenshots, and need it in the body of ticket, because there are explanations of the screenshot.

#20 fixed fails with request for r/w permissions when user possesses them already anonymous rercola@…
Description

I have a Trac 0.10.3 install on this machine, and I grabbed email2trac 0.10, configured it using dpkg-buildpackage, and installed it as a deb.

I edited the config to point to my trac install, and then edited postfix to point appropriately and run run_email2trac.

It silently failed a number of times before I thought to turn on syslog, and it now prints the following error:

Aug 9 06:30:07 einstein email2trac: Traceback (most recent call last): Aug 9 06:30:07 einstein email2trac: File "/usr/bin/email2trac", line 1062, in ? tktparser.parse(sys.stdin) Aug 9 06:30:07 einstein email2trac: File "/usr/bin/email2trac", line 647, in parse self.db = self.env.get_db_cnx() Aug 9 06:30:07 einstein email2trac: File "/var/lib/python-support/python2.4/trac/env.py", line 182, in get_db_cnx return DatabaseManager?(self).get_connection() Aug 9 06:30:07 einstein email2trac: File "/var/lib/python-support/python2.4/trac/db/api.py", line 75, in get_connection return self._cnx_pool.get_cnx(self.timeout or None) Aug 9 06:30:07 einstein email2trac: File "/var/lib/python-support/python2.4/trac/db/pool.py", line 101, in get_cnx cnx = self._connector.get_connection(self._kwargs) Aug 9 06:30:07 einstein email2trac: File "/var/lib/python-support/python2.4/trac/db/sqlite_backend.py", line 113, in get_connection return SQLiteConnection(path, params) Aug 9 06:30:07 einstein email2trac: File "/var/lib/python-support/python2.4/trac/db/sqlite_backend.py", line 150, in init raise TracError?('The user %s requires read _and_ write ' \ Aug 9 06:30:07 einstein email2trac: TracError?: The user trac requires read _and_ write permission to the database file /var/acmtrac/trac-project/db/trac.db and the directory it is located in.

However, if we check the permissions... # ls -al /var/acmtrac/trac-project/db total 6352 drwxr-xr-x 2 trac trac 4096 Aug 9 06:22 . drwxr-xr-x 10 trac root 4096 Aug 9 06:10 .. -rw-r--r-- 1 trac root 2149376 Aug 9 06:22 trac.db

I'm rather at a loss. Trac functions fine, for what it's worth, so whatever it is, it's not breaking trac itself, just email2trac...

Note: See TracQuery for help on using queries.