cant receive mail but can send

ruler

posted Jun 6 '16 at 2:52 pm

the website i have was just a basic website written in php and html from the web with no registration functionality at all. i downloaded from github a registration script that contained several files and a mysql db. it all works fine and it used to work ok with mandrill which was a free mail relay service but they started charging for the service so i thought maybe it was better to use the inbuilyt mercury mail since that was what it was there for.

i wanted one account for example (a private email for myself) and i wanted another email account to handle sending confirmation/register emails when someone registers on the site or if they forget a login password it can send them an email with their details. It is really not going to be used for anything complex at all just mostly handling registration stuff only.

the website i have was just a basic website written in php and html from the web with no registration functionality at all. i downloaded from github a registration script that contained several files and a mysql db. it all works fine and it used to work ok with mandrill which was a free mail relay service but they started charging for the service so i thought maybe it was better to use the inbuilyt mercury mail since that was what it was there for.i wanted one account for example (a private email for myself) and i wanted another email account to handle sending confirmation/register emails when someone registers on the site or if they forget a login password it can send them an email with their details. It is really not going to be used for anything complex at all just mostly handling registration stuff only.&nbsp;

ruler

posted May 26 '16 at 4:40 pm

hi everyone

I am having some issues receiving mail after setting up mercury mail but can seem to send out mail fine.

I am running it on windows 10 x86 and ports 25, 143, 110 and 443 have been opened and rules applied in my AVG firewall.

here is a copy of my ini file below...

# MERCURY.INI generated by Mercury Setup
#
#
# Sample Bindery Mode MERCURY.INI file (in fact, the one I use on
# my production server). This one implements most of the possible
# switches for each module, but you can edit it to do less if you
# wish. All the fields shown below are described in the file
# MGUIDE.HLP which is supplied in the Mercury archive.
#
# 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.
#

[General]
myname:          localhost    # 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:\XAMPP\MERCURYMAIL\QUEUE    # Where mail should be put for delivery
smtpqueue:       C:\XAMPP\MERCURYMAIL\QUEUE    # Where the SMTP client should look for mail
newmail_path:    C:\XAMPP\MERCURYMAIL\MAIL\~N    # Where to find the users' WinPMail mailboxes.

[Protocols]
MERCURYS.DLL
MERCURYP.DLL
MERCURYE.DLL
# MERCURYC.DLL
MERCURYD.DLL
# MERCURYH.DLL
# MERCURYF.DLL
# MERCURYW.DLL
# MERCURYX.DLL
MERCURYI.DLL
# MERCURYB.DLL

[Mercury]
failfile:      C:\xampp\MERCURYMAIL\Mercury\FAILURE.MER    # Delivery failure notification template
confirmfile:   C:\xampp\MERCURYMAIL\Mercury\CONFIRM.MER    # Delivery confirmation template
aliasfile:     C:\xampp\MERCURYMAIL\Mercury\ALIAS.MER    # System-wide alias file
synfile:       C:\xampp\MERCURYMAIL\Mercury\SYNONYM.MER    # User synonym database
listfile:      C:\xampp\MERCURYMAIL\Mercury\LISTS.MER    # List of lists
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
bitnethost:    cunyvm.cuny.edu    # Relay host for '.bitnet' rewrites
poll:          10   # Seconds between queue polling cycles
scratch:       C:\xampp\MERCURYMAIL\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]
# Session_logging: G:\           # Directory to write session transcripts
host:             # mail mail host which relays for us
scratch:     C:\xampp\MERCURYMAIL\Mercury   # 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:\xampp\MERCURYMAIL\Mercury\FAILURE.MER # Delivery failure template
esmtp:       1                    # Yes, we want to use ESMTP extensions

[MercuryE]
Poll : 15
Timeout : 60
Nameservers : 208.67.222.222,208.67.220.220
Log_Verbose : 0
DNS_Timeout : 20
DNS_Retries : 4
Transcripts : 1
MaxThreads : 10

[MercuryD]
scratch              :     C:\xampp\MERCURYMAIL\Mercury
# Timeout : 30
# Poll : 120               # How often to check hosts for new mail (seconds)

