[quote user="forum user"]
"mydomain" isnt mine. i have "oapplications" the domain name.[/quote]
Which means you should not use "mydomain" as an example.  There IS a domain which is maintained for precisely this purpose, and it is called (surprisingly enough...) "example.com".

[quote]i changed and now i have as bellow:

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:\MAIL\~n    # Where to find the users' WinPMail mailboxes.
[/quote]
So far, so good.

[quote]i added in Mercury at "Manage local users..." a user,"mail".[/quote]
Do you have something against using sensible user-account names?  How is "mail" supposed to distinguish between various users (or various role accounts, for that matter)?

[quote]i see in C:\MAIL\   the mail folder and PMAIL.USR file.[/quote]
Do you mean to say that the PMAIL.USR file is actually in ~/MERCURY/MAIL/ and not in ~/MERCURY/MAIL/MAIL/ ?  If so, that is potentially a problem, especially when you go to add additional user accounts.

[And as a side note...  Yes, you WILL need to add additional user accounts, even if for nothing else besides "postmaster@..." and "abuse@...", both of which are required by the relevant RFCs for any domain which sends or receives mail.  If you operate a web site, you probably also ought to have "webmaster@..."; but AFAIK this is not strictly required.]

[quote]the first three at "Relaying control" are checked.[/quote]
Good.

[quote]i tested again and i found the email in mail\mail folder (the other incoming strange mails from strange users seems to be refused fine).[/quote]
You can confirm that by reviewing the log files.

[quote] Thanks for your help.All the good things.[/quote]
You're welcome.  I'm glad that you (apparently) got it (at least partially)  working.

I want to stop this kind of messages that are comming every second:

T 20110330 134658 4d9330ef Connection from 94.30.53.164
T 20110330 134658 4d9330ee Connection closed with 173.14.113.149, 2 sec. elapsed.
T 20110330 134658 4d9330ef EHLO gpccvu.com
T 20110330 134658 4d9330ef MAIL FROM:<mhvbhl@yahoo.com.tw>
T 20110330 134658 4d9330ef RCPT TO:<steven7296@mail2000.com.tw>
T 20110330 134659 4d9330ef RCPT TO:<lan04418@yahoo.com.tw>
T 20110330 134659 4d9330ef RCPT TO:<juml_no@yahoo.com.tw>
T 20110330 134659 4d9330ef RCPT TO:<e0925174545@yahoo.com.tw>
T 20110330 134659 4d9330ef RCPT TO:<j510317@ms49.hinet.net>
T 20110330 134700 4d9330ef RCPT TO:<robertwangtw17@yahoo.com.tw>
T 20110330 134700 4d9330ef RCPT TO:<allenfox65928@yahoo.com.tw>
T 20110330 134700 4d9330ef RCPT TO:<jokoniyo@yahoo.com.tw>
T 20110330 134700 4d9330ef RCPT TO:<awwdd@ms19.hinet.net>
T 20110330 134701 4d9330ef RCPT TO:<rexay@yahoo.com.tw>
T 20110330 134701 4d9330ef RCPT TO:<shesay777@yahoo.com.tw>
T 20110330 134701 4d9330ef DATA
T 20110330 134701 4d9330ef Connection closed with 94.30.53.164, 3 sec. elapsed.
T 20110330 134702 4d9330f0 Connection from 122.166.118.34
T 20110330 134702 4d9330f0 EHLO fueusu.com
T 20110330 134702 4d9330f0 MAIL FROM:<ddpah@yahoo.com.tw>
T 20110330 134703 4d9330f0 RCPT TO:<debby740721428@kimo.com>
T 20110330 134703 4d9330f0 RCPT TO:<a597211@yahoo.com.tw>
T 20110330 134703 4d9330f0 RCPT TO:<m9103527@yahoo.com.tw>
T 20110330 134703 4d9330f0 RCPT TO:<log700610@yahoo.com.tw>
T 20110330 134704 4d9330f0 RCPT TO:<yhp2522@yahoo.com.tw>
T 20110330 134704 4d9330f0 RCPT TO:<lpy0716@yahoo.com.tw>
T 20110330 134704 4d9330f0 RCPT TO:<s4092126@yahoo.com.tw>
T 20110330 134704 4d9330f0 RCPT TO:<liwen0330@yahoo.com.tw>
T 20110330 134705 4d9330f0 RCPT TO:<fbj@ms22.hinet.net>
T 20110330 134705 4d9330f0 RCPT TO:<joe200200320@yahoo.com.tw>
T 20110330 134705 4d9330f0 DATA
T 20110330 134705 4d9330f1 Connection from 75.148.112.209
T 20110330 134705 4d9330f1 EHLO yvoxqi.com
T 20110330 134705 4d9330f0 Connection closed with 122.166.118.34, 3 sec. elapsed.

I dont want to lose the posibillity to receive messages with "RCPT TO:<trusteduser@mydomain.com>".

It is hard to store unwanted messages every second.

