Re: Cannot Authenticare User with SASL

On Sat, Jan 16, 2016 at 11:36:19PM +, tech...@comcast.net wrote: > OS: Ubuntu 14.04 LTS Server > Postfix version: 2.11.0-1ubuntu1 > Cyrus SASL Version: 2.1.25.dfsg1-17build1 Debian and Ubuntu tend to enable chroot jails by default. Chroot jails tend to not be able to reach the saslauthd u

Re: Question on master.cf (possible documentation patch)

I'm no Postfix guru but I'm using this on the backup mx. Suppose your domain is example.com. /etc/postfix/main.cf: transport_maps = hash:/etc/postfix/my.tables/transport /etc/postfix/my.tables/transport: example.comsmtp:[primary.example.com]:12345 .example.comsmtp:[prima

Cannot Authenticare User with SASL

OS: Ubuntu 14.04 LTS Server Postfix version: 2.11.0-1ubuntu1 Cyrus SASL Version: 2.1.25.dfsg1-17build1 I am unable to authenticate users using Postfix and Cyrus SASL. SASL appears to be correctly configured: sudo testsaslauthd -u test -p test 0: OK "Success." However when I perform a tel

Re: Authentication query

It could be possible, but I'd be scared of breaking ClearOS's integration. I would do better to update to ClearOS 7.x which uses a version of 2.10 and/or remove the use of SMTPS which is no longer required by my ISP. But thanks for the idea anyway. Nick On 1

Re: Question on master.cf

In message Paul Goyette writes: > While researching to see if I could find a way to fix my other issue > (how my primary-MX server can differentiate between messages originating > on my backup-MX server and those that are simply relayed from elsewhere) > I thought maybe I could configure the bac

Re: Authentication query

> On 16 Jan 2016, at 16:47, Nick Howitt wrote: > > Only since 2.10 or 2.11. It was added because of a discussion with me on > these lists. My distro (RHEL6 related) is stuck on 2.6.6. At some point, when > it is more stable I'll update to my distro's RHEL7 derivative. I can't help > the ISP

Re: Authentication query

On 16/01/2016 16:39, Benny Pedersen wrote: Nick Howitt skrev den 2016-01-16 17:03:  Because I have a dynamic (quasi-static) IP so I relay via my ISP who insisted on SMTPS. SMTPS has only been introduced i

Re: Authentication query

Nick Howitt skrev den 2016-01-16 17:03: Because I have a dynamic (quasi-static) IP so I relay via my ISP who insisted on SMTPS. SMTPS has only been introduced into postfix recently and is not available for my distro. Having said that I may remove stunnel/SMTPS as the ISP backed down and now all

Re: Authentication query

Nick Howitt: >

Re: Authentication query

On 16/01/2016 15:24, Wietse Venema wrote: Nick Howitt: Is it possibly to stop anyone outside my LAN who tries to authenticate on port 25? For example: Remove 'smtpd_sasl_auth_enable = yes' from main.cf. Will do.

Re: Authentication query

On 16/01/2016 15:15, Benny Pedersen wrote: Nick Howitt skrev den 2016-01-16 15:48: reject_rhsbl_sender, dsn.rfc-ignorant.org rfc domain is gone to dev/null see rfc

Re: Authentication query

Nick Howitt: > Is it possibly to stop anyone outside my LAN who tries to authenticate > on port 25? For example: Remove 'smtpd_sasl_auth_enable = yes' from main.cf. Add '-o smtpd_sasl_auth_enable=yes' to the submission service in master.cf. Wietse

Re: Authentication query

Nick Howitt skrev den 2016-01-16 15:48: reject_rhsbl_sender, dsn.rfc-ignorant.org rfc domain is gone to dev/null see rfc-ignorant.de I send mail to the outside world using smtps via stunnel. why complicate things ? Is it possibly to stop anyone outside my LAN who tries to authenticate o

Authentication query

Hi, I'm afraid I struggle a bit with understanding all the various restrictions with their meaning and where they are applied to so can I please have some help? Last night I noticed one IP address repeatedly trying to authenticate on port 25, trying different user names until he finally went

Re: How to configure postfix so that mail are received using time from the server

Patrick Ben Koetter skrev den 2016-01-16 08:35: If you can fix the date issue in the senders client. That would be the right [tm] solution. +1, love your books btw with Ralf, even if its old its still stable grounds to read

Re: Question on master.cf (possible documentation patch)

Well, I think I spoke too soon. I do have the dual-transport mechanism set up. But I still have a "classification" problem! On the backup-MX machine, I would like to have the equivalent of if (message_origin == local) then relay via transport1 else

Re: Question on master.cf (possible documentation patch)

OK, I got this working! (Persistence pays off...) On the backup MX, I made sure that $mydestination was correctly set, and then set $local_transport to "smtp:nexthop:port" On the primary server, I created a new smtpd transport (listener) [:::::x]: inet n - n -

Re: Question on master.cf (possible documentation patch)

On Sat, 16 Jan 2016, Viktor Dukhovni wrote: On Sat, Jan 16, 2016 at 04:00:48PM +0800, Paul Goyette wrote: my_smtp:12345 inet n - n - - smtpd But it's not clear to me if this syntax will define a new listener (in which case this would belong on my primary-MX machine) or if this

Re: Question on master.cf (possible documentation patch)

On Sat, Jan 16, 2016 at 04:00:48PM +0800, Paul Goyette wrote: > my_smtp:12345 inet n - n - - smtpd > > But it's not clear to me if this syntax will define a new listener (in > which case this would belong on my primary-MX machine) or if this would > enable an _outgoing_ connection to

Question on master.cf

While researching to see if I could find a way to fix my other issue (how my primary-MX server can differentiate between messages originating on my backup-MX server and those that are simply relayed from elsewhere) I thought maybe I could configure the backup-MX to use two different smtp transport