Hi,

Ok, making a little ground on this.

When I remove the Spamhalter Local IP network IP's, (and I also shut off my Antivirus with mail scanning) I'm now getting some headers in some emails.  But, only for SOME LOCAL emails being sent. 

Appears all outside emails received via MarcuryD are not given headers.  These are the one that should be getting checked.

They are all received from my ISP's catch-all pop3 account.

If Spamhalter has been told to "whitelist" entries for an IP or domain name of incoming mail, where is this entry and how do I clear it?

Thanks,

Mark

>
> So , are you saying on a standard Comcast cable connection I can't possibly operate my own SMTP server with any degree of
> inboxing/success?

Since I have setup a number of these on Comcast I can tell you that you can successfully run a mail server on Comcast.  There though are some problems.

1.    You cannot receive via port 25 since this is blocked.  You can get a mail forwarder like MailHop Relay provided by DynDNS to forward the mail to a different port like 2525.  http://www.dyndns.com/services/mailhop/relay.html You can also use MercuryD to get your mail via POP3 from another mail service like Yahoo or Google.

2.    You cannot send via port 25 since even if it was opened by Comcast all the major systems will block the mail since the IP address is not a fixed address.

P.S./ SUGGESTION: You know, I have tried other mail servers such as

Hmail and those were easy to get up going fast.

Since they had fewer options and capabilities of course they were easier to setup.  ;-)

But I like to turn in  "Mercury SMTP Server -> Connection

control"   the parameter   "Only Authenticated SMTP

connections may relay mail" of ON!!

To got more security!

Is there a posibility in my script to put a "pasword" and a

"user" that Mercury understand it?

If port 25 of this system is available via the internet  and you do not turn off relaying and turn on strict relaying you will be running an open relay that the spammers will find in a few hours at most.  Once you turn off the relaying and set strict you can authorize relaying either through the ESMTP authorization or by allowing specific IP addresses to relay under connection control.  See the MercuryS help for details.

On the Opt In, yep, thats what we're doing.  We're using the integrated list manager for unsubscribes, and manually entering in new subscribers.  It's a static list usually, very few adds, so manual entry isn't an issue. Future lists may be much larger and more active, so I may have to design a web page to get the data into the list file.  We'll see

On the spam label, I may have come across a separate error that was causing it.  The DNS Entry for reverse lookups was fat fingered, I'm getting that fixed now.  Sorry for the false alarm on that. 

I would clear the queue and scratch directories and upgrade to the current release of Mercury/32. It might be a good idea to run Chkdsk on the disk in question and restart Windows as well.

/Rolf 

> OK, here is the mercury.ini. I'm going home now and won't be able to see any response for about an hour. Thanks for your help.

See my response in-line, I cleared out a lot of stuff that was not material.  

>
> #  MERCURY.INI generated by Mercury Setup
>
> [General]
> myname:          vm-xp2.whoi.edu    # Canonical name for this server

Valid server, responds to port 25 Does this host have a fixed IP address?


220 vm-xp2.whoi.edu ESMTP server ready.
ehlo thomas
250-vm-xp2.whoi.edu Hello thomas; ESMTPs are:
250-TIME
250-SIZE 0
250-AUTH CRAM-MD5 LOGIN
250-AUTH=LOGIN
250 HELP

>
> [MercuryC]
> Host : outbox.whoi.edu

The server does answer Start | Run telnet outbox.whoi.edu 25  

220 postal2.whoi.edu ESMTP Postfix (Debian/GNU)
ehlo thomas
250-postal2.whoi.edu
250-PIPELINING
250-SIZE 104857600
250-VRFY
250-ETRN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
mail from: <thomas@tstephenson.com>
250 2.1.0 Ok
rcpt to: <support@tstephenson.com>
554 5.7.1 <support@tstephenson.com>: Relay access denied

But it is not available for relaying.  It may allow relaying using your IP address though.  That said I would have expected it to show the use of the AUTH command.

This does not show an error FF though since I can connect to the host.  The failure also shows a error message that should be passed back to Mercury.  Can you telnet into the host from the Mercury system?


> Failfile : C:\progra~1\mercury\Mercury\FAILURE.MER
> Poll : 30
> Scratch : C:\PROGRA~1\mercury\Mercury
> ReturnLines : 15
> Timeout : 30
> ESMTP : 1
> SMTP_ConnFlags : 16
> POP3_Auth : 0
> Logfile : c:\docume~1\cis_admin\desktop\mercc.log
> Log_Verbose : 1
> Session_logging : c:\progra~1\mercury\logs\session
> Session_logmode : 1
>
> [MercuryE]
> Poll : 15
> Timeout : 60
> Nameservers : 128.128.243.3,128.128.243.2
> Log_Verbose : 0
> DNS_Timeout : 20
> DNS_Retries : 4
> Transcripts : 1
> MaxThreads : 10
>
> [MercuryS]
> Debug : 1
> Logfile : C:\progra~1\mercury\Logs\MERCURYS.LOG
> Timeout : 30
> Relay : 0
> Strict_Relay : 1
> Allow_Illegals : 0
> SMTP_Authentication : 1
> Auth_File : c:\progra~1\mercury\pw
> Session_logging : c:\progra~1\mercury\logs\session
> Session_logmode : 1
> Compliance_Settings : 0
> Maximum_Failed_Rcpts : 4
> Max_Relay_Attempts : 4
> SSL_Mode : 0
> ST_Blacklisting : 288
> No_VRFY : 0
> SMTP_ConnFlags : 0

