We will add a tellmail command to fix that in future (tellmail breakin_release), currently I'm afraid you will need to just restart surgemail to unlock that account name.

      ChrisP.

On Tuesday 15/02/2011 at 5:24 pm, Tom Cross wrote:

Once I set OK to send from multiple IP they could send again.
But I don't really want to do that when there is a spammer on the other IP.

Tom Cross
Partner (Synergist)
HTMLnet
61 2 9288 9488
0418 295 336 brHIDDEN@tml.com.au

On Monday 14/02/2011 at 01:00:03, Lyle Giese wrote:

Tom Cross wrote:

Hi All
I received the following 2 emails
==========================================================================================
Mail 1
Important report from SurgeMail html.com.au host=guru - see details below

Spammer sending detected on 202.171.168.xxx from multiple ip addresses, change users password urgently,
or set g_breakin_white xxxxxx@html.com.au or disable by setting to *

Mail 2
Important report from SurgeMail html.com.au host=guru - see details below

Spammer sending detected on 86.197.28.155 from multiple ip addresses, change users password urgently,
or set g_breakin_white xxxxxx@html.com.au or disable by setting to *
==========================================================================================

The 202 address is the correct address.
The password was changed, but the customer still could not send out through our SurgeMail server.
What else do I need to do???? to allow them to send again.

I have also black listed the 86 address.

Tom Cross
Partner (Synergist)
HTMLnet
61 2 9288 9488
0418 295 336
tomc@html.com.au

Is their account locked out due to excessive bad password attempts?

I think you need to parse the logs a bit and find out why they are having problems sending.  You apparently have been talking to them.  Get their public ip address and have them try to send a test message and look at the logs.

Once you determine the error Surgemail is generating the proper remedy can be applied.

Lyle Giese
LCR Computer Services, Inc.