Opened 11 years ago
Closed 11 years ago
#308 closed defect (fixed)
Problems with run_email2trac and no logging possible
Reported by: | kmartinka@… | Owned by: | bas |
---|---|---|---|
Priority: | critical | Milestone: | |
Component: | run_emailtrac | Version: | 2.6.2 |
Keywords: | permissions, error, installation, setup, fetchmail, pop3 | Cc: |
Description
Hello,
I'm trying to figure out how to configure email2trac with fetchmail, but I'm unable to get it working if the .fetchmailrc is set to : mda "/usr/local/bin/run_email2trac"
but it works, if I have set the following line : mda "/usr/local/bin/email2trac"
Unfortunately it imports all emails in to TRAC :(, even from unathorised users or previously deleted users (removed from permissions, but it seems, that since they are still in DB the email2trac resolves it)
- The trac2email.conf in /usr/local/etc has following options enabled and set:
log_file : /home/trac/email2trac.log log_level : DEBUG log_type : FILE . . . ignore_trac_user_settings: 0 ticket_permission_system: 1
It does not log(!) and it does ignore any permissions in TRAC.. It imports every email and it does not create the log file.
The fetchmail is being run under the account which has the permissions to the home directory.. (trac)
Please help me with the three installation issues :
- email2trac works, while run_email2trac does not (maybe explain the difference, please
- logging is not working
- permissions are not working
(Trac version 0.12.2)
}}}
Attachments (0)
Change History (8)
comment:1 Changed 11 years ago by anonymous
comment:2 Changed 11 years ago by anonymous
OK, I've got the run_email2trac working in the fetchmail, but don't know what helped. It seems, that I had to add the parameters to ./configure switch. But to be honest, not 100% sure. But it works now. The user fetching the mail is "trac".
./configure --with-mta_user=trac --with-trac_user=www-data --enable-python --sysconfdir=/usr/local/etc
The logging is still not working. Any ideas?
comment:3 follow-up: ↓ 6 Changed 11 years ago by anonymous
Ok - found the issue with logging :
The parameter log_type : file is case sensitive. The valid entry is log_type : file , invalid is log_type : FILE . So there is a bug in documentation, which says, that it is the same as the TRAC configuration itself. TRAC is case insensitive while SARA is case sensitive..
comment:4 follow-up: ↓ 7 Changed 11 years ago by anonymous
Ok, found the issue. Again not in manual..
ticket_permission_system: trac has to be set. Then it starts to work.
But now another issue - the UPDATE is not working (it used to work before)
So when the ticket_permission_system is set to trac, then the UPDATE is not working.
New log entries (with ticket_permission_system set to trac) :
2012-11-25 20:06:37,031 email2trac ZELFA: subject: u'Ticket #1034' 2012-11-25 20:06:37,032 email2trac ZELFA: function ticket_update_by_subject 2012-11-25 20:06:37,032 email2trac ZELFA: function new_ticket 2012-11-25 20:06:37,037 email2trac ZELFA: function set_cc_fields 2012-11-25 20:06:37,037 email2trac ZELFA: function set_ticket_fields
Previous log entries (without the permission_system set to trac) :
2012-11-25 20:05:00,584 email2trac ZELFA: subject: u'Re: #1034: Test_novy koli permission' 2012-11-25 20:05:00,584 email2trac ZELFA: function ticket_update 2012-11-25 20:05:00,584 email2trac ZELFA: ticket id: #1034 2012-11-25 20:05:00,589 email2trac ZELFA: function check_permission: TICKET_APPEND
WTF!?! Will try the same subject..
comment:5 Changed 11 years ago by anonymous
- Resolution set to fixed
- Status changed from new to closed
Ok updating works just only if the Subject matches the original subject...
I am closing this ticket, but I am not very "happy" about the current version of SARA. There is still a lot to do, but unfortunately I will not be able to help you at this moment..
Hope that this ticket will help others.
comment:6 in reply to: ↑ 3 Changed 11 years ago by bas
- Resolution fixed deleted
- Status changed from closed to reopened
Replying to anonymous:
Ok - found the issue with logging :
The parameter log_type : file is case sensitive. The valid entry is log_type : file , invalid is log_type : FILE . So there is a bug in documentation, which says, that it is the same as the TRAC configuration itself. TRAC is case insensitive while SARA is case sensitive..
Thanks for reporting. I will fix this
comment:7 in reply to: ↑ 4 Changed 11 years ago by bas
Replying to anonymous:
Ok, found the issue. Again not in manual..
Which documentation did you read?
- https://oss.trac.sara.nl/email2trac/wiki/Email2tracConfiguration#PermissionSystem
- did you set the right permission in the trac permission interface
comment:8 Changed 11 years ago by anonymous
- Resolution set to fixed
- Status changed from reopened to closed
It is not "clearly" stated, which options the "option has".
I would recommend to change the documentation to :
NAME | POSSIBLE VALUES | DEFAULT VALUE | Description | Version |
ticket_permission_system | trac update_restricted_to_participants <blank> | <blank> | OPTIONAL. Select which Permission System must be used trac or update_restricted_to_participants | 1.5.0 |
Legend: <blank> - empty value
- This would help others to be effective when reading the doc. Almost all values do have 1/0 but this is the one, that has different values available
- Also, I would recommend to split the documentation in to subpages in wiki :
- This will add the possibility to go one step above and make the orientation easier. But anyway, I've suceeded to install, so I'm now closing this ticket as this is something, that may initiate another discussion in a new ticket.
But anyway - thank you very much for your software and after I will have some spare time, I will contribute with the missing features.. :)
The run_email2trac raises the following error in fetchmail :