Egoitz Aurrekoetxea Aurre wrote:
Is not valid for doing all you're customers mail machines to connect
to a relayhost, because machines connecting to relay host smtpd server
are not doing any pop against nothing. Take a list of users in all
databases, do a small table in mysql set the primary ke
Michael Orlitzky wrote:
If your customers have POP3/IMAP accounts, there is already a database
of usernames and passwords *somewhere*. Query that.
Yes there is - actually there is about six different ones - so making a
system that could talk to all those authentication mechanisms would take
Ansgar Wiechers wrote:
You could put your customers on a private network not accessible by the
public (and I mean "VPN" kind of private here rather than RFC 1918 kind
of private). However, that's just moving authentication and encryption
to a different layer.
Why do you want to avoid using SASL
Sahil Tandon wrote:
You must setup SASL and only let authenticated users relay through this
new server. Forget about contacting the other mail servers to verify
that the sender email exists; that is in no way a form of
authentication.
http://www.postfix.org/SASL_README.html
You are probably r
Sven Hoexter wrote:
Does that mean that those customers run their mailserver on dynamic IP
addresses? Otherwise I'd use the IP address/domain of the customers as
the criteria.
Sven
Hi Sven,
Yes, I'm sorry, forgot to give that information. They might be running
dynamic IP adresses/domains,
Hi all,
The company I work for have approximately nine mail servers, including
Postfix, qmail, sendmail and exim.
They would like to make ONE SMTP relay host server so that all their
customers can use their SMTP server to send mail through.
The customers already get their incoming mail through