[MercuryS]
Debug : 1
Logfile : C:\xampp\MERCURYMAIL\Logs\MERCURYS.LOG
Timeout : 30
Relay : 1
Strict_Relay : 0
Interface : 127.0.0.1
Allow_Illegals : 0
SMTP_Authentication : 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]
Scratch : C:\xampp\MERCURYMAIL\Mercury
Stack : 32768
Mark_Read : 1
SSL_Mode : 0
Login_Disabled : 0
UIDL_nul_list : 1
New_UIDs : 0
No_NUL_passwords : 1
Timeout : 60

[MercuryX]
# 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]
localhost: localhost
localhost: 127.0.0.1
localhost: finchkeeper.com

[Maiser]
Maiser:          Maiser   # 'Username' of mail server account
Helpfile:        C:\xampp\MERCURYMAIL\Mercury\MAISER.HLP   # Help sent on failed maiser requests
Lookupfile:      C:\xampp\MERCURYMAIL\Mercury\MAISER.LKP   # Format file for the 'lookup' command
Send_dir:        C:\xampp\MERCURYMAIL\Mercury\SENDABLE   # Directory for the 'send' command
Logfile:         C:\xampp\MERCURYMAIL\Logs\MAISER.LOG   # Mail server log file
Notify:          C:\xampp\MERCURYMAIL\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:\xampp\MERCURYMAIL\Logs\MERCURYH.LOG
# 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:\xampp\MERCURYMAIL\SCRATCH
Timeout : 120
Server_Port : 143
Idle_Timeout : 1800
SSL_Mode : 0
Login_Disabled : 0
No_NUL_passwords : 1

[MercuryB]
Scratch : C:\xampp\MERCURYMAIL\SCRATCH
# Logfile : o:\mail\tmp\mercuryb.log
Timeout : 120
Server_Port : 2224
# Session_logging : o:\mail\mercury\mblogs
# Session_logmode : 0
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

any help would be much appreciated, thanks

