[quote user="kannanEswar"]

Hi PaulW,

 Thanks for the reply.

1. When i am sending mail from program to exchange server (smtp.ihostexchange.net), working fine and email delivered successfully.[/quote]

ihostexchange.net appears to be a hosted Exchange service and not a server hosted on your network - is that correct? 

[quote]My need is i want to send emails to users from C# program using mercury service instead of exchange server.[/quote]

Are these users local (on the same network as the server) or remote (on the internet)?

If local - you will have to maintain accounts for them on the server, but how are they going to collect them from Mercury? POP3 ? IMAP ?

If remote - you can either open your router ports up so they can collect like local users above, or use MercuryC with a relay server to deliver them over the internet.  (The second option is probably easier to set up and requires less maintenance.)

[quote]2.  I have setup the user with name "websupport". And also predefined user admin is present there.

             From email address: support@mydomain.com

             To email address:  kannan@mydomain.com [/quote]

You are using 2 local names (support & kannan) but you have defined completely different names (websupport & admin).  What's going on?  Is mydomain.com the domain name in "local domains" section of the configuration?  If so, each and every name you use must be set up as a local user.

On a general point it is very difficult to help you if you obscure the actual user and domain information and don't explain the configuration you are using.  I suggest you use the extensive help that is provided in the program and read the relevant sections of the manual you will find in the Mercury\docs sub-directory.  Then if there are any specific items that are not clear, ask a question about that item.  Configuring and maintaining a mailserver for a non-standard installation can be a challenging and time-consuming project, and requires complete understanding of all the elements of email handing and network architecture.

Hi,

I have installed mercury 32 service in windows 2008 R2 server. When i start the service, i received the below exception in Event logger,

•  The Mercury32 service is marked as an interactive service.  However, the system is configured to not allow interactive services.  This service may not function properly.
• A timeout was reached (30000 milliseconds) while waiting for the Mercury32 service to connect.
• The Mercury32 service failed to start due to the following error:
  The service did not respond to the start or control request in a timely fashion.
• Windows could not start the service on on Local Computer
• Error 1053: The service did not respond to the start control request in a timely fashion

could you please let me know what i did wrongly?

Thanks in advance.

It could be that the license file isn't correctly installed, or that there is a specific Windows policy active that somehow prevents interactive services from running.

Hi Rolf,

Thanks for the update.

I want to run mercury 32 as a windows service on my windows2008 R2 server.

And i going to use this service for sending email from my C# program. My email server is Microsoft Exchange server.

And i have unchecked  the "Allow service to interact with desktop"  check-box in windows service properties log-on tab. Please address me to resolve this issue.

Thanks.

If the Mercury license is correctly installed you should be able to run the program as a service. Note though that Mercury needs full write access to its main folder and all sub-folders, which means it can't be located the Program Files folders in newer versions of Windows.

If you are running Exchange on the same server there will presumably be problems with binding to the ports that normally are used for email handling. 

Hi,

We have purchased the license. I have installed service in

windows server 2008, and  I have successfully run the service and able

to send email.

 We have migrated our server to windows azure 2012

server. So, i have installed the  service in azure machine, and i have

set port  to 250. When sending email from program i am getting the below

