[quote user="bwhite"]Hi PaulW,  not sure how that would work in my situation in that we currently have a pop3 account that is our Domain Mailbox.  All mail sent to an address in our domain is collected there.  We then have mercury retreive the messages from that account to distribute to our internal users.[/quote]

That's a fairly standard setup, but has various drawbacks.

[quote]To use MercuryS we would have to have our Email host setup to periodically send all mail collected to our email server, right? [/quote]

No, that wouldn't gain you anything.  You must be the email host by changing the domain's mx record to point to your server.

[quote]With our ISP we have a problem with our "Static" IP addresses not being so Static, so that we be another problem.[/quote]

Ah, that would cause complications.

I need to find a way to have mercury respond to an email sent to an invalid user.

We have an ISP setup for our Email using a catch-all Domain Mailbox.  All mail sent ot our domain is held there.  We then use MercuryD to retrieve those emails and distribute to the local users.  Occasionally an email will have an invalid address, it could be either someone has mispelled the address or it is just being sent to anyone@mydomain.  Without setting the Default User then all we see is that a 'Non-Local Message is ignored', and so deleted.  If we set up a Default user then we need away to send a response to the sender that their message did not get delivered and that they should correct the address and try again.  Exactly the same as it is when a local user sends an email to an invalid address internally.

I did try to setup a Default User and then have an AutoReply, but it would only work once per senders email address.  If the same sender sends more than one incorrectly addressed email they will only get one reply.  This doen't matter if they send the emails at different times, thats it one response and after that the sender has no idea the email did not get delivered.

 Any suggestions?

As you have discovered, a default user will collect all incorrectly addressed mail.

I would be wary of automating replies as a big proportion of my badly addressed mail is spam or malware.  How many good messages are you dealing with?  Can you manually sort these?  If it is a common misspelling of a small number of names, there are better ways of dealing with it through filters or aliases.

There are not that many but it has to do more with the fact that a sender does not know if the email they had sent to us was delivered or not  We could sort these thru the default user account but then I would have to check it often throughout the day just in case someone has sent an email,  We have 50 plus email users here.  There is nothing common about the errors in the emails as the emails are from anyone. We have setup several aliases for common mispellings and that works well for known errors.

The way we are currently setup is that we have an Email host that we have setup one Domain Email box for our company.  They collect all email to our domain for us.  We then have Mercury setup on one of our servers to collect this email using MercuryD which is then delivered to our email users.  Maybe, this is not the proper way to handle this type of setup?  Is there a better way?  

What I would like to be able to do is use a 'Delivery Failure Template' like in the Core Module Configuration, only have one setup to be sent to anyone that sends an email to us with an incorrect address, letting them know of the error.  I am somewhat concerned about the spammers but our Email host has been doing a very good job of eliminating 99% of the spam from our Domain mailbox. 

As it is now we have several users complaining that they are not getting emails from various people.  The ones I have tracked down I found that the sender has errored in the spelling, the format was wrong such as including the '<' as part of the address, or they just sent it to an assumed email address.

You may be able to use a general rule set with action "Reply using a template" for this, and set as default user in MercuryD . Have a look at the help text for filtering rules for more details.

/Rolf 

[quote user="bwhite"]The way we are currently setup is that we have an Email host that we have setup one Domain Email box for our company.  They collect all email to our domain for us.  We then have Mercury setup on one of our servers to collect this email using MercuryD which is then delivered to our email users.  Maybe, this is not the proper way to handle this type of setup?  Is there a better way?[/quote]

With 50 users I would definitely be using MercuryS to receive external mail.  Incorrectly addressed mail is handled by the sending server and you won't have to worry about it at all.

Thanks Rolf, I will look into that.

Hi PaulW,  not sure how that would work in my situation in that we currently have a pop3 account that is our Domain Mailbox.  All mail sent to an address in our domain is collected there.  We then have mercury retreive the messages from that account to distribute to our internal users.

To use MercuryS we would have to have our Email host setup to periodically send all mail collected to our email server, right? 

With our ISP we have a problem with our "Static" IP addresses not being so Static, so that we be another problem.

Any more incite you may have would be greatly appreciated.

Thank you,

Barry