hi everyoneI am having some issues receiving mail after setting up mercury mail but can seem to send out mail fine.&nbsp;I am running it on windows 10 x86 and ports 25, 143, 110 and 443 have been opened&nbsp; and rules applied in my AVG firewall.here is a copy of my ini file below...&nbsp;&nbsp;#&nbsp; MERCURY.INI generated by Mercury Setup # # #&nbsp; Sample Bindery Mode MERCURY.INI file (in fact, the one I use on #&nbsp; my production server). This one implements most of the possible #&nbsp; switches for each module, but you can edit it to do less if you #&nbsp; wish. All the fields shown below are described in the file #&nbsp; MGUIDE.HLP which is supplied in the Mercury archive. # #&nbsp; Anything after a '#' to the end of the line is a comment and #&nbsp; is stripped out before parsing. Trailing and leading whitespace #&nbsp; is also stripped before parsing. Many sample commands have been #&nbsp; left in this file commented out for reference purposes. # [General] myname:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; localhost&nbsp;&nbsp;&nbsp; # Canonical name for this server timezone:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +0000&nbsp;&nbsp;&nbsp; # Time Zone to add to date fields file_api:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Use the file api instead of queues mailqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\XAMPP\MERCURYMAIL\QUEUE&nbsp;&nbsp;&nbsp; # Where mail should be put for delivery smtpqueue:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\XAMPP\MERCURYMAIL\QUEUE&nbsp;&nbsp;&nbsp; # Where the SMTP client should look for mail newmail_path:&nbsp;&nbsp;&nbsp; C:\XAMPP\MERCURYMAIL\MAIL\~N&nbsp;&nbsp;&nbsp; # Where to find the users' WinPMail mailboxes. [Protocols] MERCURYS.DLL MERCURYP.DLL MERCURYE.DLL # MERCURYC.DLL MERCURYD.DLL # MERCURYH.DLL # MERCURYF.DLL # MERCURYW.DLL # MERCURYX.DLL MERCURYI.DLL # MERCURYB.DLL [Mercury] failfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\FAILURE.MER&nbsp;&nbsp;&nbsp; # Delivery failure notification template confirmfile:&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\CONFIRM.MER&nbsp;&nbsp;&nbsp; # Delivery confirmation template aliasfile:&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\ALIAS.MER&nbsp;&nbsp;&nbsp; # System-wide alias file synfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\SYNONYM.MER&nbsp;&nbsp;&nbsp; # User synonym database listfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\LISTS.MER&nbsp;&nbsp;&nbsp; # List of lists logwidth:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp; # Width of address fields in logfile retpath:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Do/Don't use 'return-path' for errors maxhops:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp; # Used to detect mailing loops gullible:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, don't validate 'From' fields bitnethost:&nbsp;&nbsp;&nbsp; cunyvm.cuny.edu&nbsp;&nbsp;&nbsp; # Relay host for '.bitnet' rewrites poll:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 10&nbsp;&nbsp; # Seconds between queue polling cycles scratch:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Scratch&nbsp;&nbsp;&nbsp; # Where we can write temp files returnlines:&nbsp;&nbsp; 15&nbsp;&nbsp;&nbsp; # How many lines of failed messages to return postmaster:&nbsp;&nbsp;&nbsp; Admin&nbsp;&nbsp;&nbsp; # NetWare UIC of postmaster broadcast:&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Yes, we want broadcast notifications, but receipts:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # ... no broadcasts for receipt confirmations PM_notify:&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # Do/Don't send errors to the postmaster change_owner:&nbsp; 1&nbsp;&nbsp;&nbsp; # Change message ownership to recipient auto_tzone:&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # If NZ, obtain timezone information from OS LogLevel:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 15&nbsp;&nbsp;&nbsp; # System message reporting level LogMax:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 100&nbsp;&nbsp;&nbsp; # Maximum number of system messages to store RetryPeriod:&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp; # Period between job retries (minutes) MaxRetries:&nbsp;&nbsp;&nbsp; 16&nbsp;&nbsp;&nbsp; # Maximum number of times a job can fail TwoPasses:&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # If NZ, process submission queue in 2 passes Autoaddress:&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, auto-generate user addresses based on name Daily_exit:&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, auto-restart each day after maintenance No_Areply:&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, disable automatic replies system-wide Alt_Forward:&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, allow alternate forwarding specification Maint_hour:&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp;&nbsp; # Hour for daily maintenance (24-hour clock) Maint_min:&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # Minute for daily maintenance Retry_Mode:&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # If NZ, use progressive backoff for queue retries Local_DSNs:&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp; # If NZ generate Delivery Status for local users only DSN_time1:&nbsp;&nbsp;&nbsp;&nbsp; 10800&nbsp;&nbsp;&nbsp; # Seconds deferred before first DSN is sent DSN_time2:&nbsp;&nbsp;&nbsp;&nbsp; 86400&nbsp;&nbsp;&nbsp; # Seconds deferred before second DSN is sent DSN_time3:&nbsp;&nbsp;&nbsp;&nbsp; 259200&nbsp;&nbsp;&nbsp; # Seconds deferred before third DSN is sent Host_in_title: 0&nbsp;&nbsp;&nbsp; # If NZ, show hostname in system tray and taskbar Lingering:&nbsp;&nbsp;&nbsp;&nbsp; 0&nbsp;&nbsp;&nbsp; # Enable or disable 'lingering mailboxes' Linger_Timeout: 60&nbsp;&nbsp; # Seconds before a lingering mailbox is shut down Alert_Host:&nbsp;&nbsp;&nbsp; notify.pmail.com&nbsp;&nbsp;&nbsp; # Host to check for licensee advisories Alert_Interval: 720&nbsp;&nbsp; # Frequency in minutes (min 240) for checks Alert_Flags:&nbsp;&nbsp; 3&nbsp;&nbsp;&nbsp; # Flags controlling advisory checks [MercuryC] # Session_logging:&nbsp; G:\&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # Directory to write session transcripts host:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # mail mail host which relays for us scratch:&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury&nbsp;&nbsp; # Where we can write temp files poll:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 30&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # Seconds between queue polling cycles returnlines: 15&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # How many lines of failed messages to return failfile:&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\FAILURE.MER&nbsp; # Delivery failure template esmtp:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # Yes, we want to use ESMTP extensions [MercuryE] Poll : 15 Timeout : 60 Nameservers : 208.67.222.222,208.67.220.220 Log_Verbose : 0 DNS_Timeout : 20 DNS_Retries : 4 Transcripts : 1 MaxThreads : 10 [MercuryD] scratch&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury # Timeout : 30 # Poll : 120&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; # How often to check hosts for new mail (seconds) [MercuryS] Debug : 1 Logfile : C:\xampp\MERCURYMAIL\Logs\MERCURYS.LOG Timeout : 30 Relay : 1 Strict_Relay : 0 Interface : 127.0.0.1 Allow_Illegals : 0 SMTP_Authentication : 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] Scratch : C:\xampp\MERCURYMAIL\Mercury Stack : 32768 Mark_Read : 1 SSL_Mode : 0 Login_Disabled : 0 UIDL_nul_list : 1 New_UIDs : 0 No_NUL_passwords : 1 Timeout : 60 [MercuryX] # 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&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; TESTGRP [Domains] localhost: localhost localhost: 127.0.0.1 localhost: finchkeeper.com [Maiser] Maiser:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Maiser&nbsp;&nbsp; # 'Username' of mail server account Helpfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\MAISER.HLP&nbsp;&nbsp; # Help sent on failed maiser requests Lookupfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\MAISER.LKP&nbsp;&nbsp; # Format file for the 'lookup' command Send_dir:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\SENDABLE&nbsp;&nbsp; # Directory for the 'send' command Logfile:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Logs\MAISER.LOG&nbsp;&nbsp; # Mail server log file Notify:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Mercury\TMP&nbsp;&nbsp; # Dir. for pending 'notify' commands NoList:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; N&nbsp;&nbsp; # If 'Y', disable the 'list' command Local_only:&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Y&nbsp;&nbsp; # If 'Y', local 'notify' commands only [MercuryH] Logfile&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; :&nbsp;&nbsp;&nbsp;&nbsp; C:\xampp\MERCURYMAIL\Logs\MERCURYH.LOG # 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:\xampp\MERCURYMAIL\SCRATCH Timeout : 120 Server_Port : 143 Idle_Timeout : 1800 SSL_Mode : 0 Login_Disabled : 0 No_NUL_passwords : 1 [MercuryB] Scratch : C:\xampp\MERCURYMAIL\SCRATCH # Logfile : o:\mail\tmp\mercuryb.log Timeout : 120 Server_Port : 2224 # Session_logging : o:\mail\mercury\mblogs # Session_logmode : 0 Idle_Timeout : 1800 # URL_Base : enter_your_domain_here [Groups] [Rewrite] [Statistics] StatFlags:&nbsp;&nbsp;&nbsp; 0&nbsp; # Statistical reporting settings STF_Hours:&nbsp;&nbsp;&nbsp; 24&nbsp; # How often to write stat log files STM_Hours:&nbsp;&nbsp;&nbsp; 24&nbsp; # How often to e-mail stat log files &nbsp;any help would be much appreciated, thanks

