Page 1 of 1

MESettings.MailFrom not working for Fogbugz upload

Posted: Wed Aug 01, 2018 2:32 am
by martin.lawrence
I am setting MESettings.MailFrom to a valid email address (name <email@domain>) but am not seeing the name or email address when I am uploading an error to FogBugz and the send assistant dialog pops up. It seems that I need to set the ContactForm name and email address? These seem to be defaulted to a Registry setting. As I have multiple users all using the same Windows logon this is not good for me. I need the ability to customise the 'from name' and 'from email address'. How can I do this?

Thanks
Martin

Re: MESettings.MailFrom not working for Fogbugz upload

Posted: Wed Aug 01, 2018 7:52 am
by madshi
Using FogBugz isn't really "mailing", so it doesn't use MESettings.MailFrom.

Please look at the bottom of this page:

http://help.madshi.net/HowToUseMadExcept.htm

It explains how to remove items from the bug report header. In the same way you can also add information. Hope that helps?

Re: MESettings.MailFrom not working for Fogbugz upload

Posted: Wed Aug 01, 2018 8:23 pm
by martin.lawrence
Yeah, I figured that the MailFrom field had no link to the FogBugz upload. It is important that that FogBugz gets the correct submitter name and email. Our software already has these recorded for the user so it would be great to have the facility to populate the name/email address fields before uploading to FogBugz - possible?

Re: MESettings.MailFrom not working for Fogbugz upload

Posted: Wed Aug 01, 2018 8:29 pm
by madshi
Which exact "name/email address fields" are you talking about? Are you talking about the bug report header of the madExcept bug report?

Re: MESettings.MailFrom not working for Fogbugz upload

Posted: Wed Aug 01, 2018 11:42 pm
by martin.lawrence
The contact information form. I assume that these are passed on to FogBugz?

Re: MESettings.MailFrom not working for Fogbugz upload

Posted: Thu Aug 02, 2018 7:13 am
by madshi
Where exactly in FogBugz do you want these to go? Does FogBugz have fields for that? The usual approach is to add this information to the madExcept bug report header. Isn't that good enough?