Feature changed by: Scott Couston (zczc2311) Feature #313054, revision 2 Title: Interface Yast Mail Server connfig POP3/LDAPSMTP and notifications emai client openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Partner organization: openSUSE.org Description: Yast currently has the ability to configure a Mail Server. This configuration is really based on the user having their domain and DNS settings maintained in Opensuse/Apache or direct interface with Domains Managed via a DNS external host. We need to consider that the user many NOT EVEN HAVE A DOMAIN!!!As most Yast applications rely on the preface that every user HAS a domain. This assumption is short sighted and very narrow but has massive commercial applications as we ALL understand! This entire request is based on a user NOT having a Domain to interface..Just a normal user that uses the OPENsuse premise! This additional Enhancement request is in two parts. Firstly to add an additional setup to permit POP3/IMAP/SMTP to interface with locally held email clients of Thunderbird and Kmail etc in Yast Mail Server Creation. The secondly is to add POP3/SMTP/IMAP notifications to many Yast Applications. Many Yast applications don't currently have message notifications sent out with POP3/SMTP/IMAP. Most have only local syslog which really helps NO one on a LAN. This piece of code should be universally available to all yast application that, by nature would benefit for the ability to offer notifications. AppArmour tries to support email notifications, however these are based on sendmail and the fields in AppArmour Notifications will accept anything you enter into the 'email' fields without validation nor the ability to send notification out via POP3/SMTP/IMAP. So firstly on setup of Mail server add functions for POP3/SMTP/IMAP as the third option. Secondly to write code that any Yast applications that can benefit from notifications, enable to call for POP3/SMTP/IMAP fields that are valid validated and function in this way. If no mail server configuration exists call for one to be set-up dependant. Here we also make sendmail notifications as well! If mail server is configured for POP3/SMTP/IMAP then call notifications validated fields and interface AND If mail Server configured as currently opened then then provide fields validated for this purpose and interface. The same should be true for SENDMAIL/PROXY configured in mailserver to call for email validated functionality and fields validation. + Discussion: + #1: Scott Couston (zczc2311) (2011-12-07 00:02:25) + With this request for new.+ enhancement to Yast applications we can + provide Network based notification for the first time of both POP and + SENDMAIL and we can take care of users who DO NOT have a Domain and the + ones that do have a domain to manage either locally or hosted else + wear. Either way we provide Network Based notification to both open and + commercial users of SUSE! I will also be writing a new request to use + standard IP based syslog notifications to most all of Yast. That way + any syslog server or complex event manager can look after the largest + LANS to provide Network based IP syslog servers/complex event + management to take the health and performance of an entire Network and + Enterprise. + I will also be suggesting a .NLM Module to go hand in hand with IP + based Syslog notifications and Interface with other .NLM Modules that + auto install software or auto implement Network/Enterprise based + software config changes and interface with the Network/Update server + request I wrote the request for which was take up...:-) -- openSUSE Feature: https://features.opensuse.org/313054

Feature changed by: Scott Couston (zczc2311) Feature #313054, revision 4 Title: Interface Yast Mail Server connfig POP3/LDAPSMTP and notifications emai client openSUSE.org: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Partner organization: openSUSE.org Description: Yast currently has the ability to configure a Mail Server. This configuration is really based on the user having their domain and DNS settings maintained in Opensuse/Apache or direct interface with Domains Managed via a DNS external host. We need to consider that the user many NOT EVEN HAVE A DOMAIN!!!As most Yast applications rely on the preface that every user HAS a domain. This assumption is short sighted and very narrow but has massive commercial applications as we ALL understand! This entire request is based on a user NOT having a Domain to interface..Just a normal user that uses the OPENsuse premise! This additional Enhancement request is in two parts. Firstly to add an additional setup to permit POP3/IMAP/SMTP to interface with locally held email clients of Thunderbird and Kmail etc in Yast Mail Server Creation. The secondly is to add POP3/SMTP/IMAP notifications to many Yast Applications. Many Yast applications don't currently have message notifications sent out with POP3/SMTP/IMAP. Most have only local syslog which really helps NO one on a LAN. This piece of code should be universally available to all yast application that, by nature would benefit for the ability to offer notifications. AppArmour tries to support email notifications, however these are based on sendmail and the fields in AppArmour Notifications will accept anything you enter into the 'email' fields without validation nor the ability to send notification out via POP3/SMTP/IMAP. So firstly on setup of Mail server add functions for POP3/SMTP/IMAP as the third option. Secondly to write code that any Yast applications that can benefit from notifications, enable to call for POP3/SMTP/IMAP fields that are valid validated and function in this way. If no mail server configuration exists call for one to be set-up dependant. Here we also make sendmail notifications as well! If mail server is configured for POP3/SMTP/IMAP then call notifications validated fields and interface AND If mail Server configured as currently opened then then provide fields validated for this purpose and interface. The same should be true for SENDMAIL/PROXY configured in mailserver to call for email validated functionality and fields validation. Business case (Partner benefit): openSUSE.org: This provides notification for all application in yast that currently only wright audit logs or make a dismal or non working message type notifications. For example, the tick against, send root emails to this user, during installation; actually works in a usable manner of notification. I understand the extreme reluctance to change Yast as everything is a front end to innate command line interface. Its about time we get rid of this past-its-useby pretext Discussion: #1: Scott Couston (zczc2311) (2011-12-07 00:02:25) With this request for new.+ enhancement to Yast applications we can provide Network based notification for the first time of both POP and SENDMAIL and we can take care of users who DO NOT have a Domain and the ones that do have a domain to manage either locally or hosted else wear. Either way we provide Network Based notification to both open and commercial users of SUSE! I will also be writing a new request to use standard IP based syslog notifications to most all of Yast. That way any syslog server or complex event manager can look after the largest LANS to provide Network based IP syslog servers/complex event management to take the health and performance of an entire Network and Enterprise. I will also be suggesting a .NLM Module to go hand in hand with IP based Syslog notifications and Interface with other .NLM Modules that auto install software or auto implement Network/Enterprise based software config changes and interface with the Network/Update server request I wrote the request for which was take up...:-) + #2: Scott Couston (zczc2311) (2011-12-27 23:27:06) + more test-case and relationship to be added soon -- openSUSE Feature: https://features.opensuse.org/313054