Pegasus Mail & Mercury

Hi, I'm using XAMPP on my server local so I have  Mercury  as SMTP  server.  When I try to send email from  php script the SMTP server response is: 553 We do not relay non-local mail, sorry.

Can you help me? tanks 

zenic:

Hi, I'm using XAMPP on my server local so I have  Mercury  as SMTP  server.  When I try to send email from  php script the SMTP server response is: 553 We do not relay non-local mail, sorry.

Can you help me? tanks 

 

Go to Configuration | MercuryS |  Connection control and enter a username and password in the ESMTP AUTH file that has been setup.  You can then use that ESMTP authorization in your script.

David Harris has implemented ESMTP AUTH CRAM-MD5 for WinPMail, Mercury and Mercury/32.  They do a SMTP authentication in accordance with RFCs 2554 and 2195.  Mercury and Mercury/32 also do the LOGIN and the strange MS AUTH=LOGIN.  Here's a bit of code used by SquirrelMail to do the ESMTP auth.

function cram_md5_response ($username,$password,$challenge) {
    $challenge=base64_decode($challenge);
    $hash=bin2hex(hmac_md5($challenge,$password));
    $response=base64_encode($username . " " . $hash) . "\r\n";
    return $response;

 

---

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.

zenic:

Tank you!!!! Now Mercury is ok...bat i must fight with PHP...

code is:

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

<?php
    $y=mail("enzonicolino@alice.it", "oggetto", "messaggio");
    if($y){
    echo "<h3>Il messaggio e' stato inviato!</h3><p>Riceverai una risposta il prima possibile!</p>";
    }
?>

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

and in php.ini :

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

[mail function]
; For Win32 only.
SMTP =localhost       
smtp_port = 25

; For Win32 only.
sendmail_from = postmaster@localhost.com

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

Mercury core process say:

 from postmaster@localhost.com<local> to Admin <local> and not to enzonicolino@alice.it

 

the response of mail() function is true but...on remote alice server don't receive mail...

I don't know if you can help me too but tank you of heart.
 

 

I do not know anything about PHP code, but turn on session logging in MercuryS and then send your message via PHP again.  You might want to post the results to this list for analysis.

 

---

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.

When send message via PHP I have:
-------------------------------------------------------------------------------------------------------------
--------------Session logging----------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
05:16:26.515: Connection from 127.0.0.1, Sun Sep 16 05:16:26 2007<lf>
05:16:26.515: << 220 localhost ESMTP server ready.<cr><lf>
05:16:26.515: >> HELO southtec<cr><lf>
05:16:26.531: << 250 localhost Hello, southtec.<cr><lf>
05:16:26.531: >> MAIL FROM:<postmater@localhost.com><cr><lf>
05:16:27.578: << 250 Sender OK - send RCPTs.<cr><lf>
05:16:27.578: >> RCPT TO:<enzonicolino@alice.it><cr><lf>
05:16:27.578: << 250 Recipient OK - send RCPT or DATA.<cr><lf>
05:16:27.593: >> DATA<cr><lf>
05:16:27.593: << 354 OK, send data, end with CRLF.CRLF<cr><lf>
05:16:27.593: >> Date: Sun, 16 Sep 2007 05:16:27 +0200<cr><lf>
05:16:27.593: >> Subject: object<cr><lf>
05:16:27.593: >> To: enzonicolino@alice.it<cr><lf>
05:16:27.593: >> From: enzo <postmater@localhost.com><cr><lf>
05:16:27.593: >> <cr><lf>
05:16:27.609: >> Messaggio da: enzo (127.0.0.1)<lf>
05:16:27.609: >> Email: enzonicolino@alice.it<lf>
05:16:27.609: >> <lf>
05:16:27.609: >> ciao<cr><lf>
05:16:27.609: >> .<cr><lf>
05:16:27.609: << 250 Data received OK.<cr><lf>
05:16:27.609: >> QUIT<cr><lf>
05:16:27.609: << 221 localhost Service closing channel.<cr><lf>
05:16:27.703: --- Connection closed normally at Sun Sep 16 05:16:27 2007. ---
05:16:27.703:

-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
--------------in  \xampp\MercuryMail\QUEUE\MO0007B5.QDF-----------------------
-------------------------------------------------------------------------------------------------------------
Received: from spooler by localhost (Mercury/32 v4.01b); 16 Sep 2007 05:16:52 +0200
From: Mail Delivery System <postmaster@localhost>
To: Mail Delivery System <>
Date: Sun, 16 Sep 2007 05:16:41 +0200
Subject: Delivery failure notification
MIME-Version: 1.0
Content-Type: Multipart/Report; boundary=Part_Boundary-246746
Message-ID: <24928C2B5B@localhost>

--Part_Boundary-246746
Content-type: Text/plain; charset=US-ASCII
Content-description: Mail delivery failure report
Content-disposition: Inline

With reference to your message with the subject:
   "Delivery failure notification"

The local mail transport system has reported the following problems
it encountered while trying to deliver your message:

-------------------------------------------------------------------
*** <postmater@localhost.com>
User <postmater@localhost.com> not known at this site.
-------------------------------------------------------------------

Your mail message is being returned to you in the next part of this
message.

Should you need assistance, please mail postmaster@localhost.

--Part_Boundary-246746
Content-type: Message/RFC822
Content-description: Contents of original mail message

-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
--------------in  \xampp\MercuryMail\MAIL\Admin\YE4ADFL8.CNM---------------
-------------------------------------------------------------------------------------------------------------

Received: from spooler by localhost (Mercury/32 v4.01b); 16 Sep 2007 05:16:52 +0200
X-Envelope-To: Electronic Postmaster <Admin@localhost>
To: Electronic Postmaster <Admin@localhost>
From: Electronic Postmaster <postmaster@localhost>
Date: Sun, 16 Sep 2007 05:16:41 +0200
Subject: Postmaster Notify: Delivery Failure.
MIME-Version: 1.0
Content-type: multipart/mixed; boundary=28723.2385718

This message is in MIME format. If you are seeing this text,
then your mailer does not understand this format properly.

--28723.2385718
Content-type: Text/Plain; charset=US-ASCII
Content-Disposition: Inline
Content-Description: Reason for delivery failure.

The attached message has failed delivery and has been referred
to you as postmaster. The following error report or reports
were given to explain the problem:

   *** <postmater@localhost.com>
   User <postmater@localhost.com> not known at this site.

--28723.2385718
Content-type: Message/RFC822

From: Mail Delivery System <postmaster@localhost>
To: <postmater@localhost.com>
Date: Sun, 16 Sep 2007 05:16:30 +0200
Subject: Delivery failure notification
MIME-Version: 1.0
Content-Type: Multipart/Report; boundary=Part_Boundary-243BF0

--Part_Boundary-243BF0
Content-type: Text/plain; charset=US-ASCII
Content-description: Mail delivery failure report
Content-disposition: Inline

With reference to your message with the subject:
   "object"

The local mail transport system has reported the following problems
it encountered while trying to deliver your message:

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

--- Problems not related to specific addresses in the message:
Job has invalid or illegal from address.
*** <enzonicolino@alice.it>
-------------------------------------------------------------------

Your mail message is being returned to you in the next part of this
message.

Should you need assistance, please mail postmaster@localhost.

--Part_Boundary-243BF0
Content-type: Message/RFC822
Content-description: Contents of original mail message

Return-path: <postmater@localhost.com>
Received: from southtec (127.0.0.1) by localhost (Mercury/32 v4.01b) ID MG0007B0;
   16 Sep 2007 05:16:27 +0200
Date: Sun, 16 Sep 2007 05:16:27 +0200
Subject: object
To: enzonicolino@alice.it
From: enzo <postmater@localhost.com>

Messaggio da: enzo (127.0.0.1)
Email: enzonicolino@alice.it

ciao
ciao

--Part_Boundary-243BF0--


--28723.2385718--

-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
--------------in  Mercury core Process---------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
Job MG0007B3: from postmaster@localhost (local)
To: Admin (local) -OK
Job MG0007b4 from<> (local)
To: <> (non-local) (JOB MOooo7b5)- OK)

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

 