Looks good.

> [Domains]
> vm-xp2: vm-xp2
> vm-xp2: vm-xp2.whoi.edu
>

I upgraded from v4.62 to v4.72, and noted that the ModulePoll daemon

ceased to work.  Changed no settings, and couldn't resolve this.

I'm using Petr Jaklin's Module Poll on v4.72 and I just tested it with MercuryD.  The mail I sent to the MercuryD alias turned on MercuryD.

What version of Module Poll are you using?  

What are you using it to trigger?

Depends entirely on your ISP's policy, you should check with them.

In addition to Thomas' comments it should be noted that paths without drive letter may not work if running Mercury as a service. This is how it Mercury creates a path by default:

mailqueue:       C:\PROGRAM\MERCURY\QUEUE

Paths are not needed for protocol modules (the dll:s should be in the Mercury directory).

Unless your computer actually is named "localhost" you shouldn't specify that name in the Domains section.

As you apparently had the scheduling module MercuryX loaded it should be noted that this module is broken in the 4.72 release and may have caused problems for you. There is a patch in the downloads section, but in your case just turn it off as Thomas suggested.

/Rolf 

The answer to the problem is quite straightforward: I should have used the smtp address belonging to the mobile carrier, not my ISP![:$]

I don't have any really good solution to that I'm afraid. Noticeboards are not part of any standard, it's a proprietary feature that only works if you use Pegasus as your email client. The IMAP protocol won't allow you to have several users with different access rights connecting to the same mailbox. One idea would be to create several distribution lists, one for each folder you want to create, and have the email clients move the messages to the appropriate local folders. But in that scenario each user would have its own copies of all messages, of course, and would be able to delete them if they wanted to.

/Rolf 

Thanks for your tipps.

I have found the error and it was in the MercuryS setup where I had the localhost IP 127.0.0.1 instead of ASUS desktop IP 192.168.178.28 as IP interface to use!

Now I can receive the test message and hopefully also the status messages from my Linkstation without any additional changes on port settings or opening ports in the windows firewall.

A bit of healthy paranoia never goes amiss [:P]

Okay, don't know what I changed but it works now. The purpose of my 'copy' was that postmaster also gets a copy of the mail next to Sandya, for now seems to work. No MercuryS present of course ;-)

 Tnx for all,

<Erik>

> When I attempt to check my e-mail on the host PC (the pc that mercury is installed to) I get the following error in Windows Mail (Pegasus
> mail doesn't give an error but still doesn't recieve e-mail): Unable to send or receive messages for the Graficka (admin) account. The e-mail
> server returned an error.
>
> Server Error: 0x800CCC90
> Server Response: -ERR
> Server: 'mail.graficka.net'

This server responds as a good POP3 server.

+OK <32232848.11318@mail.graficka.net>, POP3 server ready.
user thomas
+OK thomas is known here.
pass none
-ERR Username or password is invalid or incorrect.

> Windows Live Mail Error ID: 0x800CCC90
> Protocol: POP3
> Port: 110
> Secure(SSL): No
>  
> Mercury shows the following when looking at the logs:
>
>  Connection from xxx.xxx.xxx.xxx, Sat Feb 20 01:33:45 2010
> 0 sec. elapsed, connection closed Sat Feb 20 01:33:45 2010

We really need to see a copy of the MercuryP session log to determine what is happening between MercuryP and Live Mail.

No, it won't be your router, unless you have your NAT backwards.

Try the second method. Has been documented before, maybe on the Merc list.

> Great, a scenario to add to the helpfiles. Indeed I did need MercuryP too...
>
> Remaining problem, less urgent than receiving as sending could be done directly even from the 2nd PC: why does SMTP relay not reach MercuryC?

It should be connecting to MercuryS.  MercuryC is the outbound SMTP client, MercuryS is the inbound SMTP server.

>
> No sessionlog filled... Tnx,

Possible causes

1.    Mercury not running on port 25.

2.    Port 25 being blocked.

3.    Another SMTP application is on port 25.

In any case setup an alternative port of 587 on MercuryS and then try to telnet into port 587.   You should see a reply from MercuryS that looks like

220 novell-tstephenson.com ESMTP server ready.

when you telnet into port 587 or port 25.  If you see something different it's quite possible you have another SMTP host running.
 

[quote user="erikdr"]

Okay, it WAS Vista. The Ini file which was correctly personalised was done so during the install, and then due to Vista''s defaults the Mercury installer uses elevated rights. Normal Mercury config util can not get these rights [:P]

Tnx a lot to all, more questions to come for next stepz,

<Erik>

[/quote]

Can you please describe how you personalized .ini file and what changes you did? I have the same problem on Vista and want to solve it without reinstalling. Thanks for help! 

Yes.

Stealth is overrated IMHO. Closed is fine if you are wanting to keep others out.