I'm pleased to say that (possibly in response to my concerns) Lonely Cat Games, the vendors of Profimail, have published version 3.14c as a beta - this has the option to use STARTTLS on an IMAP connection and it works with Mercury. I can recommend it to any wanting to connect a Symbian smartphone to a Mercury server over IMAP.

 

As Thomas says you will need to make sure that the webmail gets a copy of the messages if you want to be able to read the mail there as well.

/Rolf 

[quote user="matthewsdowns"]It seems like my ISP (Verizon) has blocked the ability to open port 25 in my residential use?  Is there a work-around using a different port or something else I can do?[/quote]

Checkout the services provided by DynDNS.  They provide services for both inbound and outbound mail on non-standard ports for a pretty reasonable annual fee.  https://www.dyndns.com/services/

 

Thanks....That was exactly what I was looking for!  I remember turning on logging, but never turned it off, so this should fix it.

 

RonC

[quote user="Ashley"]

Hi

Interesting this, when i set up Mercury, it says there MUST be an entry for the machine itself, (no domain), however this results in receiving email for anything at "ipaddress", is there a way to stop this, so it only receives email for domains the server controls?
[/quote]

I presume you mean something like this?

[Domains]
server: [123.123.123.123]

server: yourdomain.com

 

It's good practice, but I don't know if it is required by RFC's (I am no expert). I would be surprised if many servers supported that now. Also, I have never seen it used by any incoming mail.[quote]

However will this kill the "postmaster" function account?[/quote]

No. The postmaster account is postmaster@<internet name for this system in Core Config>
[quote]Will i have to create a rule that only says to process emails to specific domains (will still kill the postmaster account i think?)

[/quote]

As long as your (anti-)relaying settings are correct it should only accept mail for the domains listed in the [Local Domains] section.

Assuming i do this, this means this is acting as a total mail server,

with a POP mailbox for each domain, that said could i then use

WSMTPEX.EXE to then look for the files and forward those to the "real"

server behind the firewall, this would negate the need to use POP by

the real server to pull the emails....

Yes, WSMTPEX can be used to send all mail in a mailbox to the second SMTP host on any port. 

Having said that, would

WSMTPEX.EXE use MercuryE to send the emails out as a process, and if so

