Here are some relevant settings of my assp.cfg.

Postfix is only listening on port 25, but this port is redirected to port 2225.
In this way I can keep the setting of postfix intact (it's Plesk managed).
When I start ASSP this rule is inserted in iptables

-A PREROUTING -d 83.221.251.230/32 -p tcp -m tcp --dport 25 -j DNAT 
--to-destination 83.221.251.230:2225

This rule is deleted when I stop ASSP. The start and stop scripts are heavily 
modified and do this automatically.


# egrep '(Auth|AUTH|localDomains|listenPort)' assp.cfg
listenPort:=83.221.251.230:2225
listenPortSSL:=
listenPort2:=83.221.251.230:587
smtpAuthServer:=83.221.251.230:25
NoAUTHlistenPorts:=
EnforceAuth:=1
MaxAUTHErrors:=3
noMaxAUTHErrorIPs:=file:files/nomaxautherrorips.txt
WhitelistAuth:=1
nolocalDomains:=
relayAuthUser:=00000e0000
relayAuthPass:=00000e0000
localDomains:=file:files/localdomains.txt
NoTLSlistenPorts:=
useAuthenSASL:=




 
 
-----Oorspronkelijk bericht-----
> Afzender:Jean-Pierre van Melis <[email protected] <mailto:[email protected]> >
> Verstuurd: Zondag 23 Februari 2014 11:43
> Aan: ASSP development mailing list <[email protected] 
> <mailto:[email protected]> >
> Onderwerp: Re: [Assp-test] Spammers able to go through ASSP with false 
> credentials... (as it seems to be for me)
> 
> I've been thinking a bit more about this...
> 
> Never in the past I configured postfix to distrust its own IP's and ASSP has 
> always been the last line of defence in my setups. I'm running ASSP for more 
> than 5 years and it never showed this behaviour before.
> 
> I just now saw a post about someone in the mailing list about some 
> auto-whitelisting of an address.
> His problem might be related to this.
> 
> 
> As a sidenote....  Having a true full transparent proxy would not get me in 
> this trouble. Has anyone ever succeeded to get an ASSP-setup this way with 
> for instance iptables TPROXY? With a full transparent proxy the MTA thinks it 
> gets its information from the real IP. Postfix would never endorse relaying 
> from a foreign IP without authentication.
> 
> 
> 
>  
>  
> -----Oorspronkelijk bericht-----
> > Afzender:Jean-Pierre van Melis <[email protected] <mailto:[email protected]>  
> > <mailto:[email protected] <mailto:[email protected]> > >
> > Verstuurd: Zondag 23 Februari 2014 11:23
> > Aan: [email protected] 
> > <mailto:[email protected]>  
> > <mailto:[email protected] 
> > <mailto:[email protected]> > 
> > Onderwerp: [Assp-test] Spammers able to go through ASSP with false 
> > credentials... (as it seems to be for me)
> > 
> > In a setup that's been running for several years I'm now getting spammers 
> > able to send authenticated mail through an ASSP => postfix setup. The 
> > server is managed using Plesk 11.5
> > I'm still investigating it and still don't know exactly what's going on.
> > 
> > Can someone help me to find the source of the problem?
> > 
> > The first time I encountered it I checked the password of the user and it 
> > was indeed a password that could have been obtained using a dictionary 
> > attack. But now I'm getting more and more users and some of them have less 
> > likely passwords. I'm now thinking these spammers can get in without valid 
> > credentials.....
> > 
> > I'm now thinking it's something else. I've been blocking some IP's in 
> > Russia, India, Bulgaria and Turkey but now I would like to know exactly 
> > what's going on.
> > 
> > ASSP is listening on port 25 and port 587. On port 587 it's obligatory to 
> > use authentication. I just recently created a max of 3 authentication 
> > errors in ASSP. Never had it before...
> > 
> > Another thing to note is the sender's address. There's indeed a 
> > [email protected] <mailto:[email protected]>  <mailto:[email protected] 
> > <mailto:[email protected]> > , but this is an alias and this address can't be 
> > used for authentication. This account uses a different login name and the 
> > full name including @blabla.nl has to be used for authentication
> > 
> > Here's ASSP's log...
> > 
> > # grep 116.203.191.142 /opt/ASSP/logs/maillog.txt  | head
> > Feb-21-14 17:44:08 [Worker_2] Connected: session:7FFA5A36C968 
> > 116.203.191.142:3323 > 85.214.251.232:2225 > 85.214.251.232:25
> > Feb-21-14 17:44:08 [Worker_2] 116.203.191.142 [SMTP Reply] 220 
> > ns6.mr-wolf.nl ESMTP Postfix (Ubuntu)
> > Feb-21-14 17:44:08 [Worker_2] 116.203.191.142 [SMTP Reply] 250 DSN
> > Feb-21-14 17:44:09 [Worker_2] 116.203.191.142 info: injected STARTTLS 
> > request to 85.214.251.232
> > Feb-21-14 17:44:09 [Worker_2] [TLS-out] 116.203.191.142 info: 
> > authentication - plain is used
> > Feb-21-14 17:44:09 [Worker_2] [TLS-out] 116.203.191.142 [SMTP Reply] 235 
> > 2.7.0 Authentication successful
> > Feb-21-14 17:46:26 ns6-01186-06849 [Worker_2] [TLS-out] 116.203.191.142 
> > <[email protected] <mailto:[email protected]>  <mailto:[email protected] 
> > <mailto:[email protected]> > > info: found message size announcement: 27 Byte
> > Feb-21-14 17:46:27 ns6-01186-06849 [Worker_2] [TLS-out] 116.203.191.142 
> > <[email protected] <mailto:[email protected]>  <mailto:[email protected] 
> > <mailto:[email protected]> > > [SMTP Reply] 250 2.1.0 Ok
> > 
> > 
> > At the same time I'm getting this in the postfix. It doesn't mention any 
> > approval of a login.... 
> > 
> > grep 'Feb 21 17:44:0' /var/log/psa/maillog.processed
> > 
> > Feb 21 17:44:01 ns1 postfix/smtpd[5838]: warning: SASL authentication 
> > failure: no secret in database
> > Feb 21 17:44:01 ns1 postfix/smtpd[5838]: warning: 
> > ns6.mr-wolf.nl[85.214.251.232]: SASL CRAM-MD5 authentication failed: One 
> > time use of a plaintext password will enable requested mechanism for user
> > Feb 21 17:44:01 ns1 postfix/smtpd[18250]: connect from 
> > ns6.mr-wolf.nl[85.214.251.232]
> > Feb 21 17:44:01 ns1 postfix/smtpd[18250]: disconnect from 
> > ns6.mr-wolf.nl[85.214.251.232]
> > Feb 21 17:44:04 ns1 postfix/smtpd[5838]: warning: SASL authentication 
> > failure: no secret in database
> > Feb 21 17:44:04 ns1 postfix/smtpd[5838]: warning: 
> > ns6.mr-wolf.nl[85.214.251.232]: SASL CRAM-MD5 authentication failed: One 
> > time use of a plaintext password will enable requested mechanism for user
> > Feb 21 17:44:08 ns1 postfix/smtpd[4453]: connect from 
> > ns6.mr-wolf.nl[85.214.251.232]
> > Feb 21 17:44:08 ns1 courier-imaps: Unexpected SSL connection shutdown.
> > Feb 21 17:44:09 ns1 postfix/smtpd[5838]: warning: SASL authentication 
> > failure: no secret in database
> > Feb 21 17:44:09 ns1 postfix/smtpd[5838]: warning: 
> > ns6.mr-wolf.nl[85.214.251.232]: SASL CRAM-MD5 authentication failed: One 
> > time use of a plaintext password will enable requested mechanism for user
> > 
> > 
> > Because ASSP is on the same IP as the MTA this MTA will relay anything. 
> > It's ASSP that has to stop the connection because the authentication 
> > failed. It appears it doesn't
> > 
> > 
> > 
> > ------------------------------------------------------------------------------
> > Managing the Performance of Cloud-Based Applications
> > Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> > Read the Whitepaper.
> > http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk_______________________________________________
> >  
> > <http://pubads.g.doubleclick.net/gampad/clk?id=121054471&amp;iu=/4140/ostg.clktrk_______________________________________________>
> >   
> > <http://pubads.g.doubleclick.net/gampad/clk?id=121054471&amp;iu=/4140/ostg.clktrk_______________________________________________>
> >  
> > <http://pubads.g.doubleclick.net/gampad/clk?id=121054471&amp;amp;iu=/4140/ostg.clktrk_______________________________________________&gt;>
> >  ; 
> > Assp-test mailing list
> > [email protected] <mailto:[email protected]>  
> > <mailto:[email protected] 
> > <mailto:[email protected]> > 
> > https://lists.sourceforge.net/lists/listinfo/assp-test
> > 
> 
> ------------------------------------------------------------------------------
> Managing the Performance of Cloud-Based Applications
> Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
> Read the Whitepaper.
> http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk_______________________________________________
>  
> <http://pubads.g.doubleclick.net/gampad/clk?id=121054471&amp;iu=/4140/ostg.clktrk_______________________________________________>
>  
> Assp-test mailing list
> [email protected] <mailto:[email protected]> 
> https://lists.sourceforge.net/lists/listinfo/assp-test
> 

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to