Tue, 08 Jan 2013 22:06:26 +0100 skrev Reindl Harald <h.rei...@thelounge.net>:
> > > Am 08.01.2013 21:48, schrieb Titanus Eramius: > > This raises the question (or at least I think it do), if it's > > possible to "force" the users onto 587 by denying relay access to > > 25? > > it's more a human problem than a technically to force a large amount > of users to change their for a long time wrong usage of port 25 > > submission inet n - n - 50 smtpd > -o smtpd_client_connection_count_limit=15 -o > smtpd_client_connection_rate_limit=80 -o smtpd_sasl_auth_enable=yes > -o smtpd_delay_reject=yes -o > smtpd_client_restrictions=permit_sasl_authenticated,reject -o > max_idle=1h -o max_use=500 > > remove "permit_sasl_authenticated" at the same time from main.cf and > you should be more or less done, but as said. how to explain all > users that thheir config is wrong since the first day they are using > it > Thankfully I still have a few months before I start to have actual costumers, so this is my one chance to avoid some of the common problems. But I suspect you might be right with 587 anyway, because at least this client (Claws Mail) uses 25 as the standard port when sending through POP. Thank you for the example to deactivate client relaying through 25. I think this solves my problem, so thanks again for the replies.
