Here is the mercuryC logs. i see that extra < in the email that the forums sent. Sorry i dont know alot about scripts and code (just enough to put up a site and forums, which then brings me here to bug you guys with my problems. Thanks again for all the help and if you need anymore files or logs let me know. I also posted on SMF forums havent gotten a response.
> Hello Mr. Stephenson, > your mail domain tstephenson.com is registered with the DNS system.
Yes, it is registered. But I also have some DynDNS domains registered as well and there is no problem using the GMail servers as long as I authenticate and use the proper setup.
(b) -SMTP STARTTLS -
Server host name: smtp.gmail.com Server TCP/IP port: 587 SSL/TLS: via STARTTLS Enable server certificate fingerprint tracking: checked SMTP Authentication: Login to the SMTP server using POP3 username/password (the GMAIL-POP3-definition has been chosen)
(c) - SMTP via SSL -
Server host name: smtp.gmail.com Server TCP/IP port: 465 SSL/TLS: via direct ssl connection Enable server certificate fingerprint tracking: unchecked SMTP Authentication: Login to the SMTP server using POP3 username/password (the GMAIL-POP3-definition has been chosen)
> I guess you have a fixed IP or something better than the free SynDNS service (including MX records).
I have MX records with DynDNS as well, GMail does not care if I have a fixed IP address or not. They do require a valid SMTP connection.
> I did not check with Gmail (as i have no account there) what happens, if you have a dynamic IP and a fantasy local mail domain name.
No problem.
> I tried it with web.de (a german provider) and they refused relaying - even if i authenticate correctly (i have a account there) - because the > FROM was not that of my account there, but something like user1@fantasydomain.net (the account of my local mail server).
Are you sure you properly authenticated?
Did you register the e-mail address you used for sending?
What is the actual domain being used? Is you IP address on any blacklists?
Be specific and use real data otherwise I'm simply guessing as to why it failed.
> > > > I have no idea about this server, I do know that Mercury has no > > problems sending any message using any address the sender wants to > > use with either MercuryC or MercuryE. > > I was asking if Mercury could be configured, so that dependent of the > local user, it chooses a different relay server and if Mercury could > rewrite the FROM in external send mail to something configurable for > the fore mentioned relay (configurable for the local user).
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?
> > 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.
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.
> 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?
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.