[quote user="houston"]

Yes you're right, outlook express sent e-mails properly. I guess I didn't bollux the syntax......

[/quote]

Sorry, I wasn't trying to be rude [:)]  , but using telnet for any more that basic testing is prone to typo's and errors, using a client generally removes this point of failure.

I still think you should look at your relaying controls urgently, as with these turned off, sure YOU can send mail, but so can EVERYONE else. 

I installed Mercury/32 Version 4.52 a while ago and I guess I am missing something simple. Searched through the forum but couldn't get an answer, sorry if this is a double thread. I am testing the system via telnet smtp commands, everything looks normal. However, the e-mails are kept in the queue and they are not delivered to outside domains. Mercury Core Process says:

Outgoing jobs: Ready 7, Pending 0, Complete 0.  

Local delivery is successful and relay is enabled for our internal network under Configuration -> MercuryS SMTP Server -> Connection Control by unchecking "Do not permit SMTP  Relaying of non-local mail".

 
No error has been returned either. Is there any other thing that I should do for proper relaying?

Thanks,
Best,

Ustun
 

[quote user="houston"]

I installed Mercury/32 Version 4.52 a while ago and I guess I am missing something simple. Searched through the forum but couldn't get an answer, sorry if this is a double thread. I am testing the system via telnet smtp commands, everything looks normal. However, the e-mails are kept in the queue and they are not delivered to outside domains. Mercury Core Process says:

Outgoing jobs: Ready 7, Pending 0, Complete 0.  

Local delivery is successful and relay is enabled for our internal network under Configuration -> MercuryS SMTP Server -> Connection Control by unchecking "Do not permit SMTP  Relaying of non-local mail".

 
No error has been returned either. Is there any other thing that I should do for proper relaying?

Thanks,
Best,

Ustun
 

[/quote]

How have you setup Mercury/32 to send the mail?  MercuryE? MercuryC?   In either case, what do the logs show?  Have you tried using session logging to see what errors are being reported?  Do you have any MO*.QIF files matching a MO*.QCF/QDF.  The QIF files show the delivery last error.

Hi,

If you can inject mail by SMTP, relaying control is correctly configured.

It sounds like you've simply failed to load either MercuryC or MercuryE.  Those are necessary to send mail using SMTP.  Make sure you have either one enabled and configured and your jobs should leave your queue.

Cheers,

Sabahattin

Yes, thanks, I added MercuryE and managed to send mails out side. I used my gmail and hotmail web client accounts. From, To and body are empty in gmail and To is empty in hotmail, as well. I know that these issues don't seem "so" specific to mercury, probably some RFC stuff but would appreciate if anyone experienced such problems and shed some light.  Tests were done via telnet from localhost and subnet, again.

 Thanks,

Ustun
 

[quote user="houston"]

Yes, thanks, I added MercuryE and managed to send mails out side. I used my gmail and hotmail web client accounts. From, To and body are empty in gmail and To is empty in hotmail, as well. I know that these issues don't seem "so" specific to mercury, probably some RFC stuff but would appreciate if anyone experienced such problems and shed some light.  Tests were done via telnet from localhost and subnet, again.

 Thanks,

Ustun
 

[/quote]

Maybe you bolluxed the syntax in the telnet session [:#]

Have you tried with a mail client?

Also, if your mercuryS is listening on your internet connection you will want to turn this back ON, pronto...

Configuration -> MercuryS SMTP Server -> Connection Control by unchecking "Do not permit SMTP  Relaying of non-local mail"

[/quote]

You will also want to turn on "Strict relaying" and, if you have any offsite users, "Authenticated connections may relay.."

You can add your local IP range as a connection control entry to set "Connections from this range may relay...", then any local users won't need to Authenticate to send mail.

Also make sure your correct domain is in the Local section of Core config 

Yes you're right, outlook express sent e-mails properly. I guess I didn't bollux the syntax but I'm lacking enough knowledge. AFAIK, a proper telnet SMTP session operates like this as you can find as the first entry in a search engine:

helo hostname

mail from: sender@domain.com

rcpt to: recipient@example.com 

data

"write down Subject, To, Cc, mail body here"

<crlf>.<crlf>

 Should I read all the RFC821 :S

Thanks anyway,

Ustun 

[quote user="houston"]

Yes you're right, outlook express sent e-mails properly. I guess I didn't bollux the syntax but I'm lacking enough knowledge. AFAIK, a proper telnet SMTP session operates like this as you can find as the first entry in a search engine:

helo hostname

mail from: sender@domain.com

rcpt to: recipient@example.com 

data

"write down Subject, To, Cc, mail body here"

<crlf>.<crlf>

 Should I read all the RFC821 :S

Thanks anyway,

Ustun 

[/quote]

IAW the RFC the MAIL FROM: and RCPT TO: addresses must be in <>.  The message ends with a period<CR><LF>  Here's a WinPMail SMTP (not ESMTP) session log showing the entire operation using old email addresses from a ISP that not longer exists.