Community Discussions and Support
Spammer again

Hi folks , i got an issue with an spammer / scammer again i just dont have a clue how he could spoof the right credentials ...

heres a session log , maybe someone can gimme a hint , i tried to decrypt the md5 pass and username but no success ...

i use dns blacklists , not permitting relay from non local , auth users can relay and spamhalter with all options except greylisting

 03:30:49.062: Connection from 64.220.121.86, Wed Mar 11 03:30:49 2009<lf>
03:30:49.078: << 220 mail.xxx.org ESMTP server ready.<cr><lf>
03:30:50.250: >> EHLO User<cr><lf>
03:30:50.250: << 250-mail.xxx.org Hello User; ESMTPs are:<cr><lf>250-TIME<cr><lf>
03:30:50.250: << 250-SIZE 0<cr><lf>
03:30:50.265: << 250-8BITMIME<cr><lf>
03:30:50.265: << 250-AUTH CRAM-MD5 LOGIN<cr><lf>
03:30:50.265: << 250-AUTH=LOGIN<cr><lf>
03:30:50.265: << 250 HELP<cr><lf>
03:30:50.859: >> AUTH LOGIN<cr><lf>
03:30:50.859: << 334 VXNlcm5hbWU6<cr><lf>
03:30:50.031: >> dGVzdA==<cr><lf>
03:30:50.031: << 334 UGFzc3dvcmQ6<cr><lf>
03:30:51.218: >> dGVzdA==<cr><lf>
03:30:51.218: << 235 Authentication successful.<cr><lf>
03:30:51.406: >> RSET<cr><lf>
03:30:51.406: << 250 Command processed OK.<cr><lf>
03:30:51.578: >> MAIL FROM:<support@securityi.com><cr><lf>
03:30:51.593: << 250 Sender OK - send RCPTs.<cr><lf>
03:30:51.781: >> RCPT TO:<marco@addr.com><cr><lf>
03:30:51.781: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:51.968: >> RCPT TO:<marco@adhoc.ch><cr><lf>
03:30:51.968: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:52.156: >> RCPT TO:<marco@drco.com><cr><lf>
03:30:52.156: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:52.359: >> RCPT TO:<marco@econophone.ch><cr><lf>
03:30:52.359: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:52.546: >> RCPT TO:<marco@geocities.com><cr><lf>
03:30:52.546: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:52.718: >> RCPT TO:<marco@gmail.com><cr><lf>
03:30:52.718: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:52.906: >> RCPT TO:<marco@gonnapuke.com><cr><lf>
03:30:52.906: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:53.093: >> RCPT TO:<marco@hgsi.com><cr><lf>
03:30:53.093: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:53.281: >> RCPT TO:<marco@hicom.net><cr><lf>
03:30:53.281: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:53.453: >> RCPT TO:<marco@hongkong.com><cr><lf>
03:30:53.453: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:53.656: >> RCPT TO:<marco@iland.net><cr><lf>
03:30:53.656: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:53.859: >> RCPT TO:<marco@ime.net><cr><lf>
03:30:53.859: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:53.046: >> RCPT TO:<marco@ina.com><cr><lf>
03:30:53.046: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:54.234: >> RCPT TO:<marco@inforamp.net><cr><lf>
03:30:54.234: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:54.421: >> RCPT TO:<marco@interaccess.net><cr><lf>
03:30:54.421: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
03:30:54.593: >> DATA<cr><lf>
03:30:54.593: << 354 OK, send data, end with CRLF.CRLF<cr><lf>
03:30:54.796: >> From: "Support"<support@securityi.com><cr><lf>
03:30:55.250: >> Subject: Notification from PayPal<cr><lf>
03:30:55.250: >> Date: Tue, 10 Mar 2009 19:30:54 -0700<cr><lf>
03:30:55.250: >> MIME-Version: 1.0<cr><lf>
03:30:55.250: >> Content-Type: text/plain;<cr><lf>
03:30:55.250: >>     charset="Windows-1251"<cr><lf>
03:30:55.250: >> Content-Transfer-Encoding: 7bit<cr><lf>
03:30:55.250: >> X-Priority: 3<cr><lf>
03:30:55.250: >> X-MSMail-Priority: Normal<cr><lf>
03:30:55.250: >> X-Mailer: Microsoft Outlook Express 6.00.2600.0000<cr><lf>
03:30:55.250: >> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000<cr><lf>
03:30:55.250: >> <cr><lf>
03:30:55.250: >> Dear PayPal Member,<cr><lf>
03:30:55.250: >> <cr><lf>
03:30:55.250: >> We recently have determined that different computers have logged onto<cr><lf>
03:30:55.250: >> your PayPal account, and multiple password failures were present before<cr><lf>
03:30:55.250: >> the logins. We now need you to re-confirm your account information to us.<cr><lf>
03:30:55.250: >> If this is not completed by March 08, 2009, we will be forced to suspend<cr><lf>
03:30:55.250: >> your account indefinitely, as it may have been used for fraudulent purposes.<cr><lf>
03:30:55.250: >> We thank you for your cooperation in this manner. To confirm your Account<cr><lf>
03:30:55.250: >> records click on the following link:<cr><lf>
03:30:55.250: >> <cr><lf>
03:30:55.250: >> http://www.paypal.com.cgi-bin.webscr.ki2row.es:8085/service/login.htm<cr><lf>
03:30:55.250: >> <cr><lf>
03:30:55.250: >> Thank you for your patience in this matter.<cr><lf>
03:30:55.250: >> PayPal Customer Service.<cr><lf>
03:30:55.250: >> Please do not reply to this e-mail as this is only a notification.<cr><lf>
03:30:55.250: >> <cr><lf>
03:30:55.250: >> 1999-2009 PayPal. All rights reserved.<cr><lf>
03:30:55.250: >> .<cr><lf>
03:30:55.250: << 250 Data received OK.<cr><lf>
03:30:55.437: >> QUIT<cr><lf>
03:30:55.437: << 221 mail.xxx.org Service closing channel.<cr><lf>
03:30:55.437: --- Connection closed normally at Wed Mar 11 03:30:55 2009. ---

