I understand that it's not that easy to quickly implement all those standards inside the current fm, but that is actually what you usually find on devices sending all sort of alarms via email: a simple configuration panel where you specify smtp,port,ssl or not, password type and so on. Actually, I can very easily achieve this with a few lines of code in Java using JavaMail, supporting all modern standards. Would it be nice to have it run a small Java app? If java is not suggested, there is also another native tool I often use: smtpclient, written in C. I mean, we don't need a full mailing system to send one single mail to a reachable mail server. A simple command like "smtpclient -S ..... Don't you think? ---------------------------------------------------------------------------------- Da: Hans Rosenfeld via illumos-discuss A: [email protected] Data: 18 novembre 2014 14.51.11 CET Oggetto: Re: [discuss] fault management mail settings Hi Gabriele, On Tue, Nov 18, 2014 at 01:31:05PM +0100, Gabriele Bulfon via illumos-discuss wrote: Hi, as far as I know, setting up fault management to send emails is not as straightforward as one would think. I would expect settings to have not only the destination email, but also the smtp server (ip or name) to use. Relying on system sendmail configuration is just a very headache. That would require to extend mail or mailx (whichever FMA uses, I don't know) to know how to speak SMTP, SSL, SASL (?), plus some more. I don't think this is going to happen. Alternatively you could try to make FMA use a different mailer like mutt that already supports all that. Not sure how hard that is. Or you just install another MTA like postfix and use IPS alternatives or mailwrapper to make that the default. Why? Because usually storage servers just know how to work with virtual servers, so they may no have public dns, public connection, full mx resolution. That would be delegated to the configured smtp server (maybe just an IP/port/ssl/user/pass) that knows all this stuff. Also, even in case it knows how to deliver through mx resolution, the system will present himself with a sender that in most cases is not valid (unknown domain, or whatever). So, we should also be able to configure a sender email. Editing sendmail.cf is a madness. Something I'm not doing for ages, since I switched to postfix for my real mail servers... The oldest sendmail I have ever configured was a version 5.x from 1988. Even back then editing sendmail.cf was not the preferred way to do it. It's essentially some kind of machine language. I have no idea why everybody still believes they have to edit sendmail.cf to change the configuration... The minimal configuration in sendmail.mc for delivering to a remote smtp server is this: define(`SMART_HOST',`relay:smtp.example.com') If you need SMTP AUTH, you'll also need something like this: define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN') FEATURE(`access_db') plus an entry in /etc/mail/access: AuthInfo:smtp.example.com "U:user" "P:password" Doesn't look all that terrible to me. Hans -- %SYSTEM-F-ANARCHISM, The operating system has been overthrown ------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175541-02f10c6f Modify Your Subscription: https://www.listbox.com/member/?&id;secret=21175541-29e3e0ee Powered by Listbox: http://www.listbox.com
------------------------------------------- illumos-discuss Archives: https://www.listbox.com/member/archive/182180/=now RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be Modify Your Subscription: https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4 Powered by Listbox: http://www.listbox.com
