# cat vmap
ilom-alert@192.168.100.63: avantsys...@avant.ca
Looks like there is a colon there -- could that be the problem?
Quoting Adam Thompson <athom...@athompso.net>:
I'm running smtpd 5.6-RELEASE inside the firewall, acting as an SMTP relay.
One host in particular (a Sun ILOM2 card) inists on sending some
emails addressed to "ilom-alert@192.168.100.63". This is a bug in
the firmware that they will not fix, so it's up to me to deal with it.
What I'm trying so far is:
#
# cat smtpd.conf
listen on all
table aliases db:/etc/mail/aliases.db
table vmap db:/etc/mail/vmap.db
table localnets { 192.168.10.0/24, 192.168.100.0/24,
192.168.157.0/24, 192.168.158.0/24, 192.168.101.0/24 }
accept from local for any relay via
smtp://smtp-relay.gmail.com
accept from source 192.168.100.63 for any virtual <vmap> deliver to
lmtp localhost:25
accept from source <localnets> for any relay via
smtp://smtp-relay.gmail.com
#
# cat vmap
ilom-alert@192.168.100.63: avantsys...@avant.ca
#
This isn't working, all I get in the log file is:
Jun 24 15:41:06 mailrelay smtpd[18970]: smtp-in: New session
3b402a76adf8e592 from host hexen-ilom.asg.local [192.168.100.63]
Jun 24 15:41:06 mailrelay smtpd[18970]: smtp-in: Failed command on
session 3b402a76adf8e592: "RCPT TO:<avantsys...@avant.ca>" => 550
Invalid recipient
Jun 24 15:41:06 mailrelay smtpd[18970]: smtp-in: Closing session
3b402a76adf8e592
...which, ironically, means the ILOM card is NOT misbehaving at the
moment. (Sometimes it does, sometimes it doesn't. Like I said,
it's a bug.)
Why isn't this working?
FYI, the previous log entries for the damaged emails looked like:
Jun 24 15:38:30 mailrelay smtpd[25726]: relay: PermFail for
df4ac3f4da1dd91b: session=9edd2c7aecf6c1b4,
from=<ilom-alert@192.168.100.63>, to=<avantsys...@avant.ca>,
rcpt=<->, source=192.168.100.96, relay=74.125.142.28
(ie-in-f28.1e100.net), delay=5s, stat=550 5.7.0
https://support.google.com/a/answer/6140680#maildenied
y6sm410732igy.1 - gsmtp
Jun 24 15:38:30 mailrelay smtpd[25726]: smtp-out: Error on session
9edd2c7aecf6c1b4: Connection closed unexpectedly
Jun 24 15:38:31 mailrelay smtpd[25726]: smtp-in: New session
9edd2c7b6ae6b2d7 from host localhost [local]
Jun 24 15:38:31 mailrelay smtpd[25726]: smtp-in: Accepted message
2cdbc169 on session 9edd2c7b6ae6b2d7: from=<>,
to=<ilom-alert@192.168.100.63>, size=982, ndest=1, proto=ESMTP
Jun 24 15:38:31 mailrelay smtpd[25726]: smtp-in: Closing session
9edd2c7b6ae6b2d7
Jun 24 15:38:34 mailrelay smtpd[25726]: smtp-out: Connecting to
smtp://74.125.142.28:25 (ie-in-f28.1e100.net) on session
9edd2c7cf3690436...
Jun 24 15:38:34 mailrelay smtpd[25726]: smtp-out: Connected on
session 9edd2c7cf3690436
Jun 24 15:38:34 mailrelay smtpd[25726]: relay: PermFail for
3da7d01d6b54d9ed: session=9edd2c7cf3690436, from=<>,
to=<ilom-alert@192.168.100.63>, rcpt=<->, source=192.168.100.96,
relay=74.125.142.28 (ie-in-f28.1e100.net), delay=8s, stat=550 5.1.1
https://support.google.com/mail/answer/6596 x14sm419535igx.1 - gsmtp
Jun 24 15:38:34 mailrelay smtpd[9955]: warn: queue: no return path!
Jun 24 15:38:35 mailrelay smtpd[25726]: relay: PermFail for
2cdbc169e9ab3b96: session=9edd2c7cf3690436, from=<>,
to=<ilom-alert@192.168.100.63>, rcpt=<->, source=192.168.100.96,
relay=74.125.142.28 (ie-in-f28.1e100.net), delay=4s, stat=550 5.1.1
https://support.google.com/mail/answer/6596 x14sm419535igx.1 - gsmtp
Jun 24 15:38:35 mailrelay smtpd[9955]: warn: queue: no return path!
(Naturally, google should reject such badly-addressed emails. That's
what I have to fix before handing it off.)
Thanks,
-Adam Thompson
athom...@athompso.net
--
You received this mail because you are subscribed to misc@opensmtpd.org
To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
--
Vijay Sankar, M.Eng., P.Eng.
ForeTell Technologies Limited
vsan...@foretell.ca
--
You received this mail because you are subscribed to misc@opensmtpd.org
To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org
