AW: Autosupport HTTPs receiver self hosted
Alexander Griesser <[email protected]>
| Newsgroups | gmane.comp.hardware.netapp |
|---|---|
| Message-ID | <[email protected]> |
Yah, I'm doing these for some of our customers too, but the question arose because one customer does not want to allow mails from specific IP addresses, he only supports authenticated mail relays and I could not find a way to configure SMTP authentication on the NetApp filers and hence the idea to somehow interecept these messages and multiplex or redirect them to a locally running service, which could then do $things with what it got from the filer. Alexander Griesser Head of Systems Operations ANEXIA Internetdienstleistungs GmbH E-Mail: [email protected]<mailto:[email protected]> Web: http://www.anexia-it.com<http://www.anexia-it.com/> Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 Von: Timothy Naple <[email protected]> Gesendet: Donnerstag, 18. Juli 2019 07:00 An: Alexander Griesser <[email protected]>; 'Toasters' <[email protected]> Betreff: RE: Autosupport HTTPs receiver self hosted Alexander, Most are doing HTTPS to NetApp Support and SMTP for their internal notifications (you can do those simultaneously). There is no HTTPS available to go anywhere other than NetApp Support at this time. For customers who cannot send to NetApp Support for security reasons they are mostly using SNMP monitoring and/or internal SMTP. Thank you, Tim From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Alexander Griesser Sent: Wednesday, July 17, 2019 9:36 PM To: Toasters Subject: Autosupport HTTPs receiver self hosted Hey there, when using SMTP for autosupports, one can add additional e-mail addresses which will also receive the SMTP notifications and we're using this feature to collect autosupports in one of our support mailboxes. If we'd want to move away from SMTP, how could we do that in the future? When we switch to the https transport method, the autosupports most likely will only be posted to NetApp, I suppose. Am I overlooking something or is there really no way to specify an additional URL or something like this so that we can also receive these alerts then? Ideally, I'd either like to run the autosupport receiver locally on our infrastructue and forward the requests to NetApp then. This way, I could parse the requests and (if necessary) create tickets, etc. and archive them internally. Anyone ever worked on something like this or knows where I can find more information about that? Thanks, Alexander Griesser Head of Systems Operations ANEXIA Internetdienstleistungs GmbH E-Mail: [email protected]<mailto:[email protected]> Web: http://www.anexia-it.com<http://www.anexia-it.com/> Anschrift Hauptsitz Klagenfurt: Feldkirchnerstraße 140, 9020 Klagenfurt Geschäftsführer: Alexander Windbichler Firmenbuch: FN 289918a | Gerichtsstand: Klagenfurt | UID-Nummer: AT U63216601 _______________________________________________ Toasters mailing list [email protected] http://www.teaparty.net/mailman/listinfo/toasters