The original idea with an alias should work as well. The alias should be:

alias - the sender address you use

real address - your local mailbox name (without any domain part) 

This will, however, make it impossible to send any messages to the real external "sender address" through the Mercury server, they will all be redirected to your local mailbox. 

/Rolf 

Hi,

I'm trying to use Mercury on a single PC with outlook to send emails directly, but with no luck. Until now I was using free relay smtp server ( www.softstack.com/freesmtp.html )  and it works just fine,but has limit of 10 emails per day.

In outlook I configured my outgoing server as "localhost" and it worker in such way. When I try to use Mercury in a same way it say "553 We do not relay non-local mail, sorry". How can I be more local if I'm on localhost already???  Unchecking box to allow non-local mail seems to work somehow and sends mail if all ok. But if sending mail from Mercury to outside world fails it does not return any Error Message to outlook while mail is taken from outbox and put in to sent folder and looks like it was sent ok. I tried to put unresolvable domain in to destination email address - so Mercury for sure can not even connect to target server but still email is moved from outbox to Sent and no error reported. 

The earlier relay SMTP server was also acting similar but every time it fails - I was getting "System Administrator- Undeliverable:... " message in to inbox with error description. Is there any way to use Mercury in similar way?

I have installed MercuryS+MercuryE   

  Thanks

As you want your MercuryS/E to relay, set up a MercuryS password according to help, and allow authenticated connections to relay.

Using suggestion above I identified that the problem is when Mercury has failed to deliver mail to remote destination, it tries to send error notfication (the one I waiting for) to the "From" email address which in turn is something what can not be hosted on my personal pc.

So the narrowed question is:

Is there a way to configure Mercury so the if it fails to deliver original message - the error notification is sent to my outlook inbox at localhost as "System Administrator-Undeliverable.." instead of trying to sent to remote email address which was on the "From" line of original message? 

Assuming that error notifications is the only kind of messages to the remote From address that will pass through the server you could create an alias to redirect it to your local mailbox.

/Rolf

might be a solution. But how the alias (address) for my local outlook mailbox can look?  I have looked to previously generated error notfications when Mercury refused to accept mail form outlook. There is email account name within outlook on the line "To". Tried myaccount@localhost  but not worked. 

From:

Sent: 04 August, 2009 09:51

To: myaccount

Subject:

Your message did not reach some or all of the intended recipients.

Subject: trial

Sent: 2009-08-04 09:51

The following recipient(s) could not be reached:

'something@fardomain.org' on 2009-08-04 09:51

553 We do not relay non-local mail, sorry.

You should probably check the information in the Local domains tab in Core configuration. Here you should enter all hostnames that Mercury should consider local (hostname as used by Windows, domain, hostname in domain, IP address within brackets (LAN address as well as public IP). Read the help text for more information. Do preferably not use "localhost" here, or anywhere in Mercury configuration.

/Rolf

[quote user="karnel"] Using suggestion above I identified that the problem is when Mercury has failed to deliver mail to remote destination, it tries to send error notfication (the one I waiting for) to the "From" email address which in turn is something what can not be hosted on my personal pc.

So the narrowed question is:

Is there a way to configure Mercury so the if it fails to deliver original message - the error notification is sent to my outlook inbox at localhost as "System Administrator-Undeliverable.." instead of trying to sent to remote email address which was on the "From" line of original message? [/quote]

mmm, this requires some thought - interesting - I guess one way could be to add MercuryP, create a local user account, and a global filter rule, so that any system administrator message is forwarded/saved to this account, then killed. - should be doable.

Anything does not work. But thinking all over again I suspect it might be impossible. There is new version how I understand this. Outlook opens connection to MercuryS and transfers  mail which it has in outbox. MercuryS checks is there any restrictions to accept connection or mail from outlook and if so returns error - othrervise ok. If error present - outlooks generates sytem notfication(like one I got) an places it in to inbox or overwise moves  message from Outbox to Sent and cosiders transaction is done. All that happens on single connection initiated by Send/Receive comand in outlook which is closed at the end.    Later after MercuryS got message it tries to send it to destination via MercuryE and if fails it can not tell this to outlook any more because cennection MercuryS<->Outlook is closed. So the outlook believes it sent message ok, but in reality it got stuck at MercuryS which can not send it to outside world and can not report to outlook.

If all above correct - it looks like I need to get rid somehow of MercuryS and communicate to MercuryE directly. It should be done so that when outlook opens connection to MercuryE, try to send message over it, and wait for outcome.Only then outlook should receive either error either ok and can close connection to MercuryE. Or another option to force MercuryS not give any answer to outlook until it not received outcome from MercuryE and not passed it back to outlook.

Any comments or suggestions?

If all above correct - it looks like I need to get rid somehow of

MercuryS and communicate to MercuryE directly. It should be done so

that when outlook opens connection to MercuryE, try to send message

over it, and wait for outcome.Only then outlook should receive either

error either ok and can close connection to MercuryE. Or another option

to force MercuryS not give any answer to outlook until it not received

outcome from MercuryE and not passed it back to outlook.

Any comments or suggestions?

Outlook must be sending via a valid e-mail address, i.e. the From:, Sender: and MAIL FROM: addresses all must point to a valid e-mail account.   MercuryE when sending the mail will always bounce the mail back to the original senders address when it bounces a message.  If this is a valid address then Outlook just looks at that account to get the bounces. 

This means if you use a phony address something like dave@localhost for an e-mail address then the must be a domain "Localhost" in Mercury core and a user called Dave in Configuration | Manage local users.  In addition Outlook must be downloading this mail via IMAP4 or POP3 in order to get back to Outlook.

[quote user="karnel"] If all above correct - it looks like I need to get rid somehow of MercuryS and communicate to MercuryE directly. It should be done so that when outlook opens connection to MercuryE, try to send message over it, and wait for outcome.Only then outlook should receive either error either ok and can close connection to MercuryE. Or another option to force MercuryS not give any answer to outlook until it not received outcome from MercuryE and not passed it back to outlook.[/quote]

You can't talk to MercuryE directly. Below is the path a message travels

Outlook -> MercuryS -> Core -> MercuryE -> mx.host

An error is received when MercuryE talks to the foreign system, f.ex. recipient does not exist. This message is the one you need to get back, f.ex. by creating as Thomas says, a local user account under the domain localhost - but then your from will be bogus, or move the error report message via filtering rule. In order to retrieve this message you need to activate MercuryP, and set up a retrieve only account in your Outlook, that retrieves the message from the Mercury local user you just created.