If you make sure that "Strict local relaying restrictions" is checked in MercuryS configuration, and "Accept mail for invalid local addresses" isn't checked you will only receive mail for valid local users.

/Rolf

but i need to receive emails from internet, and if i do that way and get from internet isnt accepted.

i was thinking that if the mail is to mail@mydomain.com at RCPT i can accept mail@mydomain.com at RCPT and to refuse other RCPT maybe?How?

but i need to receive emails from internet, and if i do that way and get from internet isnt accepted.

i

was thinking that if the mail is to mail@mydomain.com at RCPT i can

accept mail@mydomain.com at RCPT and to refuse other RCPT maybe?How?

You are running an open relay and if you do not turn it off you are going to be on every blacklist so you'll not be able to either send or receive mail in no time at all.

"Strict local relaying restrictions" is checked and "Accept mail for invalid local addresses" isn't checked.

to test it i try to send an email to my mail through internet and it was refused. i cannot refuse a mail from a company that try to contact me (with unknown email). Until i find a solution i must continue my work.

the difference between when i send to my server is that the email is addressed to mail@mydomain.com instead of xy@z.com. Is possible to accept emails addressed as i said?Is there another solution?How to resolve the server problem?

"Strict local relaying restrictions" is checked and "Accept mail for invalid local addresses" isn't checked.

 In Configuration | MercuryS you should have selected the first three options to both block replaying off your server and to allow connections using the ERSMTP AUTH command to relay.

to

test it i try to send an email to my mail through internet and it was

refused. i cannot refuse a mail from a company that try to contact me

(with unknown email). Until i find a solution i must continue my work.

I assume you are trying to send mail to either a local used on Mercury or are using ESMTP authorization to relay off the server to send to a non-local address.

the

difference between when i send to my server is that the email is

addressed to mail@mydomain.com instead of xy@z.com. Is possible to

accept emails addressed as i said?Is there another solution?How to

resolve the server problem?

I'm not sure what you are asking.  MercuryS should be set to receive mail for local accounts and to allow your external e-mail clients to use the server to relay to non-local e-mail addresses.

It would help a lot if you were to provide a copy of your mercury.ini file for anaylsis.

[quote user="Thomas R. Stephenson"]

I assume you are trying to send mail to either a local used on Mercury or are using ESMTP authorization to relay off the server to send to a non-local address.

I'm not sure what you are asking.  MercuryS should be set to receive mail for local accounts and to allow your external e-mail clients to use the server to relay to non-local e-mail addresses.

[/quote]

Yes im trying to send to a local user (the root) from internet but i cannt create it.(i tryed "Manage local users...","Add", completed, ok, the list is empty, restart, still empty).

I dont have external users.

I wrote my questions bellow the ini file.

#  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:          mydomain.com    # 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:\MAIL    # Where mail should be put for delivery
smtpqueue:       C:\MAILDIR    # Where the SMTP client should look for mail
newmail_path:    C:\MAIL    # Where to find the users' WinPMail mailboxes.

[Protocols]
C:\MERCURY\mercurys.dll
C:\MERCURY\mercurye.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:    mail    # NetWare UIC of postmaster
broadcast:     1    # Yes, we want broadcast notifications, but
receipts:      0    # ... no broadcasts for receipt confirmations
PM_notify:     0    # 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
Allow_Illegals : 0
SMTP_Authentication : 1
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]
mydomain: mydomain
mydomain: mydomain.com

[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

 

Maybe i have to create a user manually? How?

Just for starters you need to at least address the following problems.

> General]
> myname:          mydomain.com    # Canonical name for this server

Is this you?

Answer Section:
    mydomain.com, A, 66.150.120.131
    mydomain.com, A, 64.14.143.57
    mydomain.com, MX, 0, mx.mailix.net
    mydomain.com, NS, ns1.mydomain.com
    mydomain.com, NS, ns2.mydomain.com
    mydomain.com, NS, ns3.mydomain.com
    mydomain.com, NS, ns4.mydomain.com

      Dotster Inc.
      8100 NE Parkway DR
      Suite 300
      Vancouver, WA  98662
      US
      360-253-2210
      360-253-4234


   Domain servers in listed order:
      NS1.MYDOMAIN.COM
      NS2.MYDOMAIN.COM
      ns3.mydomain.com
      ns4.mydomain.com

End of Whois Information

Results brought to you by the GeekTools WHOIS Proxy
Server results may be copyrighted and are used with permission.
Your host (209.128.94.2) has visited 1 times today.


> timezone:        +0000    # Time Zone to add to date fields
> file_api:        1    # Use the file api instead of queues
> mailqueue:       C:\MAIL    # Where mail should be put for delivery
> smtpqueue:       C:\MAILDIR    # Where the SMTP client should look for mail

These are normally both the same.  C:\mercury\queue.  This is where the Pegasus Mail client puts the mail for sending and the mail server expects to find them for processing.
 
> newmail_path:    C:\MAIL    # Where to find the users' WinPMail mailboxes.

The newmail_path should be C:\MAIL\~n The mailbox structure with this setting would be