&lt;p&gt;Hi folks , i got an issue with an spammer / scammer again i just dont have a clue how he could spoof the right credentials ...&lt;/p&gt;&lt;p&gt;heres a session log , maybe someone can gimme a hint , i tried to decrypt the md5 pass and username but no success ...&lt;/p&gt;&lt;p&gt;i use dns blacklists , not permitting relay from non local , auth users can relay and spamhalter with all options except greylisting &lt;/p&gt;&lt;p&gt;&amp;nbsp;03:30:49.062: Connection from 64.220.121.86, Wed Mar 11 03:30:49 2009&amp;lt;lf&amp;gt; 03:30:49.078: &amp;lt;&amp;lt; 220 mail.xxx.org ESMTP server ready.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.250: &amp;gt;&amp;gt; EHLO User&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.250: &amp;lt;&amp;lt; 250-mail.xxx.org Hello User; ESMTPs are:&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt;250-TIME&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.250: &amp;lt;&amp;lt; 250-SIZE 0&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.265: &amp;lt;&amp;lt; 250-8BITMIME&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.265: &amp;lt;&amp;lt; 250-AUTH CRAM-MD5 LOGIN&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.265: &amp;lt;&amp;lt; 250-AUTH=LOGIN&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.265: &amp;lt;&amp;lt; 250 HELP&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.859: &amp;gt;&amp;gt; AUTH LOGIN&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.859: &amp;lt;&amp;lt; 334 VXNlcm5hbWU6&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.031: &amp;gt;&amp;gt; dGVzdA==&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.031: &amp;lt;&amp;lt; 334 UGFzc3dvcmQ6&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.218: &amp;gt;&amp;gt; dGVzdA==&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.218: &amp;lt;&amp;lt; 235 Authentication successful.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.406: &amp;gt;&amp;gt; RSET&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.406: &amp;lt;&amp;lt; 250 Command processed OK.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.578: &amp;gt;&amp;gt; MAIL FROM:&amp;lt;support@securityi.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.593: &amp;lt;&amp;lt; 250 Sender OK - send RCPTs.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.781: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@addr.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.781: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.968: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@adhoc.ch&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.968: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.156: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@drco.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.156: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.359: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@econophone.ch&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.359: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.546: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@geocities.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.546: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.718: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@gmail.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.718: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.906: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@gonnapuke.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:52.906: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.093: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@hgsi.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.093: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.281: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@hicom.net&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.281: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.453: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@hongkong.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.453: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.656: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@iland.net&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.656: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.859: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@ime.net&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.859: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.046: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@ina.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:53.046: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:54.234: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@inforamp.net&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:54.234: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:54.421: &amp;gt;&amp;gt; RCPT TO:&amp;lt;marco@interaccess.net&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:54.421: &amp;lt;&amp;lt; 250 Recipient OK - send RCPT or DATA.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:54.593: &amp;gt;&amp;gt; DATA&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:54.593: &amp;lt;&amp;lt; 354 OK, send data, end with CRLF.CRLF&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:54.796: &amp;gt;&amp;gt; From: &quot;Support&quot;&amp;lt;support@securityi.com&amp;gt;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; Subject: Notification from PayPal&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; Date: Tue, 10 Mar 2009 19:30:54 -0700&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; MIME-Version: 1.0&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; Content-Type: text/plain;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; &amp;nbsp;&amp;nbsp; &amp;nbsp;charset=&quot;Windows-1251&quot;&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; Content-Transfer-Encoding: 7bit&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; X-Priority: 3&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; X-MSMail-Priority: Normal&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; X-Mailer: Microsoft Outlook Express 6.00.2600.0000&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; &amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; Dear PayPal Member,&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; &amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; We recently have determined that different computers have logged onto&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; your PayPal account, and multiple password failures were present before&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; the logins. We now need you to re-confirm your account information to us.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; If this is not completed by March 08, 2009, we will be forced to suspend&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; your account indefinitely, as it may have been used for fraudulent purposes.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; We thank you for your cooperation in this manner. To confirm your Account&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; records click on the following link:&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; &amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; http://www.paypal.com.cgi-bin.webscr.ki2row.es:8085/service/login.htm&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; &amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; Thank you for your patience in this matter.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; PayPal Customer Service.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; Please do not reply to this e-mail as this is only a notification.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; &amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; 1999-2009 PayPal. All rights reserved.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;gt;&amp;gt; .&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.250: &amp;lt;&amp;lt; 250 Data received OK.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.437: &amp;gt;&amp;gt; QUIT&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.437: &amp;lt;&amp;lt; 221 mail.xxx.org Service closing channel.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:55.437: --- Connection closed normally at Wed Mar 11 03:30:55 2009. ---&lt;/p&gt;

