Custom Query (332 matches)
Results (247 - 249 of 332)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#272 | fixed | how does email2trac parses the to-field | bas | anonymous |
Description |
I set om@… as my recipient_list.And we have another email aom@…. When i send an email to aom@… from om@…, a ticket is created. is it because of the aom/om? or just a matter of misconfiguration. |
|||
#274 | fixed | Enhanced run_email2trac to support supplementary groups | bas | Dennis McRitchie <dmcr@…> |
Description |
Hi Bas, We are now using a more secure approach to group ownership and file permissions that supports 1) webserver r/w access, 2) r/w access by selected users who are logged in via ssh, and 3) no other r/w access. The idea is to create a supplementary group whose only members are the webserver user, and the selected ssh users. World access is then removed from all dual-access files (i.e., files writable via webserver and ssh). Thus, with a umask of 007 and the gid bit set, all created dual-access files are group-writable by users belonging to the special supplementary group, and to no one else. Currently, besides the uid, run_email2trac sets only the gid associated with the trac user. This patch will cause it to also set the supplementary groups associated with the trac user, thus supporting a "best practices" approach to dual-access. Let me know if you have any questions. Dennis McRitchie? |
|||
#275 | worksforme | Ticket updates do not display reporter address ('From'-header) | bas | rvengelen@… |
Description |
When updating an existing ticket through email2trac, the added comment does not contain the From: header. The wanted result is something like the following:
From: Some One <someone@example.org> To: An Other <another@example.org> CC: <email2trac@example.org> Date: Tue, 18 Oct 2011 15:44:06 +0200 Subject: RE: some subject (reference: #9304:) ...
On Tue, 18 Oct 2011 15:44:06 +0200 Some One <someone@example.org> wrote: Messagetext |