Tank you too..Teacher  

Looks like the MAIL FROM: address is invalid.  The postmater@localhost.com address lokks like it does not match any username or domain.

 

---

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.

Thanks dear Thomas R. Stephenson

But how and where we can use bit of code used by SquirrelMail to do the ESMTP auth?

 

 

Bharat:

Thanks dear Thomas R. Stephenson

But how and where we can use bit of code used by SquirrelMail to do the ESMTP auth?

 

 

 

I'm currently on a cruise ship and the access is bad, slow and expensive.  Send me a message to thomas@tstephenson.com and I'll try to help you offline.

 

---

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 had the same prob as zenic and i was looking at the first post you rote to him and i tried it and it didnt work! and ideas?

this is the error it gave me:

 

Warning: mail() [function.mail]: SMTP server response: 553 We do not relay without RFC2554 authentication. in C:\xampp\htdocs\tom\feedback.php on line 123

poopoo321:

i had the same prob as zenic and i was looking at the first post you rote to him and i tried it and it didnt work! and ideas?

this is the error it gave me:

 

Warning: mail() [function.mail]: SMTP server response: 553 We do not relay without RFC2554 authentication. in C:\xampp\htdocs\tom\feedback.php on line 123

You need to provide a MercuryS session log to find out what is happening.  If it is the ESMTP authorization problem then you will have to change your PHP application to use ESMTP authorization or turn off the anti-relay. You can turn off anti-relay setup in Configuration | MercuryS | Connection control as long as there is no access to MercuryS  from the internet that the spammers can use to send mail through your server.

 Mercury supports an Internet standard called Authenticated SMTP: when this feature is enabled, Mercury will advertise to connecting clients that it can accept SMTP authentication. If a client then authenticates correctly, it will be allowed to relay. Pegasus Mail and other widely-used Internet mail clients support authenticated SMTP, and it is an excellent way of allowing your roving users to use your server without opening yourself to relay abuse. Mercury supports three Authentication methods - CRAM-MD5, PLAIN and LOGIN, although LOGIN and PLAIN are very weak and you should avoid clients that use them.