Having a user called 'test' with a password of 'test' will be why. [:O]

Change it.

&lt;p&gt;Having a user called &#039;test&#039; with a password of &#039;test&#039; will be why. [:O] &lt;/p&gt;&lt;p&gt;Change it. &lt;/p&gt;

ye that was the issue last time but i deleted it and i could decrypt it too with md5 decrypter but this time i cant guess which credentials the spammer used ... test / test isnt the fault ...

ye that was the issue last time but i deleted it and i could decrypt it too with md5 decrypter but this time i cant guess which credentials the spammer used ... test / test isnt the fault ...

[quote user="Sammy123"]ye that was the issue last time but i deleted it and i could decrypt it too with md5 decrypter but this time i cant guess which credentials the spammer used ... test / test isnt the fault ...
[/quote]

This says that it is

[quote]

03:30:50.859: >> AUTH LOGIN<cr><lf>
03:30:50.859: << 334 VXNlcm5hbWU6<cr><lf>
03:30:50.031: >> dGVzdA==<cr><lf>
03:30:50.031: << 334 UGFzc3dvcmQ6<cr><lf>
03:30:51.218: >> dGVzdA==<cr><lf>
03:30:51.218: << 235 Authentication successful.<cr><lf>[/quote]

It is base64 encoded, and decoding it gives test / test as the successfully authenticated user / pass

&lt;p&gt;[quote user=&quot;Sammy123&quot;]ye that was the issue last time but i deleted it and i could decrypt it too with md5 decrypter but this time i cant guess which credentials the spammer used ... test / test isnt the fault ... [/quote]&lt;/p&gt;&lt;p&gt;This says that it is&lt;/p&gt;&lt;p&gt;[quote]&lt;/p&gt;&lt;p&gt;03:30:50.859: &amp;gt;&amp;gt; AUTH LOGIN&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.859: &amp;lt;&amp;lt; 334 VXNlcm5hbWU6&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.031: &amp;gt;&amp;gt; dGVzdA==&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:50.031: &amp;lt;&amp;lt; 334 UGFzc3dvcmQ6&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.218: &amp;gt;&amp;gt; dGVzdA==&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt; 03:30:51.218: &amp;lt;&amp;lt; 235 Authentication successful.&amp;lt;cr&amp;gt;&amp;lt;lf&amp;gt;[/quote]&lt;/p&gt;&lt;p&gt;It is base64 encoded, and decoding it gives test / test as the successfully authenticated user / pass &lt;/p&gt;

weird ... i got no user named test in my local users and also no one in my aliases ... also no folder test in my mailbox folders ... now im confused ... [:S]

weird ... i got no user named test in my local users and also no one in my aliases ... also no folder test in my mailbox folders ... now im confused ... [:S]

It will be in auth.pwd, the file that MercS uses to authenticate SMTP connections.

It will be in auth.pwd, the file that MercS uses to authenticate SMTP connections.

no test / test their either ... but it seems like it is an old sessionlog from last year march  when i look at the timestamps inside the log . But when i look in filesystem the log file time stamp is from today ..... weird weird ...as if mercury changes the timestamp of old log files in filesystem to newer dates ...

no test / test their either ... but it seems like it is an old sessionlog from last year march&amp;nbsp; when i look at the timestamps inside the log . But when i look in filesystem the log file time stamp is from today ..... weird weird ...as if mercury changes the timestamp of old log files in filesystem to newer dates ...

If a session log with the name of the current transaction ID already exists, the new log is appended to the end of the existing file.

If a session log with the name of the current transaction ID already exists, the new log is appended to the end of the existing file.

oh ok , then it seems that this time it was blind alert ;)

thank u anyway for your  time and patience :)

&lt;p&gt;oh ok , then it seems that this time it was blind alert ;)&lt;/p&gt;&lt;p&gt;thank u anyway for your&amp;nbsp; time and patience :) &lt;/p&gt;
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft