Re: tracker does not want to send mail

Hi Ed:

In message <PH7PR12MB5656F6808B595CB3EF16E35484439@PH7PR12MB5656.namprd12.prod.
outlook.com>,
Ed Trumbull writes:
>I changed the setting to localhost. I still don't get any mail out.
>Worse, there's nothing in the /var/log/mail.log file or the
>/var/log/roundup.log file (where I have roundup logging) to show
>what's not happening. Nothing but silence.

I'm sorry you are having issues with this. Do you have a file
called:

   nosyreaction.py

in your tracker's detector directory? If it is not there, find the
tracker template directory (usually one of:

    /usr/share/roundup/templates
    <python lib directory>/site-packages/<prefix>/share/roundup/templates
    <python lib directory>/site-packages/share/roundup/templates
    <python lib directory>/dist-packages/usr/share/roundup/templates

where prefix is /usr or /usr/local etc. then copy
classic/detectors/nosyreaction.py into your tracker's detector
directory.


You can also use find (1) or locate (if it is set up) to find
nosyreaction.py. This is much more difficult than it should be. I have
opened https://issues.roundup-tracker.org/issue2551233 to try to take
the guess work out of finding tracker template locations.

A little background, unlike other issue tracking systems, the Roundup
core doesn't pre-define a field (like nosy) that magically sends
emails.  The work of sending mails is done by a reactor which is one
of the two types of detectors. In all the supplied tracker templates
(except minimal) the nosyreaction.py file is the link between the
tracker and the mail system.

The settings in config.ini configure the mail functions in the core
that are called by the reactor as well as basic functions of
nosyreaction.py.

When you run ./demo or roundup-demo, it does not include the
nosyreaction.py as sending mail requires more setup than required for a
demo. If you convert a tracker created using demo mode, you need to
add back nosyreaction.py to get email capability.

If you have a nosyreaction.py in your tracker's detectors directory,
check to make sure that postfix is listening on port 25 ('netstat -an'
or 'ss -tl'). If not you may need to add:

Note that mail programs like mail/mailx or elm do not use port
25. Instead they run a sendmail stub provided by the postfix
package. Roundup does not use this method and needs a mail server
listening on port 25 (or the port configured in config.ini).

IIRC pine/alpine do/can use port 25 to send mail. So you could try
sending mail with one of those to see if it works. Try this test as
well:

Run: telnet localhost 25
     Trying 127.0.0.1...
     Connected to localhost.
     Escape character is '^]'.
     220 uland ESMTP Postfix (Ubuntu)
     quit
     221 2.0.0 Bye

(the 25 above should be the port value from config.ini). You type
"quit" to exit as shown above. Does this work?

After you first posted, I took a look at the mailer code.
Unfortunately, the mailer subsystem doesn't do much logging.  To debug
further I would have to supply some instrumented code to you.

Hopefully this helps you move forward. Thanks for trying Roundup and
for your questions. They are helping us find out where the rough edges
are.

Have a great week.

--
				-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.