Hi all, Solved my own problem shortly after posting earlier message.

Problem was my ISP decided to fire-fight spam and their IPs from blacklisting by blocking port 25. Duh!

From what I see, they are not blocking all traffic but only from selected users.

Anyhow, used alternative port on Mercury. problem solved.

I don't think it matters since this appears to be an issue with Novell's UP (perhaps a policy setting?) not populating the NDS password field properly like it should.

I really don not know why we choose 200.128.1.nnn for our internal IP addresses, whether it was our choice or suggested to us by our ISP in the early days of our use of IP internally.   I had noted that addresses in the range we use belong in Brazil.

 I might get this changed as it could explain why AOL block emails from us which have attachments.

Thanks for the links I have looked them up.
 

Can't connect to 213.180.114.52 on port 25: Timed out

Firewall?  TCP port 25 incoming needs to be opened.  Check your router.  Check your software firewall configuration.  In the Windows firewall, allow mercury.exe.

Tip: if you only have one mail server, it is easy to do away with a large volume of spam delivered by broken ratware that doesn't know about the RFC 2821 zero-preference rule.  Delete all MX records.  Delete mail.binos.lv.  Now just set up binos.lv with A 213.180.114.52.  Mail servers will try MX record.  There isn't one, so delivery is attempted directly with binos.lv, which works.  But spammers often don't do the second step.

Cheers,

Sabahattin

Thanks for that, Thomas. I've downloaded the text, and will have a look.

Cheers!

You need to use a service wrapper to run Mercury/32 as a service.  I use NT Wrapper to do this since it allows me to run the service as a specific user and still interact with the desktop. The NT Wrapper allows standard Win32 applications or scripts to be run as a Windows NT/2000/XP/2003 Service. 

Features:
    ·    Easy configuration thru a GUI and simple INI files. 
    ·    Prioritization of sub-processes. 
    ·    Custom environments. 
    ·    CPU binding 
    ·    Redirecting of Stdout/Stderr to file 
    ·    Logging to the event log and to disk. 
    ·    The capability to run multiple applications in a 
         single NT Wrapper service instance. 
    ·    Monitoring of a service in the sys-tray. 

http://www.duodata.de/ntwrapper/

The MS email server used with MS servers is Exchange and it works SMTP only to get the mail.  I would expect that would be the same email  server functionality that they would provided with the home server.  There are some add-ons that allow for download via POP3 however they also simply download all the mail in the account expecting that the email client will get the email from the local server.

How the world was a lot nicer if : there was no spam, there was no war, there was no .....

Well, all you people thanks for listening and giving points in the right direction.

The error was not there, when sending me an e-mail, you get the delivery notification error that the domain does not exists. so last friday i found after four e-mails that my former hoster, who do control and maintain my ip to domainname (DNS) that 'someone' had change things although they did say at first that there was no changing..... )-:

Well, someone did actually change my MX record, resulting in a ip.name  instead of an ip only or name only.

Finding that, restoring that, evrything works fine.

I must now send them a message that this may have been an small error (leaving a period in the line where it does not belong) but the consequences were severe.

Thanks to all for helping me out.

Anne.

[quote user="FeralReason"]

I am trying to set up a local environment using XAMPP on Windows XP to test PHP scripts. I try filling out a feedback form and then forwarding the contents through a PHP script. Whether the receiving address is (for example)  or johndoe@aol.com makes no difference. The mail does not show up in the johndoe account in Pegasus or in the johndoe@aol.com account.

 Any suggestions ? Thanx !

[/quote]

Check Mercury logs (or console windows) to find out what is happening. The MercuryS log should show the messages being recieved from PHP, the core log should show the delivery to the local mailbox, and the MercuryE / MercuryC log (depending on what module you use for external delivery) should show the aol.com delivery.

Before doing anything else, please make sure that the local domains section in core configuration is OK (have a look at the help text for it).

/Rolf  

[quote user="skv"]

Hello,

I want to restrict outgoing emails from one or more account from one particular department to send only to certain email address.

Let say I have 15 user ids 5 of them belong to one department.  Their user ids are user1, user2,.....user5 and I want to restrict their ability to send emails only to the directors say user6, user7,..user10.  Emails to all other addresses should not go.  Even if the "to: contains the directors ID along with other email IDs it should go only to the directors ID and it should not send it to other ID.

Please help me solve this issue.

Thanks

skv

[/quote]

Looks like you are trying to use technology to solve a social problem and that's never a good idea.  I'd personally put the rules in writing and then send the rules to the affected user(s) and tell them what will happen when the break the rules.

That said, I can see no easy way to restrict mail to specific users only without a lot of filters.  Even there you could possibly have mail to the directors that have Bcc: addresses to other local users.  For example, a message user1 sent to user6 that has a Cc: or Bcc: to user2  is going to be very difficult to catch if received via MercuryS.

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.

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.