exception.

 {"A connection attempt failed because the

connected party did not properly respond after a period of time, or

established connection failed because connected host has failed to

respond ip:250"}

Can you please help me to resolve this error.

Thanks,

Port 250 isn't commonly used for any email protocol, and I don't really understand how this is configured on your server. MercuryS will need port 25 to work. If you provide more details we might be able to figure it out.

Hi Rolf,

I have changed the port number to 25, and i enabled smtp port 25 in azure server. But still i receiving the same error.

Regards,

Kannan E.

Can you see in MercuryS logs if any connection ever gets through to Mercury? If not make sure Mercury is listening on all network interfaces (in MercuryS settings), and check that there isn't any firewall software that blocks access.

Hi Rolf,

 Thanks for the update.

I have checked, none of the MercuryS logs are present. I have set TCP/IP port as 25 in mercury setting. is i need to make any changes in relaying control of mercury setting?

I have added endpoint for smtp(25)  in windows azure virtual machine and added inbound rules for smtp(TCP-25) in windows firewall.  But still there is no success.  

Regards,

KannanEswar.

If there was a relaying problem of some kind the connection would still be listed in the logs, so this is on another level. However, check in Configuration / MercuryS SMTP Server that "IP Interface to use" is blank, so that MercuryS will listen on all available networks. Restart Mercury if you make a change here.

If that didn't solve it, try to make a Telnet connection to the server (telnet <address> 25) and see what happens. 

Hi Rolf,

 I have  restarted mercury service and smtp service. now i got the below exception. And i checked the log still there is no file.

 Mailbox unavailable. The server response was: 5.7.1 Unable to relay for  abc.com

Regards,

KannanEswar.

If there is some other service running that binds to port 25 connections won't reach Mercury. The message you quoted doesn't look like it originated from Mercury.

Hello, I do not have a direct touch on a Windows 2012 server but it looks like you are running at the same time the native (Microsoft) SMTP service and Mercury.(you said u started mercury service and smtp service)

Either Mercury or Microsoft native SMTP service can run at the same time on the same IP on port 25.   Mercury do include its own SMTP server module so guess u have to stop/disable the Microsoft SMTP server to have Mercury one working. 

If you need to have both of them working (because maybe some application running on the server is using MS one) then you have to add an ip to the network interface and explicitly bind Mercury or the MS one on this new ip and the other to original IP.

Having two SMTP servers on the same machine  anyway means that you have to differentiate mail domains and properly set MX records for these domain in order to point to the corresponding SMTP server.

 Last hint: double check windows firewall settings.. receiving mails means having a TCP port in listen mode and default configurations usually tend to block all listening ports.

Hope it helps.

Best regards

Giorgio

Is it an option to configure your C# program to use an alternate port with MercuryS configured accordingly?  This comes to mind because we closed port 25 in our firewall because of dictionary attacks and now use an alternate port for relay access by our remote salespeople.

Hi,

Previously i have started both

native SMTP services and mercury service. Now i have stopped the native

SMTP services. Now i got "Remote server unable to connect exception". When i am installing mercury service, i have selected only smtp service.

Is i need to install mercury client too?

Thanks,

KannanEswar.

[quote user="kannanEswar"]

Hi,

Previously i have started both native SMTP services and mercury service. Now i have stopped the native SMTP services. Now i got "Remote server unable to connect exception". When i am installing mercury service, i have selected only smtp service.[/quote]

Please be more detailed in what test you are doing and where these messages are produced.

Have you tried the manual "telnet" test that was mentioned some days ago?

[quote]Is i need to install mercury client too? [/quote]

You will eventually need to install an outgoing module if you want the emails to go onto the internet.

Hi PaulW,

Thanks for the update. I have installed the client. I got no exception. Still mail not arrived to my mailbox. Please find the email sender code below.

////////////////////////

SmtpClient s;
MailMessage msg;

s = new SmtpClient();
msg = new MailMessage();
s.Port = 250;
s.Host = "server address";
s.UseDefaultCredentials = true;
s.Credentials = new NetworkCredential("username", "password");
s.EnableSsl = false;          
msg.IsBodyHtml = true;
msg.Body = "hello ";
msg.Subject = "website";
msg.To.Add("to  address");
msg.From = new MailAddress("from address");
s.Send(msg);

/////////////////////////

And in the mercury s log folder i got the below messages,

 Connection from ip address
EHLO ***********
AUTH login ************
MAIL FROM:<from address>
RCPT TO:<to address>
DATA
DATA - 10 lines, 239 bytes.
Connection closed with 'ip address', 13 sec. elapsed.

======================================

Regards,

Kannan E.

[quote user="kannanEswar"]

Hi PaulW,

Thanks for the update. I have installed the client. I got no exception. Still mail not arrived to my mailbox. Please find the email sender code below.[/quote]

As I wrote before, you are not giving us enough information to help you.  Please post your Mercury.ini file. Which protocol modules exactly are you running?  What mailbox are you referring to - a Mercury mailbox, or another internal one, or an external internet one?

[quote]And in the mercury s log folder i got the below messages,

 Connection from ip address
EHLO ***********
AUTH login ************
MAIL FROM:<from address>
RCPT TO:<to address>
DATA
DATA - 10 lines, 239 bytes.
Connection closed with 'ip address', 13 sec. elapsed.[/quote]

Well that's a standard SMTP transaction which shows the message succesfully delivered by MercuryS.  What happened next?  The Mercury core window will show you.

Hi PaulW,

I am using the following protocol module,

- MercuryS SMTP server

- MercuryC SMTP relaying client

- MercuryD distributing pop3 client

============================

 Mailbox  -- Outlook

==============================

Please find the mercury.ini file below.

 =============================================

#  MERCURY.INI generated by Mercury Setup
#
#
#  Sample Bindery Mode / Standalone Mode MERCURY.INI file.
#  This sample file implements most of the possible switches for each
#  module, but you can edit it to do less if you wish.
#
#  Anything after a '#' to the end of the line is a comment and
#  is stripped out before parsing. Trailing and leading whitespace
#  is also stripped before parsing. Many sample commands have been
#  left in this file commented out for reference purposes.
#
#  Note that in general, manual modification of this file is NOT
#  RECOMMENDED - use the Mercury "Configuration" menu to change the
#  program's settings wherever possible.
#

[General]
myname:          ******.**********.*********    # Canonical name for this server
timezone:        +0000    # Time Zone to add to date fields
file_api:        1    # Use the file api instead of queues
mailqueue:       C:\MERCURY\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\MERCURY\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\MERCURY\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
C:\MERCURY\mercurys.dll
C:\MERCURY\mercuryc.dll
C:\MERCURY\mercuryd.dll


[Mercury]
failfile:      C:\MERCURY\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   C:\MERCURY\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     C:\MERCURY\Mercury\ALIAS.MER    # System-wide alias file
synfile:       C:\MERCURY\Mercury\SYNONYM.MER    # User synonym database
listfile:      C:\MERCURY\Mercury\LISTS.MER    # List of lists
logfile:       C:\MERCURY\Logs\Core\~y-~m-~d.log    # Traffic logging file
logwidth:      30    # Width of address fields in logfile
retpath:       1    # Do/Don't use 'return-path' for errors
maxhops:       30    # Used to detect mailing loops
gullible:      0    # If NZ, don't validate 'From' fields
poll:          10   # Seconds between queue polling cycles
scratch:       C:\MERCURY\Scratch    # Where we can write temp files
returnlines:   15    # How many lines of failed messages to return
postmaster:    Admin    # NetWare UIC of postmaster
broadcast:     1    # Yes, we want broadcast notifications, but
receipts:      0    # ... no broadcasts for receipt confirmations
PM_notify:     1    # Do/Don't send errors to the postmaster
change_owner:  1    # Change message ownership to recipient
auto_tzone:    1    # If NZ, obtain timezone information from OS
LogLevel:      15    # System message reporting level
LogMax:        100    # Maximum number of system messages to store
RetryPeriod:   30    # Period between job retries (minutes)
MaxRetries:    16    # Maximum number of times a job can fail
TwoPasses:     1    # If NZ, process submission queue in 2 passes
Autoaddress:   0    # If NZ, auto-generate user addresses based on name
Daily_exit:    0    # If NZ, auto-restart each day after maintenance
No_Areply:     0    # If NZ, disable automatic replies system-wide
Alt_Forward:   0    # If NZ, allow alternate forwarding specification
Maint_hour:    2    # Hour for daily maintenance (24-hour clock)
Maint_min:     0    # Minute for daily maintenance
Retry_Mode:    0    # If NZ, use progressive backoff for queue retries
Local_DSNs:    1    # If NZ generate Delivery Status for local users only
DSN_time1:     10800    # Seconds deferred before first DSN is sent
DSN_time2:     86400    # Seconds deferred before second DSN is sent
DSN_time3:     259200    # Seconds deferred before third DSN is sent
Host_in_title: 0    # If NZ, show hostname in system tray and taskbar
Lingering:     0    # Enable or disable 'lingering mailboxes'
Linger_Timeout: 60   # Seconds before a lingering mailbox is shut down
Alert_Host:    notify.pmail.com    # Host to check for licensee advisories
Alert_Interval: 720   # Frequency in minutes (min 240) for checks
Alert_Flags:   3    # Flags controlling advisory checks

[MercuryC]
logfile : C:\MERCURY\Logs\MercuryC\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\MERCURY\Sessions\MercuryC\    # Directory for session log files
Session_logmode : 0
host:             # mail mail host which relays for us
scratch:     C:\MERCURY\scratch           # Where we can write temp files
poll:        30                   # Seconds between queue polling cycles
returnlines: 15                   # How many lines of failed messages to return
failfile:    C:\MERCURY\Mercury\FAILURE.MER  # Delivery failure template
esmtp:       1                    # Yes, we want to use ESMTP extensions

[MercuryE]
Poll : 15
Timeout : 60
logfile : C:\MERCURY\Logs\MercuryE\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\MERCURY\Sessions\MercuryE\   # Directory for session log files
Session_logmode : 0
# Nameservers : 139.80.64.1

[MercuryD]
Session_logging : C:\MERCURY\Sessions\MercuryD\    # Directory for session log files
Session_logmode : 0
Scratch : C:\MERCURY\Scratch\MercuryD
# Timeout : 30
# Poll : 120               # How often to check hosts for new mail (seconds)

[MercuryS]
Debug : 1
Logfile : C:\MERCURY\Logs\MercuryS\~y-~m-~d.log
Timeout : 30
Relay : 0
Strict_Relay : 1
Server_Port : 250
Allow_Illegals : 0
SMTP_Authentication : 3
Auth_File : c:\mercury\auth
Session_logging : C:\MERCURY\Sessions\MercuryS
Session_logmode : 0
Compliance_Settings : 0
Maximum_Failed_Rcpts : 4
Max_Relay_Attempts : 4
SSL_Mode : 0
ST_Blacklisting : 288
No_VRFY : 0
SMTP_ConnFlags : 0

[MercuryP]
logfile : C:\MERCURY\Logs\MercuryP\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\MERCURY\Sessions\MercuryP\   # Directory for session log files
Session_logmode : 0
Scratch : C:\MERCURY\Scratch\MercuryP
Timeout : 60
UIDL_nul_list : 1
New_UIDs : 1
No_NUL_passwords : 1

[MercuryX]
Drain_queues: 1
# Cmd_Delay: 10
# Cmd_Wait: 1
# IE4_Dialling: 0
# Use_ETRN: 1
# Clients_only: 1
# Sunday: 0800,1800,3,15,30,60
# Monday: 0830,2100,5,15,60,60
# Tuesday: 0830,2100,5,15,60,60
# Wednesday: 1500,1900,2,30,5,30
# Thursday: 0900,1900,2,30,0,0
# Friday: 0830,2100,5,15,60,60
# Saturday: 1031,1035,2,45,-1,0

# [Groups]
# testgroup            :     TESTGRP

[Domains]
******: ******
******: ******.**********.*********

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        C:\MERCURY\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\MERCURY\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\MERCURY\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         C:\MERCURY\Logs\Maiser\~y-~m-~d.LOG   # Mail server log file
Notify:          C:\MERCURY\Mercury\TMP   # Dir. for pending 'notify' commands
NoList:          N   # If 'Y', disable the 'list' command
Local_only:      Y   # If 'Y', local 'notify' commands only

[MercuryH]
logfile : C:\MERCURY\Logs\MercuryH\~y-~m-~d.log   # Traffic logging file
# Addressbook : \\CLIO\SYS\SYSTEM\MERCURY\PH.PMR
# MOTD : \\CLIO\SYS\SYSTEM\MERCURY\PH-MOTD.TXT
# Administrator : postmaster@clio.pmail.gen.nz
Timeout : 30

[MercuryI]
Scratch : C:\MERCURY\Scratch\MercuryI
logfile : C:\MERCURY\Logs\MercuryI\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\MERCURY\Sessions\MercuryI\   # Directory for session log files
Session_logmode : 0
Timeout : 120
Server_Port : 143
Idle_Timeout : 1800

[MercuryB]
Scratch : C:\MERCURY\Scratch\MercuryB
logfile : C:\MERCURY\Logs\MercuryB\~y-~m-~d.log   # Traffic logging file
Session_logging : C:\MERCURY\Sessions\MercuryB\   # Directory for session log files
Session_logmode : 0
Timeout : 120
Server_Port : 80
Idle_Timeout : 1800
# URL_Base : enter_your_domain_here

[Groups]

[Rewrite]

[Statistics]
StatFlags:    0  # Statistical reporting settings
STF_Hours:    24  # How often to write stat log files
STM_Hours:    24  # How often to e-mail stat log files

==============================================================

Regards,

Kannan e.