Create New Bug via email_in.pl

[losl...@gmail.com]

Hi,
I have 2 questions regarding the use of email_in.pl. I am running Bugzilla 5.0.4 on RHEL 7.6.

First problem: I am able to update an existing bug, using the following format, but the signature is added to the update. How do I prevent the signature from being added to the update?


Email Sent
Subject: [Bug 94]

@product General
@component software
@version unspecified

This is to verify that Bugzilla can update a ticket from an email
delivered to it's mailbox.

--
Signature

Updated Bug
This is to verify that Bugzilla can update a ticket from an email
delivered to it's mailbox.
--

Signature



Second problem: I am unable to create a new bug, using email_in.pl, with the following format:

Email Sent

Subject: Bugzilla New Bug Creation

@product General
@component software
@creation_ts 2019-02-13
@short_desc Bugzilla Emailing Requirements
@op_sys Linux
@priority Highest
@function_affected Application
@rep_platform All
@version unspecified

This is a new bug created using Bugzilla's email option. It lists all the required settings

--
Signature

Error message sent in response
There is no component named 'software@creation_ts 2019-02-13' in the 'General' product.

If I remove '@creation_ts 2019-02-13', it errors with, 'software@short_desc Bugzilla Emailing Requirements'

Please let me know if you need any additional information.

Any help is appreciated,
al

[Thorsten Schöning]

Guten Tag losl...@gmail.com,
am Donnerstag, 14. Februar 2019 um 17:29 schrieben Sie:

> First problem: I am able to update an existing bug, using the
> following format, but the signature is added to the update. How do
> I prevent the signature from being added to the update?

email_in.pl does that already, I suspect your signature is simply
wrong: It needs to have a space after "--":

> # This is the USENET standard line for beginning a signature block
> # in a message. RFC-compliant mailers use this.
> use constant SIGNATURE_DELIMITER => '-- ';

As per your second question, there might be problem with newlines:

> $body = remove_leading_blank_lines($body);
> my @body_lines = split(/\r?\n/s, $body);

Check your raw mail in a HEX editor for things like single \r.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail: Thorsten....@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

[Anthony Lynch]

Thanks for the quit turnaround. I can't believe after all these years
I never knew about the space after the SIGNATURE_DELIMITER; that fixed
the first issue.

In regards to bug creation, I checked and changed the emails to text
mode. This got me a bit closer. Here's the next error:

A value must be set for the 'Function Affected' field.

I am assuming, it wants something other than '@function_affected' as
the name of the field, but I have no idea.

Regards,
al

[losl...@gmail.com]

[Thorsten Schöning]

Guten Tag Anthony Lynch,
am Donnerstag, 14. Februar 2019 um 19:51 schrieben Sie:

> A value must be set for the 'Function Affected' field.

If that's a custom field, try the suffix "cf_". That's the name of
those fields internally at most places.

[Anthony Lynch]

Changed it to @cf_function_affected Application, with no luck. It shows as a Required Field, so if I leave it out, it gives the same error.

[Thorsten Schöning]

Guten Tag Anthony Lynch,
am Donnerstag, 14. Februar 2019 um 20:54 schrieben Sie:

> Changed it to @cf_function_affected Application, with no luck. It
> shows as a Required Field, so if I leave it out, it gives the same error.

But it is a custom field? I suggest checking the config of the field
again, especially the name, when it is required, if its values depend
on some other field and stuff. In January 2015 someone had a similar
problem and the prefix cf_ fixed it for him.

> Q: A value must be set for the 'Ticket_Type' field.
[...]
> A: All custom fields starts with cf_. So please use @cf_ticket_type
[...]
> Q: That did it! Thanks Albert.

Can't link the mails for some reason...

https://groups.google.com/forum/#!searchin/mozilla.support.bugzilla/Re$3A$20Using$20email_in.pl$20with$20custom$20field$20mandatory|sort:date/mozilla.support.bugzilla/StkF4F6TXN8/vhzNSdTb4o4J

[losl...@gmail.com]

Yes, it most definitely is a custom field. I missed that fact initially and the fact that it was created without an underscore in its name, cf_functionaffected.

Thank you so much for all your support and suggestions. I don't know if I ever would have figured it out without you.

Take care and regards,
al