Totally against this.
Even if mailpiler exposed a miltner port, if the daemon failed the port
would still fail.
Which makes the entire exercise of adding miltner support pointless.
As for having the SMTP port exposed globally, a simple firewall and/or
whitelist should always be enabled, which prevents the smtp being a
publicly accessible port.
Correctly setting up your mail-server should be the focus.
One can set it to discard bounce notifications for specific servers
as-well as queue the emails indefinitely for a specific smtp server.
On 05-May-15 4:23 PM, Janos SUTO wrote:
Hello Uwe,
On 2015-05-05 15:06, Uwe Eischens wrote:
of course it's not Piler's fault. But I've seen it happen a few times
in the last days while evaluating Piler with (until now) some of my
users Mailboxes, that the SMTP Port on the Piler machine suddenly
stopped listening, as mentioned because of various reasons which I yet
this should be investigated. Let me know if you need a hand to do it
have to search out, and that led to the described problem:
undeliverable mail responder to sender (and some baffled users on the
phone..."hey, I didn't send any mail to this address, so does it mean?
WTF, do I have a virus?" ;-). Sure the smtp-forwarding is a sturdy,
solid solution, but just for the (worst) case...
that's odd. Unless the remote server (in this case piler) actually
rejects
the message, it shouldn't be bounced back to the sender.
In our Mailserver (we are using Axigen) it is possible to set up a
special routing statement which kicks in during the processing of Mail
(more exact it's the first smtp-rule after the Mail is processed via
our ASSP AntiSpamProxy). Any message will then be additionally routed
to a ip:port which is definable in Axigen. So if Piler would be
capable of receiving mails through this port, I could set up the above
the port is one thing only, the used protocol is another. I assume it
must be milter, and the usual smtp won't work out. Perhaps it's worth
to check assp as well if it may rescue us.
routing to this milter port, no matter if it's an external or internal
IP.
But I guess it's a not-so-easy thing to implement that in Piler. Maybe
a completely different protocol, eg. milter, would definitely pose a
challenge and additional complexity, so for starters I'd look for a
perl (whatever) based example milter I could start from.
Janos
