Pegasus Mail & Mercury

Yes, I set follow that but seem like mercury don't read AUTH file that keep user and password for checking AUTH

any user can send mail.

Sounds like you have not turned off relaying.  Show us the {MercuryS] section of your mercury.ini  file.  Here's one of mine.  I've flagged the critical parts for turning off relaying, setting strict relaying, turning on AUTH and setting the AUTH username and password file.

 

[MercuryS]
Debug : 1
Logfile : C:\MERCURY\Logs\MERCURYS\MS~y~m~d.LOG
Timeout : 300
Relay : 0
Strict_Relay : 1
Alt_Server_Port : 587
Allow_Illegals : 0
SMTP_Authentication : 1
Auth_File : c:\mercury\pass.txt
Session_logging : c:\mercury\logs\mercurys
Session_logmode : 0
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 0
No_VRFY : 0
SMTP_ConnFlags : 0

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.

I set like you all.... but still cant

 now, mail server and mail client is on 1 computer .

that is the problem?

and version of becky is 2.45

and 1 thing that wanna know ... when you sent mail from becky and type wrong pass with auth file on server , how about the result?

thx. so much 

 

 now, mail server and mail client is on 1 computer .

that is the problem?

No, not a problem at all.

 and version of Becky is 2.45

Mine is 2.48.1

and 1 thing that wanna know ... when you sent mail from Becky and type wrong pass with auth file on server , how about the result?

I get the  "Cannot relay" error when trying to relay.  Are you sure that you are getting to MercuryS on Mercury/32?  Do you see the connection from Becky on the console? Could you provide a MercuryS session log containing a Becky transaction?

 

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.

Yes i see the connection from Becky on the console.. like this..................

 -----------------------------------------------------------------------------

Connection from 127.0.0.1, Mon Oct 27 10:16:30 2008

EHLO [127.0.0.1]

AUTH CRAM-MD5

RSET

MAIL FROM:< test@mail.mercury >

RCPT TO: < ake@mail.mercury >

DATA

DATA - 16 lines,500 bytes

Quit

4 sec. elapsed, connection closed Mon Oct 27 10:16:34 2008

---------------------------------------------------------------------

But like Server dont read auth file that keep the pair of username and password

what wrong with connection?

OS is Windows2000

thx. for your help

teemeekiew:

Yes i see the connection from Becky on the console.. like this..................

 -----------------------------------------------------------------------------

Connection from 127.0.0.1, Mon Oct 27 10:16:30 2008

EHLO [120.0.0.1]

AUTH CRAM-MD5

RSET

MAIL FROM:< test@mail.mercury >

RCPT TO: < ake@mail.mercury >

DATA

DATA - 16 lines,500 bytes

Quit

4 sec. elapsed, connection closed Mon Oct 27 10:16:34 2008

---------------------------------------------------------------------

Looks like a normal process to me.

 

But like Server dont read auth file that keep the pair of username and password

what wrong with connection?

OS is Windows2000

thx. for your help

You really need to turn on session logging in MercuryS and provide a log if this transfer that shows all the details.

 

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.

i just turn on session log

and found that .....

--------------------------

...

<< 501 Authentication failed - bad user or password

>> RSET

<< 250 Command Processed OK.

...

----------------------------

and Mail send complete o_O"

Is it strange?

and RSET is mean RESET? if yes, how i cancel that RESET?

 

 

 

<< 501 Authentication failed - bad user or password

>> RSET

<< 250 Command Processed OK.

 Here is a complete session log showing a valid AUTH from Becky.  The base64 strings have been munged.

