Comments (2)
keepalived does not support SMTP authentication, nor indeed TLS for SMTP; it is strictly an RFC821 implementation that uses HELO and does not use authentication.
According to https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes error code 553 means 553 Requested action not taken: mailbox name not allowed, which seems to imply that either the MAIL FROM or the RCPT TO field is not acceptable. It may indeed be that this is because your email server requires authentication.
It you can provide a Wireshark trace of the SMTP exchange that fails with the 553 error, I will consider enhancing the SMTP functionality to support RFC2821 (EHLO etc), TLS and authentication, although this will not be an insignificant task.
from keepalived.
Hi, sorry for joining an already answered question, but maybe you can try to use a local installed postfix.
I'm not a postfix expert, but you can try configuring keepalived to send email notifications to 127.0.0.1:25 and then route those messages to your preferred server with TLS and authentication enabled.
from keepalived.
Related Issues (20)
- SELinux AVC denial for setattr HOT 4
- vrrp mem leak when reload HOT 2
- keepalived instances without explicit interface cannot be monitored via DBus HOT 1
- Template 'keepalived.conf' in the etc folder is somewhat misleading HOT 2
- Does Authentication in VRRP Have Actual Meaning HOT 1
- vipv6 cannot load balance to the backend HOT 4
- VRRP Json dump readiness notifications HOT 2
- Question: Active-active Load balancing using ARP replies HOT 1
- Arp reply from illegal virtual interface HOT 2
- Error: no route to host when connect via VIP HOT 3
- Segmentation fault on keepalived HOT 3
- Keepalived occasionally fails SSL_CHECK HOT 1
- Dedicated log file HOT 1
- ability to specify using vmac_prefix for addresses not on the VRRP instance's interface. HOT 1
- One of the vrrp instance remains in FAULT state after reload HOT 3
- One health check for Multiple VIP with same real servers HOT 1
- fifo_write_vrrp_states_on_reload not always working HOT 1
- Reload segfaults if routes are defined HOT 2
- VIPs are not cleaned up when the keepaived process is killed. HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from keepalived.