Its out of my hands, the schools uses numbers for usernames (with leading 0)in active directory, ive linked the emails to the numbers..

itll take me another couple of sessions at the school to get it all up and running... once i do, ill get the money to you guys for the license

regards

 

 

[quote user="Thomas R. Stephenson"][quote user="d.johnson"]

i restarted the server 2003 and it worked upon restart

and yes im using accounts with leading zeros, gulp, is this going to cause problems with pegasus?

usernames are 0401-0440, 0501-0540, 0601-0640, 0701 - 0740

[/quote]

 

I really do not know, all I know is in the past on Windows workstations this was a problem.  Also had a problem with older Linux systems.  I've just quit using directories with leading zeros.

 

 

[/quote]

Yes that is exactly what we have been doing for years.   Our work mail server occasionally fails as we tend to use old workstations as servers.   Each time it has taken just minutes to get Mercury running again by merely copying the last automated backup and starting the program.   There are loads of backup programs you can use, we use Arcserve and make automated copy's to disk on a backup server every night.   You can of course just take the backup copy pop it in a new server share and map the appropriate drive, start the Mercury.exe and away you go running again in moments.

Oops, I did not see your answer when I edited my previous one. You are exactly right, the main problem was my not being able to make changes and save them as I was testing my settings. I downloaded a fresh version from pmail.com, got it working and then copied the mercury ini setting to my XAMPP version. All seems well now.  Much appreciate your help!

You say Clamwall is running OK, but why do you need to ignore local SMTP messages?  Is it about allowed attachments?

 

Thanks very much for your reply.  Well that did it!  Sure enough when I edited a MultiPOP account entry it had a path listed for where the mail data was housed.  Once I updated that, it worked perfectly.  I'll work to transition accounts from MultiPOP to use in my main identity instead (just been used to using MultiPOP for years).  Thanks again!  :-)

Dont' know if the help file has been munged in XAMPP, but mine has a LOT more info than that (you have clicked on the links in the page you referenced for 'Mercury Core Module' etc. haven't you [:^)])

I would suggest you start at the contents page and browse through the help file. There is a lot of very good info, explanations and examples.

If it doesn't turn a light on, at least you will have some more specific questions to ask [:P].

(i.e. RTFM [:D])

It would also be helpful to know what you want your mail server to do.

Send AND RECEIVE via SMTP?

Get mail from a POP3 box?

How many users, onsite/offsite?

IMAP?

Mail lists?

.....?

 

 

Make sure you're using XAMPP 1.8.3.

XAMPP 1.8.2 had this as a known bug.

If you have an MX pointer pointing to your server, you should also make an entry of this IP in the domains section.

This means that whenever there are problems with name resolution you're still reachable at f.ex. hostmaster@[ip-number entered]

Wrong group

Sorry, I just noticed that my question on this topic has already been answered by someone else, sometime back.

 Any way, any new inputs on this topic would be helpful.

 

[quote user="scubalg"]

i own the website witch is a PHP based website it has a mail server built into it for example the user registration on the website requires a relay to mail things to other address. mail comes in from DONOTREPLY@livinggods.com and sends it to XXXXusersaccountXXX@yyyy.com

the server is a windows 2003 server and is not configed as a domain controller and does not have any local area networks. Its strickly a web hosting server, which runs our clan website, teamspeak 2 server, FTP server, MySQL Database, and Call of Duty 4 server

i do not want to setup mailboxes i just want the SMTP to relay the mail

[/quote]

 

You can do this.  You would run MercuryS as the SMTP host and MercuryE as the sender.   Your PHP application could send mail to local host if Mercury/32 was running on the server. 

I would worry about relaying for spammers though since many of these web based application are not very good about controlling what is sent to the relay host.  If the spammers were able to take over this web site then your system would very shortly be blocked by every black list out there.

 

 

Thanks Thomas & Dilbert,

The chain is:

Internet -> Mercury -> pop3 connector -> Exchange 

I've realized what the problem was.

When I moved spam to spambucket@mydomain, Mercury was putting that mail into my Domain mailbox with

X-Envelope-To: spambucket@mydomain

To: OriginalRecepient@mydomain 

 