14:21:10.265: Connection from 192.168.1.5, Fri Oct 24 14:21:10 2008<lf>
14:21:10.265: << 220 tstephenson.com ESMTP server ready.<cr><lf>
14:21:10.281: >> EHLO [192.168.1.5]<cr><lf>
14:21:10.281: << 250-tstephenson.com Hello [192.168.1.5]; ESMTPs are:<cr><lf>250-TIME<cr><lf>
14:21:10.281: << 250-SIZE 0<cr><lf>
14:21:10.281: << 250-AUTH CRAM-MD5 LOGIN<cr><lf>
14:21:10.281: << 250-AUTH=LOGIN<cr><lf>
14:21:10.281: << 250-STARTTLS<cr><lf>
14:21:10.281: << 250 HELP<cr><lf>
14:21:10.453: >> AUTH CRAM-MD5<cr><lf>
14:21:10.453: << 334 PDg0Mzk3NDUzLjM0NkB0c3RlcGhlbnNvbi5jb20+<cr><lf>
14:21:10.453: >> dXNElciA4YTA2NTU0OWVlODDVjZmU2YjFEhZTJhMjE3MGQ3OWI4MA==<cr><lf>
14:21:10.453: << 235 Authentication successful.<cr><lf>
14:21:10.453: >> RSET<cr><lf>
14:21:10.453: << 250 Command processed OK.<cr><lf>
14:21:10.453: >> MAIL FROM:<donna@tstephenson.com><cr><lf>
14:21:10.453: << 250 Sender OK - send RCPTs.<cr><lf>
14:21:10.453: >> RCPT TO:<support@tstephenson.com><cr><lf>
14:21:10.468: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
14:21:10.468: >> DATA<cr><lf>
14:21:10.468: << 354 OK, send data, end with CRLF.CRLF<cr><lf>
14:21:10.468: >> Date: Fri, 24 Oct 2008 14:21:10 -0700<cr><lf>
14:21:10.468: >> From: Donna Stephenson <donna@tstephenson.com><cr><lf>
14:21:10.468: >> To: support@tstephenson.com<cr><lf>
14:21:10.468: >> Subject: Test of AUTH.<cr><lf>
14:21:10.468: >> Message-Id: <20081024142101.6DA6.5E4A2843@tstephenson.com><cr><lf>
14:21:10.468: >> MIME-Version: 1.0<cr><lf>
14:21:10.468: >> Content-Type: text/plain; charset="US-ASCII"<cr><lf>
14:21:10.468: >> Content-Transfer-Encoding: 7bit<cr><lf>
14:21:10.468: >> X-Mailer: Becky! ver. 2.48.01 [en]<cr><lf>
14:21:10.468: >> <cr><lf>
14:21:10.468: >> This a a test of Becky authorization.<cr><lf>
14:21:10.468: >> <cr><lf>
14:21:10.468: >> <cr><lf>
14:21:10.468: >> <cr><lf>
14:21:10.468: >> -- <cr><lf>
14:21:10.468: >> Donna Stephenson <donna@tstephenson.com><cr><lf>
14:21:10.468: >> <cr><lf>
14:21:10.625: >> .<cr><lf>
14:21:10.625: << 250 Data received OK.<cr><lf>
14:21:10.656: >> QUIT<cr><lf>
14:21:10.656: << 221 tstephenson.com Service closing channel.<cr><lf>
14:21:10.656: --- Connection closed normally at Fri Oct 24 14:21:10 2008. ---
14:21:10.656:

If the authorization fails and the RCPT TO: address is non-local then the 553 message is sent saying we do not relay.

08:07:06.093: Connection from 192.168.1.5, Mon Oct 27 08:07:06 2008<lf>
08:07:06.093: << 220 tstephenson.com ESMTP server ready.<cr><lf>
08:07:06.093: >> EHLO [192.168.1.5]<cr><lf>
08:07:06.093: << 250-tstephenson.com Hello [192.168.1.5]; ESMTPs are:<cr><lf>250-TIME<cr><lf>
08:07:06.093: << 250-SIZE 0<cr><lf>
08:07:06.093: << 250-AUTH CRAM-MD5 LOGIN<cr><lf>
08:07:06.093: << 250-AUTH=LOGIN<cr><lf>
08:07:06.093: << 250-STARTTLS<cr><lf>
08:07:06.093: << 250 HELP<cr><lf>
08:07:06.203: >> AUTH CRAM-MD5<cr><lf>
08:07:06.203: << 334 PDMyMTE1NDIwMy4zNDZAdHN0ZXBoZW5zb24uY29tPg==<cr><lf>
08:07:06.203: >> dXNlciBiNGZjYWUwMjcxOWUyMzViODY2NTkxN2I1ZGFhNjU1MA==<cr><lf>
08:07:06.203: << 501 Authentication failed - bad user or password.<cr><lf>
08:07:06.203: >> RSET<cr><lf>
08:07:06.203: << 250 Command processed OK.<cr><lf>
08:07:06.218: >> MAIL FROM:<donna@tstephenson.com><cr><lf>
08:07:06.218: << 250 Sender OK - send RCPTs.<cr><lf>
08:07:06.218: >> RCPT TO:<stephens@bayarea.net><cr><lf>
08:07:06.218: << 553 We do not relay without RFC2554 authentication.<cr><lf>
08:07:09.093: >> QUIT<cr><lf>
08:07:09.093: << 221 tstephenson.com Service closing channel.<cr><lf>
08:07:09.093: --- Connection closed normally at Mon Oct 27 08:07:09 2008. ---
08:07:09.093:

and Mail send complete o_O"

Is it strange?

Yes if the message was to a non-local user and then we really need to see your {MercuryS] section.  If the message is to a non-local address it looks like you have turned on authorization with out turning off relaying.

and RSET is mean RESET? if yes, how i cancel that RESET?

Why do you want to do that?

 

---

Thomas R. Stephenson
San Jose, California
Member of Pegasus Mail Support Team

I do not answer private messages from the forum. If you want to contact me use email to techsupp@tstephenson.com.

i think RSET is reason that mail still be send ...

-_-" but i'm not sure

and more question....

If the authorization fails and the RCPT TO: address is not the non-local , then how about the result?

In your test case both sender and recipient appear to be local:

MAIL FROM:< test@mail.mercury >

RCPT TO: < ake@mail.mercury >

Mercury will accept messages to local recipients without authorization.

The RSET command presumably means that the client restarts the transaction without authorization. But as Thomas said, the best way to find out exactly what is happening is to create a session log.

/Rolf 

Wow......

now it's ok

that was my problem -_-"

I dont know about local/non-local

thank you everybody for helping