Greenman

posted May 26 '16 at 5:44 pm

How are your MX records configured?

ruler

posted May 26 '16 at 6:03 pm

where would i find those?

Greenman

posted May 26 '16 at 6:27 pm

[quote user="ruler"]where would i find those?
[/quote]

I've jumped the gun - how are you getting mail delivered to Mercury/32? Are you using a forwarding rule from your domain(s) that points at your public IP address? Are you using a third party filtering service etc Have you defined the domains in the Mercury Core Module?

You need to describe your setup a bit more.

[quote user="ruler"]where would i find those? [/quote]I've jumped the gun - how are you getting mail delivered to Mercury/32? Are you using a forwarding rule from your domain(s) that points at your public IP address? Are you using a third party filtering service etc Have you defined the domains in the Mercury Core Module?You need to describe your setup a bit more.

ruler

posted May 26 '16 at 6:36 pm

ok first i will explain.

i am running it at home on my one and only home computer with windows 10 (x86).

I really only want it for registration for my website for now.

all ports have been configured correctly and all allowed in the firewall.

i login using Mozilla Thunderbird and send an email to my hotmail account and the message is received by hotmail perfectly. If i reply from hotmail i dont get the email but i get a delivery error in hotmail telling me the mail could not be delivered.

i am a complete novice with mail servers so i did expect a few problems :) i did post my mercury.ini above which should show all my settings however i have probably changed one or two since posting it.

