I have it set up like #1 already but it doesn't work. I tried sending 
from K9 Mail on my phone and it says:
Cannot connect to server. (Authentication methods SASL PLAIN and LOGIN  
are unavailable.)
Cannot connect to server. (Authentication method CRAM-MD5 is unavailable.)

I have these in my master.cf file:
127.0.0.1:1025 inet n       -       -       -       -       smtpd
127.0.0.1:11587 inet n       -       -       -       -       smtpd

This is my ASSP setup:
listenPort: 25
smtpDestination: 127.0.0.1:1025
smtpDestinationRT: empty
listenPort2: 587
smtpAuthServer: 127.0.0.1:11587
NoAUTHlistenPorts: empty
DisableExtAUTH: off
EnforceAuth: off

Could this be an issue with postfix and/or dovecot?

On 10/1/2014 10:06 AM, Stefan Pflug wrote:
> I' don't know your infrastructure, so I descripe my configuration:
>
>
> For outside users I use the Port 587/tcp "submission".
> In RFC 2476 it's definied for client-to-server communication with
> authentification.
>
>
> In the past I used  two possible ways on mta/assp site:
>
> 1. You define a portforwarding of port 587 to your assp. In assp you've to
> specify:
>     Second SMTP Listen Port (listenPort2) = 587
>     Second SMTP Destination (smtpAuthServer) = [ip of your mta]:[port of the
> second receive-connector]
>    
>    You can use optional parameters like "EnforceAuth" and "NoAUTHlistenPorts"
>
> 2. You define a portforwarding of port 587 directly to your mta.
>      The mta needs an 2nd listener for this port ( e.g. in exchange you have
> an second receive-connector for this job)
>
>
>
> If you use postfix google for "postfix submission".
> If your assp and postfix is on the same machine  you've to define a
> different port at postfix master.cf:
>
> Instead of
>       submission inet n - - - - smtpd
> use
>       127.0.0.1:11587 inet n       -       -       -       -       smtpd.
> in the master.cf and define
>       Second SMTP Destination (smtpAuthServer) = 127.0.0.1:11587
>
>
>
> ------------------------------------------------------------------------------
> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports
> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper
> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer
> http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk
> _______________________________________________
> Assp-user mailing list
> Assp-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/assp-user



------------------------------------------------------------------------------
Comprehensive Server Monitoring with Site24x7.
Monitor 10 servers for $9/Month.
Get alerted through email, SMS, voice calls or mobile push notifications.
Take corrective actions from your mobile device.
http://p.sf.net/sfu/Zoho
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to