how long will it try before it fails (and i assume means the mail sits

in the "badmail" folder?

WSMTPex sends mail with it's own built-in mailer but the receiving domain is specifed using the [<IP address>], i.e. user@[192.168.1.4].

I may need to "re-think" this as i dont

want 2 mail "servers" running, just means bumping mail to each stop

while it waits for collection.....

If you are just using the second one as a backup MX host this will work pretty well using the POP3 pull.

If you have set Mercury to handle the mail for a domain (qasti.com) by putting it in the 'local domains' section of the core module, then incoming mail to that domain will always be allowed.

Relaying only refers to mail to a non-local domain, and from your description that is not the case here.

 
  

Ive found the same problem, it was quicker (and safer i thought) to just resend the same mail, no good if the mail isnt from you though...

Searching for TheThousand@pmail on Bing produces 9 results. Google produces 5.

Is anyone promoting this? If you guys are serious about generating sustainable support for this product then advertising this far and wide is essential. There are obviously a lot of people/companies willing to contribute but they will not do so if they know nothing about this.

[quote user="Deagol"] In order to be able to connect to an administrative share like C$ you need to be an administrator on the box you are connecting to. Regular users by default can't connect to a system via administrative shares. The only 'backdoor' in this case would be the users who do have administrative rights to the mail server. A problem could arise if you decide to create another share through which the Mercury environment *is*  accessible to users. The Mercury system can be secured by setting the correct NTFS permissions.

I am running  a Mercury 4.62 system to which users connect using a web interface (so no direct pmail integration). Mercury is running as a service in the context of a specific service account.. Only this service account, a specifically appointed Mercury mail administrator and the system account are granted access to the Mercury files and directories. This setup works fine and will deny users, if they somehow manage to get access to the mailserver (i.e. access through another share) from browsing through the mail system and from reading mail from other users.[/quote]

This is the same approach we use. An AD-user called mailserver1...n is assigned the login right and is the sole reader/writer of the Mercury directories on the local drive (RAID-5), as well as the windows service account. The setup makes the Mail Servers fairly "isolated". We've also removed the windows file-sharing protocol from these servers as well as netbios. The main MTA's (all running Mercury) has since Y2K never been infected or caused any trouble, as well as being extremely stable.

Ah.... MercuryC, I just missed it because I had the other smtp module loaded.  Thanks for the tip!

It most certainly does as the centralized processes like filtering now can run concurrently. You need to change the counterlogic to minimize open file conflicts.

Try comparing all headers (not just From and To) in one of these messages with a similar message that behaves normally and see if you can find any differences.

/Rolf 

Once again Thomas, thank you for your help.

Nico, I'll be in touch.

Alex 

> Dear Mr. Stephenson,
>
>  Thank you very much for this advice; I really appreciate you taking
> the time to answer my questions. 
>
> I have made the changes that you suggested (though I'm not sure I'm
> opening ports on the router correctly -- I logged into the router and
> "port forwarding" was an option.  I added two "services," one on port
> 25 and one on port 110; each one had to have an IP address, and so I
> just typed in 192.168.1.25 and 192.168.1.26).

This needs to be forwarded to the IP address of the system running Mercury.

>
> I am no longer receiving error messages when I send email -- it tells
> me that the mail was sent successfully.  However, none of the emails
> that I'm sending to or from the address are actually showing up.  Do
> you have any idea what I could be doing wrong now?
>
> Thanks again for all your help.
>
> Chris
>
>  P.S.
>
> My IP address is 74.79.184.211.

Is this a fixed IP address?  
>
>  and my mercury.ini file is below
>
> [General]
> myname:          74.79.184.211    # Canonical name for this server

This becomes the domain name of the postmaster and maiser and so this should be specified as a valid domain name..

myname:          [74.79.184.21I]

> [Protocols]
> MERCURYS.DLL
> MERCURYP.DLL
> # MERCURYE.DLL
> # MERCURYC.DLL

if you want to send mail you need either MercuryC or MercuryE.  If that is not a fixed IP address and you do not have a domain name you need to send via MercuryC using you ISP's SMTP host.

> MERCURYD.DLL
> # MERCURYH.DLL
> # MERCURYF.DLL
> # MERCURYW.DLL
> # MERCURYX.DLL
> MERCURYI.DLL
> # MERCURYB.DLL
>
> [MercuryC]
> logfile : E:\MERCURY\Logs\MercuryC\~y-~m-~d.log   # Traffic logging file
> Session_logging : E:\MERCURY\Sessions\MercuryC\    # Directory for session log files
> Session_logmode : 0
> host:             # mail mail host which relays for us

Here is here you enter the host name of the ISP's SMTP server.

> scratch:     E:\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:    E:\MERCURY\Mercury\FAILURE.MER  # Delivery failure template
> esmtp:       1                    # Yes, we want to use ESMTP extensions
>
>
> [Domains]
> 74: 74.79.184.211

The domains section should read

[Domains]
;server : domain
Server   :  Server
Server   : [74.79.184.211]

[quote user="Rolf Lindby"]

Nope, no limitations in Mercury. This is a message from the recipient's SMTP server, or a relaying SMTP server in between.

/Rolf 

[/quote]

I'm having a similar issue with my ISP. I need to limit how many emails Mercury sends at a time. Ideally, I need a control that lets me specify how many emails are sent before pausing a certain number of seconds and then sending another batch. Is this possible with Mercury?

Thanks!

Thanks.
Got it sorted..

One of the filtering rules, was moving it to another user.

 

That was it, Rolf. I will now perform a facepalm and be on my merry way.  Thanks.

Hello, and thank you for any help you can offer me.

Send me a message to techsupp@tstephenson.com with your current mercury.ini file, and the following info

1.   The host name and IP address of the system you are using.  Is this a fixed IP address?

2.   Is there a router involved?  If so the host name and IP address of the router connection and the IP address of the router on the LAN. Is this a fixed IP address?

3.   Is there any firewall?

4.   Is there any anti-virus sorftware?

 

 

Thanks Peter.  In fact my problem messages weren't really emply, they just appeared so when viewing with Thunderbird.  I now seem to have solved the problem, or at least have a work-around.  If I allow TB to "Select this Folder for Offline Use", the message shows up straightaway.  Without checking this option there is an error message in the TB Error Console and there is no such error message there when I check the offline use box.  I will probably pursue this error message among the Thunderbird forums.  Anyway, as most people here suggested, I don't think that the problem was with Mercury.  It's just that the evidence was very ambiguous.

Thank you

Gordon