c:\mail            the location of the pmail.usr file with all the usernames.
c:\mail\USERNAME1    all of the local accounts.
.
.
c:\mail\USERNAMEn

[quote user="forum user"]

[quote user="Thomas R. Stephenson"]

I assume you are trying to send mail to either a local used on Mercury or are using ESMTP authorization to relay off the server to send to a non-local address.

 

I'm not sure what you are asking.  MercuryS should be set to receive mail for local accounts and to allow your external e-mail clients to use the server to relay to non-local e-mail addresses.

[/quote]

 

Yes im trying to send to a local user (the root) from internet but i cannt create it.(i tryed "Manage local users...","Add", completed, ok, the list is empty, restart, still empty).[/quote]
Whew!  There's quite a lot there, and I'll happily leave it to Thomas to wade through most of it (!).  But right off the bat, the above raises a BIG red flag.

Without any local users defined, Mercury CANNOT usefully send or receive mail.  Your phrasing above is not completely clear; but I gather that upon finishing (or so you thought) entering the data for the first user, the list of "Current users" shown in that dialog box was *STILL* empty.  If that is correct, then for whatever reason, the "Add" process was NOT actually "completed, ok", and you did NOT actually define any users.  There are potentially many possible reasons for this; but the first thing which springs to mind is...

Do you -- or rather, whatever "User" (from the system's POV) Mercury is running as -- have write permission for the directory in which Mercury wants to create its user mailboxes?  Typically, that would be ~/MERCURY/MAIL/ on whichever drive you have defined for Merc to keep its data on.  If Mercury cannot write to that drive/directory (specifically, to create new directories for each user), then it cannot create any new users.

Also...  I would suggest that you NOT use "root" as a user name (or e-mail address), on general principles.  That name has a specific defined meaning in some contexts, and it's best not to confuse the issue.

[quote]I dont have external users.[/quote]
What, exactly, do you mean by that?  Are you trying to say that the only users of your mail server will do so via a local LAN connection?  That's not really relevant to the above.  Regardless of from whence the traffic is originating, the addressee MUST be defined in order for Mercury to receive (and subsequently, deliver) the message.

Finally...  Would you please revisit your user profile here and enter SOME sort of real name/Handle?

"mydomain" isnt mine. i have "oapplications" the domain name.

i changed and now i have as bellow:

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:\MAIL\~n    # Where to find the users' WinPMail mailboxes.

i added in Mercury at "Manage local users..." a user,"mail".

i see in C:\MAIL\   the mail folder and PMAIL.USR file.

the first three at "Relaying control" are checked.

i tested again and i found the email in mail\mail folder (the other incoming strange mails from strange users seems to be refused fine). Thanks for your help.All the good things.

[quote user="Sailor21"][quote user="forum user"]

[quote user="Thomas R. Stephenson"]

I assume you are trying to send mail to either a local used on Mercury or are using ESMTP authorization to relay off the server to send to a non-local address.

 

I'm not sure what you are asking.  MercuryS should be set to receive mail for local accounts and to allow your external e-mail clients to use the server to relay to non-local e-mail addresses.

[/quote]

 

Yes im trying to send to a local user (the root) from internet but i cannt create it.(i tryed "Manage local users...","Add", completed, ok, the list is empty, restart, still empty).[/quote]
Whew!  There's quite a lot there, and I'll happily leave it to Thomas to wade through most of it (!).  But right off the bat, the above raises a BIG red flag.

Without any local users defined, Mercury CANNOT usefully send or receive mail.  Your phrasing above is not completely clear; but I gather that upon finishing (or so you thought) entering the data for the first user, the list of "Current users" shown in that dialog box was *STILL* empty.  If that is correct, then for whatever reason, the "Add" process was NOT actually "completed, ok", and you did NOT actually define any users.  There are potentially many possible reasons for this; but the first thing which springs to mind is...

Do you -- or rather, whatever "User" (from the system's POV) Mercury is running as -- have write permission for the directory in which Mercury wants to create its user mailboxes?  Typically, that would be ~/MERCURY/MAIL/ on whichever drive you have defined for Merc to keep its data on.  If Mercury cannot write to that drive/directory (specifically, to create new directories for each user), then it cannot create any new users.

Also...  I would suggest that you NOT use "root" as a user name (or e-mail address), on general principles.  That name has a specific defined meaning in some contexts, and it's best not to confuse the issue.

[quote]I dont have external users.[/quote]
What, exactly, do you mean by that?  Are you trying to say that the only users of your mail server will do so via a local LAN connection?  That's not really relevant to the above.  Regardless of from whence the traffic is originating, the addressee MUST be defined in order for Mercury to receive (and subsequently, deliver) the message.

Finally...  Would you please revisit your user profile here and enter SOME sort of real name/Handle?

[/quote]

when i changed the mailbox, i asigned to c:\mail and at "Manage local users..." there was "???" at the "Mailbox directory", when i put c:\mail\~n there was "c:\mail" so i can add user, before was just a "ding" win message at that event.

Thanks.