ok first i will explain. i am running it at home on my one and only home computer with windows 10 (x86).&nbsp;I really only want it for registration for my website for now. all ports have been configured correctly and all allowed in the firewall.i login using Mozilla Thunderbird and send an email to my hotmail account and the message is received by hotmail perfectly. If i reply from hotmail i dont get the email but i get a delivery error in hotmail telling me the mail could not be delivered. i am a complete novice with mail servers so i did expect a few problems :) i did post my mercury.ini above which should show all my settings however i have probably changed one or two since posting it.&nbsp;

ruler

posted May 26 '16 at 6:54 pm

I just noticed something when looking through my www directory, there is a folder called classes that contain the files...

mail.php

phpmailer.php

pop3.php

smtp.php

exception.php

when someone registers on the site or forgets their password it usually uses those files and in the mail.php i usually have to configure one of those free mailing services like Mandrill.

I'd rather not use all of that and would prefer to use mercury mail for the registration if it is possible? im not sure if it would work or not

I just noticed something when looking through my www directory, there is a folder called classes that contain the files...mail.phpphpmailer.phppop3.phpsmtp.phpexception.phpwhen someone registers on the site or forgets their password it usually uses those files and in the mail.php i usually have to configure one of those free mailing services like&nbsp; Mandrill. I'd rather not use all of that and would prefer to use mercury mail for the registration if it is possible? im not sure if it would work or not

Greenman

posted May 26 '16 at 8:56 pm

Can you post the error message you get from the delivery status notification. When we see that we'll have a much better idea of what is going on.

Can you post the error message you get&nbsp;from the delivery status notification. When we&nbsp;see that we'll have a much better idea of what is going on.&nbsp; &nbsp;

ruler

posted May 26 '16 at 9:22 pm

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

       dion@finchkeeper.com

--Forwarded Message Attachment--
From: dion2u2002@hotmail.com
To: dion@finchkeeper.com
Subject: running test
Date: Thu, 26 May 2016 14:37:58 +0100

hello!

<pre>This is an automatically generated Delivery Status Notification. Delivery to the following recipients failed. dion@finchkeeper.com </pre> --Forwarded Message Attachment-- From: dion2u2002@hotmail.com To: dion@finchkeeper.com Subject: running test Date: Thu, 26 May 2016 14:37:58 +0100 <div dir="ltr">hello! </div>

Greenman

posted May 26 '16 at 9:34 pm

Your best bet would be to speak to your domain registrar's support people and make sure you have your mail set up properly. Tell them you wish to manage your mail accounts on your own computer using mail server software. Note that for someone not familiar with SMTP this is not a trivial task and there is a lot you need to learn and understand.

Once you get that verified then we can make more positive suggestions.

Your best bet would be to speak to your domain registrar's support people and make sure you have your mail set up properly. Tell them you wish to manage your mail accounts on your own computer using mail server software. Note that for someone not familiar with SMTP this is not a trivial task and there is a lot you need to learn and understand.Once you get that verified then we can make more positive suggestions.&nbsp;

ruler

posted May 26 '16 at 9:45 pm

if you are referring to my domain name provider that would be Go Daddy, will ask them this evening and will post back here once they help me out.

thanks for your help it is much appreciated

if you are referring to my domain name provider that would be Go Daddy, will ask them this evening and will post back here once they help me out.thanks for your help it is much appreciated

bfluet

posted May 26 '16 at 9:50 pm

FWIW, when I set up Mercury for the small business I work for I opted to have our domain host host the user mailboxes and to use MercuryD to retrieve mail from those mailboxes. I did so because I was, and remain, ignorant of the complexities of SMTP to which Greenman refers. In this case Mercury wasn't a necessity but it gives me enterprise wide control over mailboxes, AV scanning, and Spam filtering.

I do not run any mailing lists so did not care about that capability in Mercury.

FWIW, when I set up Mercury for the small business I work for I opted to have our domain host host the user mailboxes and to use MercuryD to retrieve mail from those mailboxes.&nbsp; I did so because I was, and remain, ignorant of the complexities of SMTP to which Greenman refers.&nbsp; In this case Mercury wasn't a necessity but it gives me enterprise wide control over mailboxes, AV scanning, and Spam filtering.&nbsp; &nbsp;I do not run any mailing lists so did not care about that capability in Mercury.&nbsp;