The Pop3 connector I'm using, by default was reading both these headers and sending a copy to both recipients. Fortunately, I can specify which headers get read, and ask it to read X-Envelope-To only.

 Regards,

Richard 

 

Thankyou everyone for your suggestions.  I'm getting notifications now, so I guess I fixed the problem.  It seems it was due to my MercuryD setup regarding "Local User" and "Default User".

I had a user name in the Local User field and the Default User field was blank, so that all mail received goes to that one user, irrespective of who it was addressed to.  However, on reading the help regarding the Default User field I found:

If you leave this field blank, MercuryD will discard any messages for which it can find no local delivery addresses...

I believe this is where my messages were going.  Unless something else has changed without my knowledge.  All I did was move the username from the Local User field to the Default User field, and all seems well.

Thanks again

Regards, Stuzz

[quote user="tBB"][quote user="vgracia"]

it does mean that the mercury v4.52 ssl over pop3 is now compatible with outlook?

[/quote]

No, it means that you need - as Thomas already mentioned - STunnel ( http://www.stunnel.org ) if you want native SSL over POP3/IMAP4 as Mercury doesn't support it. Note that the recommended port for POP3/SSL is 995 and for IMAP4/SSL is 993 as you can see here: http://www.stunnel.org/faq/misc.html so the required STunnel.conf entry(s) would look like:

;---

[POP3S-IN]
accept = 0.0.0.0:995
connect = 127.0.0.1:110
delay = yes
TIMEOUTbusy = 120
TIMEOUTclose = 0
TIMEOUTconnect = 120
TIMEOUTidle = 30

;---

and/or

;---

[IMAPS-IN]
accept = 0.0.0.0:993
connect = 127.0.0.1:143
delay = yes
TIMEOUTbusy = 120
TIMEOUTclose = 0
TIMEOUTconnect = 120
TIMEOUTidle = 30

;---

Best regards,

Nico

[/quote]

Hi,

I know this is an old thread, but where did you find those timeout values? Especially the "TIMEOUTclose = 0". The stunnel documentation only mentions this for a broken MSIE, not relevant for imap or pop and probably old news anyway. Are they really necessary and/or do they fix any known problems?

Greetins

Markus Borst

[quote user="domiz"]

Hi all!

I installed mercury pop3 client, imap and smtp. And all works fine in my local lan. But now i want to use it from the internet. I want to connect to my mailserver through my xxx.dyndns.org address. Now my question is, where must i enter my local network address and where my dnydns address? i tried some configurations but nothing did help. All needed ports are definitly open. if anyone could help me, please do so.

Domiz 

[/quote]

 

You say the ports are open.  What happens when you try to telnet into ports 25, 110 and 143?  Can you see activity on the console?  If not then your dynamic NDS type address is not pointing to the system running Mercury/32.  FWIW, mercury automatically binds to all of the interfaces available and so if you can't get it from the outside then it looks like you are not connecting to the system.

 

 

Hi Thomas,

 

I did see that setting but since it did not say anything about SMTP I never put 2 and 2 together.  I spent most of my time looking in MercuryC configuration settings.  I will try your suggestion.

 

Many thanks for the help,

 
Charles 

1 Non-Local Message Ignored

 This indicates that there is no receipt in the message matching a local user.  For a mailing list the addresses is <list name>@<internet name for this system> and if this is not correct yuo need to create an alias to the list name.

 

Thanks..

I'll try that.
 

You may have trouble if the drive letter changes, lots of parameters in Mercury setup require a full path.

You can set the assigned drive letter in the 'Disk Management' snapin in MMC. This will need to be done on each 'new' machine.

You should set it to a "high" letter (X,Y,or Z) so there is more chance of the drive letter being available on any particular machine. (E, F & so on are commonly grabbed by extra HDD's or DVD drives, camera's etc).

Or maybe M: would be more appropriate [:D] 

So we have in fact three different things called local here: local user, local domain, and (non-)local source. The first two make sense (user with mailbox on server, domain listed as local in core configuration), but it would perhaps be better to call the third one "mail received via SMTP" if that is what it means. It isn't mentioned in Mercury help or in the manual, and it's more or less impossible to guess the meaning.

/Rolf