Wietse Venema skrev 2012-11-22 14:53:
Patric Falinder:
All I actually need to do is to allow a dyndns-adress to send without
authentication.
And why can't the SMTP client be bothered to authenticate?
Did you put your printer/scanner on the Internet?
Wietse
Some of our customers "business-systems" are for some reason programmed
so they're not able to authenticate. Now this hasn't been a problem for
any of them because they've had a local mailserver (Exchange) where we
have configured it so it didn't have to authenticate. But now when we
have migrated all their mail to our servers and shutdown their old one,
they can't use that anymore and need to use ours.
We've asked the support for the software why it is like this and they
pretty much doesn't have an answer, they will probably implement it
later on hopefully. So it's pretty urgent for them to get this working
as they have a lot of business crucial emails that need to be delivered.
Also they have a dynamic IP so I was thinking I could add their
dyndns-adress to 'mynetworks' but it only takes IP addresses, so I will
have to manually add their new IP when/if they get a new one and by then
lots of emails might have been lost due to not being delivered.
Right now I have added their IP to 'mynetworks' and it's working fine
for now, but it's not reliable as they have a dynamic IP like I said.
So either I need to be able to add a hostname/domain instead of an IP to
be able to send mail without authenticating or have an open relay on a
non-standard port where I then configure in the router who can access it
from outside. Or if you guys might have a better solution?
Thanks,
-Patric