ruler

posted May 26 '16 at 10:07 pm

ok back already :)

just spoke to them, they told me i can run a mail server here on my own computer and i do not need to make any adjustments on their site. they told me i just need to configure the server properly for it to work.

they told me my dns was setup properly and the mail side of it was not set and would have no effect on my sending or receiving mail on a home hosted mail server.

ok back already :)just spoke to them, they told me i can run a mail server here on my own computer and i do not need to make any adjustments on their site. they told me i just need to configure the server properly for it to work.they told me my dns was setup properly and the mail side of it was not set and would have no effect on my sending or receiving mail on a home hosted mail server.

ruler

posted May 26 '16 at 10:48 pm

ok just ran a port scan using an online network tool and it shows ports 25 and port 110 are being Refused (RST)

I am not sure why but they are forwarded correctly in my router and i even disabled the firewall but still the same results.mercury was running at the time of the test too. I have no idea what is going on and im just confused as to why this is happening.

ok just ran a port scan using an online network tool and it shows ports 25 and port 110 are being Refused (RST)I am not sure why but they are forwarded correctly in my router and i even disabled the firewall but still the same results.mercury was running at the time of the test too. I have no idea what is going on and im just confused as to why this is happening.

Greenman

posted May 27 '16 at 12:59 pm

I was going to suggest you do what Brian has suggested, and that is to use Mercury/32's POP3 module to retrieve email from your host, and then use MercuryC to relay via GoDaddy to deliver your mail.

Note that you need to set up a POP3 definition for each mailbox you have - how many do you have?

If you want to use SMTP all the way you will need to do a lot more than GoDaddy have told you. They have assumed they will retain control of the mail boxes. For you to assume control of the mail boxes means hosting them on your home computer, and, as I said above, that is no trivial task for someone who is new to SMTP - not because they will be on your home machine, but because of the DNS configuration required to authenticate your sending mail server, anti-spam measures you will need to take, and the on-going job of ensuring your home IP's reputation remains clean so that mail will be accepted from it.

Brian's suggestion is the safest and easiest method for you to use. You will need to configure POP3 so that it leaves a copy of the mail on the GoDaddy server. I recommend you ensure your mailboxes have appropriate storage so that several GB's can accumulate. This will allow you to log on to your GoDaddy service and delete old mail as required. If you are limited and you wish to keep all mail on your home computer then you must create daily backups of the Mercury/32 folder and your mail folders. Which mail client will you be using?

I was going to suggest you do what Brian has suggested, and that is to use Mercury/32's POP3 module to retrieve email from your host, and then use MercuryC to&nbsp;relay via&nbsp;GoDaddy to deliver your mail.Note that you need to set up a POP3 definition for each mailbox you have - how many&nbsp;do you have?&nbsp;If you want to use SMTP all the way&nbsp;you will need to do a lot more than GoDaddy have told you. They have assumed they will retain control of the mail boxes. For you to assume control of the mail boxes means hosting them on your home computer, and, as I said above, that is no trivial task for someone who is new to SMTP - not because they will be on your home machine, but because of the DNS configuration required to authenticate your sending mail server, anti-spam measures you will need to take, and the on-going job of ensuring your home IP's reputation remains clean so that mail will be accepted from it.Brian's suggestion is the safest and easiest&nbsp;method for you to use. You will need to configure POP3 so that&nbsp;it leaves a copy of the mail on the GoDaddy&nbsp;server. I recommend you ensure your mailboxes have appropriate storage so that several GB's can accumulate. This will allow you to log on to your GoDaddy service and delete old mail as required. If you are limited and you wish to keep all mail on your home computer then you must create daily backups of the Mercury/32 folder and your mail folders. Which mail client will you be using?&nbsp;

ruler

posted May 27 '16 at 6:25 pm

i have messed with smtp some years back a few times and i did manage to get this mercury working before (on the same ISP) but then i deleted my old website only to create a new one about a year later. i saved none of the old files so i had to start from scratch.i understand what you mean via pop3 server through GoDaddy but i would prefer to get it all working on here using the smtp on mercury.