Authenticated SMTP requires that both the client and server have access to a common password. For that reason, you need to provide Mercury with a list of usernames and the passwords that correspond to them - Mercury typically cannot get this information from the operating system for security reasons. Enter the name of the file where Mercury should store the user/password combinations, then click the Edit button to edit it. Each line contains one username/password pair.

Important note:  There is nothing that requires you to have a different SMTP Authentication password for every user on your system, nor is there anything that says that your SMTP Authentication username has to match any real user on your system. If you wish, it is perfectly permissible for you to set up a single AUTH username/password pair and provide it to all your users, although clearly this will have some ramifications for security.

If you check the control marked Authenticated SMTP connections may relay mail, then any authenticated connection (one where the user has provided any valid username/password pair defined in your SMTP Authentication file) will be permitted to relay messages even if it would otherwise have been prevented from doing so by either the normal or strict relaying tests (see above).

---

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.

You will get the 553 error if the local domain section does not contain the domain and the To address is misspelled. If the domain is within the local domains and the user is mis-spelled, you'll get a user not known message back instead of the chryptic 553.

---

Kind regards / Peter

Sorry, but after reading this thread, I am still confused...
I cannot send out mail; after installing Mercury/32 v4.62 and configuring my email client, I am getting two error messages:

I.  "Alert"
"An error occurred while sending mail.  The mail server responded: We do not relay non-local mail, sorry..  Please check the message recipients and try again."

