[quote user="gideon220"]When  I test this with an email client what would be my server name?  Or how do I find out the server name that needs to be in my client?  Is it just going to be smtp.server.domain.org?  Or should i use my internet IP address?  Selecting the option in core/general did work, but does that mean that anyone can send through this server?
[/quote]

Depends on the system.  If your email client is running  on the same system as Mercury/32 you can use "Localhost" or "127.0.0.1" as the server host name.  If you're running on a different system on your local lan then you can use the internal IP address of the Mercury/32 system.  If you are running from offsite then you need to use the hostname of the router or system connected to the internet.

If your server is actually connected to the internet then yes people can connect to port 25 to use your MercuryS host to send mail.  You have to turn off relaying in the MercuryS setup. 

[quote user="jdiglidis"]

Hello everybody,
is there a way to discard messages for non local users (no alias and no local user existing)
and to send an informational mail back to the sender of this message?

Thanks for any help.

[/quote]

Nope, it's already been delivered via SMTP and so anything you do about sending the mail back to the sender will have to be outside this protocol via a separate message.  This could be done with filters from the default user account.  If this is mail sent by spammers you are confirming that the message was in fact delivered to someone.  This is especially true if you return the message with all the headers.

its a Windows 2003 R2 Standard Server

Okay, thanks for clearing that up. I was successfully able to get around the outbound mail issue by just using MercuryC with my ISP's smtp service. Looks like I will have to use an MX service like you desscribed. Curse ISP's that block port 25 from legitimate mail server usage!!!

[quote user="fxmaker"] Forgive me for being dense, but I could not find out how to make a user specific to a single domain so that U@Domain1 and U@Domain2 are different users.[/quote]

Create the local maildrops as UserA, UserB, UserC

Then add aliases, so that f.ex.
info@domain1.com == UserA
info@domain2.com == UserB

this is how we run lots of domains and aliases. People who f.ex. retire, but keep their domain, have asked us to change their addresses from john@domain.com to f.ex. john.a@domain.com and they only get emails from people they really want to get email from, without having to alter usernames or passwords.

Mercury doesn't discriminate on specific interfaces.  The greeting string will be the same, no matter what the local address of the connected socket is.  As far as I can tell, there's in fact no way to tell Mercury to do anything more than bind to specific addresses for use as server; client sockets are decided as usual by the OS according to address reachability (that's behaviour you can change in Windows itself if you've a mind, but by default it's based on the IP number of the destination).

Cheers,

Sabahattin

Thanks everyone. You have all been very helpful. It appears that the Trendnet app has a serious security flaw. It seems to be using the local host's administrative password in its authorization.

It look's like I'll have to write my own app.

I can't think why the stalling is occurring only intermittently.  It can't be a filesystem permission problem.  Perhaps the jam occurs due to networking conditions.  Have you tried to change to MercuryC (if you want to)?  Alternatively, try increasing the number of MercuryE delivery threads - say, to 50 (dangerous if the host is doing anything time-critical).  See if that helps you at all.

If the jobs in the queue have errors (QIF files), it'd be nice to know what those were - if, perhaps, many open connections are occupying system resources, we might be able to explain why restarting the server made them pass through.

Cheers,

Sabahattin

Filtering rules, the core never sees transaction filters.

You can't change the subject line, this filter only adds a header, it cannot replace a header.  With what you said you should have a new header in your message showing test: hallo.

You also cannot at this time move messages via filtering to a specific folder.  What you can do is add a specific header to the message like "SPAM: True" and then have Outlook filters looking for this specific header in the headers to move it to a folder.  This type of filtering is available in Outlook 2002 I assume this is available in your version of Outlook.

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.