dhis2-devs team mailing list archive

[Bob Jolliffe <bobjolliffe@xxxxxxxxx>]

On 12 February 2013 12:49, Jason Pickering <jason.p.pickering@xxxxxxxxx> wrote:
> Would be potentially nice to send it directly from DHIS2 with JavaMail or
> something similar, so that Postfix was not required.  Setting up Postfix is
> pretty easy, but it has to be done right of course.
>
> Maybe we should add a configuration section on this to the docs once this
> gets fixed?

Yes.  Though I prefer exim4.  Which is also pretty easy.  The *most*
important thing is to have DNS, hostname and /etc/hosts properly
configured.  And of course understanding that you can't just make
these up - it has to be a real FQDN that you use.

If you don't have this, then relaying to a friendly smtp server is the
sensible option.  Though even that is probably better to setup at a
system level ie. exim4 sending to relay host rather than configuring
directly in dhis2.

Bob

>
>
> On Tue, Feb 12, 2013 at 2:30 PM, Bob Jolliffe <bobjolliffe@xxxxxxxxx> wrote:
>>
>> You are right of course.  The "fix" fixed only one of the 3 issues and
>> that incompletely.  Call it a plaster rather than a fix.
>>
>> A proper fix requires the addition of fields in the email setup
>> configuration which currently has just hostname, username and
>> password.
>>
>> In addition what is required are:
>> port number, reply to address (these could be populated with defaults)
>> and probably a checkbox for no smtp authentication required.
>>
>> I know Lars was concerned about having too much to configure but I
>> think the above would be fine provided there were sensible defaults.
>> Lars, what do you think.
>>
>> Talking of which, I don't know how most implementations are
>> configuring mail, but for an internet hosted server (which is
>> increasingly our target) I *think* the most sensible
>> zero-configuration default is to just point to localhost:25 with no
>> authentication.  I think most internet servers will have a local exim
>> or postfix installed for sending out system alerts and the like.  If
>> not they probably should :-)
>>
>> Bob
>>
>> On 12 February 2013 12:05, jason.p.pickering <1085070@xxxxxxxxxxxxxxxxxx>
>> wrote:
>> > Hi Bob,
>> > This looks like an incomplete fix actually. I think the username and
>> > password issue is OK from the code, but emails are still hard coded from
>> > noreply@xxxxxxxx.
>> >
>> > Regards,
>> > Jason
>> >
>> >
>> > ** Changed in: dhis2
>> >        Status: Fix Committed => Incomplete
>> >
>> > --
>> > You received this bug notification because you are a member of DHIS 2
>> > developers, which is subscribed to DHIS.
>> > https://bugs.launchpad.net/bugs/1085070
>> >
>> > Title:
>> >   emails-hardcoded-from-dhis2.org
>> >
>> > Status in DHIS 2 - District Health Information Software:
>> >   Incomplete
>> >
>> > Bug description:
>> >   Emails sent from the server (2.10) are sent by default on port 587 (no
>> >   way to configure this). Also, the mails always are from
>> >   noreply@xxxxxxxxx.  Not really sure this is a bug so much as a
>> >   blueprint, but anyway, wanted to report it.
>> >
>> > To manage notifications about this bug go to:
>> > https://bugs.launchpad.net/dhis2/+bug/1085070/+subscriptions
>> >
>> > _______________________________________________
>> > Mailing list: https://launchpad.net/~dhis2-devs
>> > Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> > Unsubscribe : https://launchpad.net/~dhis2-devs
>> > More help   : https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~dhis2-devs
>> Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~dhis2-devs
>> More help   : https://help.launchpad.net/ListHelp
>
>