and

II. "Send Message Error":
"Sending of message failed.
The message could not be sent because connecting to SMTP server localhost failed.  The server may be unavailable or is refusing SMTP connections.  Please verify that your SMTP server setting is correct and try again, or else contact your network administrator."

MercuryS Session Log

19:54:27.444: Connection from 127.0.0.1, Sun Oct 05 19:54:27 2008<lf>
19:54:27.444: << 220 [192.168.1.199] ESMTP server ready.<cr><lf>
19:54:27.464: >> EHLO [127.0.0.1]<cr><lf>
19:54:27.514: << 250-[192.168.1.199] Hello [127.0.0.1]; ESMTPs are:<cr><lf>250-TIME<cr><lf>
19:54:27.514: << 250-SIZE 0<cr><lf>
19:54:27.524: << 250 HELP<cr><lf>
19:54:27.524: >> MAIL FROM:<tronz@yandex.ru> SIZE=317<cr><lf>
19:54:27.574: << 250 Sender and size (317) OK - send RCPTs.<cr><lf>
19:54:28.604: >> RCPT TO:<tronz@yandex.ru><cr><lf>
19:54:28.654: << 553 We do not relay non-local mail, sorry.<cr><lf>
19:54:34.364: >> QUIT<cr><lf>
19:54:34.384: << 221 [192.168.1.199] Service closing channel.<cr><lf>
19:54:34.474: --- Connection closed normally at Sun Oct 05 19:54:34 2008. ---
19:54:34.484:


Also, just in case this info may help:

I am using Thunderbird 2.0.0.17 and the SMTP server settings for this account are:
Description: My SMTP Server  [=default server, but several other SMTP servers are also set up for other accounts]
Server Name: localhost
Port: 25
User Name: <not specified>
Secure Connection: None  [authentication and passwords are turned off]

I have a broadband connection and I am behind a firewall (m0n0wall).
I have only installed the Mercury SMTP component: S and E modules.
My ISP is blocking port 25.

In Mercury/32>Configuration>Mercury SMTP Server>Connection control - Relaying control>the box "Do not permit relaying of non-local mail" is checked.

Should I just uncheck it, or will doing that make my server vulnerable to exploitation?  If there are deeper addressing problems in my message or in the mail host how do I diagnose and fix them?

I should also say, that I also installed another SMTP server program: "Free SMTP Server", couldn't send out any mail with it either and got almost identical error messages as I and II above for Mercury.  I guess some setting needs changing on my box...?
 

tron:

19:54:27.524: >> MAIL FROM:<tronz@yandex.ru> SIZE=317<cr><lf>
19:54:27.574: << 250 Sender and size (317) OK - send RCPTs.<cr><lf>
19:54:28.604: >> RCPT TO:<tronz@yandex.ru><cr><lf>
19:54:28.654: << 553 We do not relay non-local mail, sorry.<cr><lf>

Those lines confirm that you don't relay and that yandex.ru is an external domain.  If it's local, you should add it to Core / Local domains.

In Mercury/32>Configuration>Mercury SMTP Server>Connection control - Relaying control>the box "Do not permit relaying of non-local mail" is checked.

Should I just uncheck it, or will doing that make my server vulnerable to exploitation?

No, leave that checked.  The top two relay checkboxes should normally always be checked.

On that same Connection control tab, add localhost (127.0.0.1) as an address to 'allow' relaying.

Which outgoing module are you using?  MercuryC or MercuryE?

tron:

I have only installed the Mercury SMTP component: S and E modules.
My ISP is blocking port 25.

As well as allowing relaying from 127.0.0.1, you will need to remove MercE (direct SMTP delivery module that will be blocked by your ISP) & install MercC (and configure it to relay through your ISP's smarthost with your username & password)