Today i called my ISP and tried to find out if ports 25 and 110 were being blocked and they confirmed that they do not block ports so i definately know the problem is at my end. Ive run a few port checks using online tools and they just cant seem to see port 25 or 110 but all the other ports seem fine and opened. it is strange because on mercury where you start it on the control panel it shows 25,110, 143 as being used by mercury so im guessing it is only being seen by local network even though it can still send emails over the web.

The postmaster seems to work fine but if i try to create a local user ThunderBird will not let you add the account due to password or username being wrong but i think it is because it can not connect to the mercury server because of the ports issue. the odd thing is i had all this working when it was on windows 7 when it first come out, i should have kept all the configuration files.

i have messed with smtp some years back a few times and i did manage to get this mercury working before (on the same ISP) but then i deleted my old website only to create a new one about a year later. i saved none of the old files so i had to start from scratch.i understand what you mean via pop3 server through GoDaddy but i would prefer to get it all working on here using the smtp on mercury. Today i called my ISP and tried to find out if ports 25 and 110 were being blocked and they confirmed that they do not block ports so i definately know the problem is at my end. Ive run a few port checks using online tools and they just cant seem to see port 25 or 110 but all the other ports seem fine and opened. it is strange because on mercury where you start it on the control panel it shows 25,110, 143 as being used by mercury so im guessing it is only being seen by local network even though it can still send emails over the web.The postmaster seems to work fine but if i try to create a local user ThunderBird will not let you add the account due to password or username being wrong but i think it is because it can not connect to the mercury server because of the ports issue. the odd thing is i had all this working when it was on windows 7 when it first come out, i should have kept all the configuration files.

Greenman

posted May 27 '16 at 7:17 pm

Is your thunderbird client and Mercury/32 on the same machine?

Have you configured Thunderbird to use the IP address of the W10 machine running Mercury/32 when connecting to the mailbox?

Is your thunderbird client and Mercury/32 on the same machine?Have you configured Thunderbird to use the IP address of&nbsp;the W10 machine running Mercury/32 when connecting to the mailbox?&nbsp;

ruler

posted May 27 '16 at 7:52 pm

they are both on the same computer yes. I dont think i setup any IPs on ThunderBird and thought it was automatic. will have a look and see

Brian Fluet

posted May 27 '16 at 11:47 pm

[quote user="ruler"]they are both on the same computer yes. I dont think i setup any IPs on ThunderBird and thought it was automatic. will have a look and see
[/quote]

I am surprised to see this discussion jump to the email client since it doesn't appear that Mercury is able to receive messages yet. Wish I was knowledgeable enough to help with that

Regarding Thunderbird, AFAIK, if...

Thunderbird will be accessing the Mercury mailbox via IMAP
The Mercury protocol module MercuryI must be running and configured

or, if

Thunderbird will be retrieving messages from the Mercury mailbox via POP3
The Mercury protocol module MercuryP must be running and configured

If Pegasus Mail were the email client it could integrate with Mercury such that the Mercury mailbox and the Pegasus Mail mailbox would be one and the same. No MercuryI or MercuryP needed.

[quote user="ruler"]they are both on the same computer yes. I dont think i setup any IPs on ThunderBird and thought it was automatic. will have a look and see [/quote]I am surprised to see this discussion jump to the email client since it doesn't appear that Mercury is able to receive messages yet.&nbsp; Wish I was knowledgeable enough to help with that Regarding Thunderbird, AFAIK, if... <ul><li>Thunderbird will be accessing the Mercury mailbox via IMAP</li><li>The Mercury protocol module MercuryI must be running and configured </li></ul>&nbsp;or, if <ul><li>Thunderbird will be retrieving messages from the Mercury mailbox via POP3</li><li>The Mercury protocol module MercuryP must be running and configured </li></ul>If Pegasus Mail were the email client it could integrate with Mercury such that the Mercury mailbox and the Pegasus Mail mailbox would be one and the same.&nbsp; No MercuryI or MercuryP needed.&nbsp;

Greenman

posted May 28 '16 at 12:56 pm

Can Thunderbird download and send mail directly from/to your domain? (i.e. without the need to connect to Mercury)

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history