how does email2trac parses the to-field

[anonymous]

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.

[bas]

It is not exact match, but a search. So substrings will match. It must be an exact match. It is a search:

• ​https://subtrac.sara.nl/oss/email2trac/browser/trunk/email2trac.py.in#L281

[anonymous]

is there any work around to make it an exact match?

[bas]

try to replace:

result =  TO_RE.search(header_field)

to:

result =  TO_RE.match(header_field)

[bas]

Some people want exact match other only want a match. For example allow all email for domain sara.nl:

• recipient_list : sara.nl

If we use exact match this must be rewritten to use regular expression:

• recipient_list : .*sara.nl$

So maybe i will make this configurable.

[anonymous]

thanks again.

[anonymous]

tried below config but old issue arise again.

​https://subtrac.sara.nl/oss/email2trac/ticket/268

Replying to bas:

try to replace:

result =  TO_RE.search(header_field)

to:

result =  TO_RE.match(header_field)

[anonymous]

i think i got it. I used use second option which is using regular expression in the recipient list.

instead of: recipient_list: om@…

i used: recipient_list: ^om@…

thank you for your help.

[anonymous]

sorry for misleading. this thing did not work since it created another issue.

Replying to anonymous:

i think i got it. I used use second option which is using regular expression in the recipient list.

instead of: recipient_list: om@…

i used: recipient_list: ^om@…

thank you for your help.

[bas]

(In [572]) adjusted email_header_acl we now loop over all to address to allow regexs like (*.sara.nl or ^basv@sara.nl), see #272

[bas]

Will close this. Did not encounter problem in our environment