Thanks Paul and Rolf and sorry for the delay to reply, too much work these days.

[quote user="PaulW"]

But how can you avoid creating backscatter - sending a reply to a 'spoofed' address?

[/quote]

Sure, but the alternative is too have wrong addresses mails not sent back to the senders, then the sender may think that his/her mail was received.

I tried to link a rule to the 'misc' mailbox but it is not seen as a mailbox linked to a user by Mercury, it 's just seen as a garbage folder.

I'm trying to write a program  that would process the .cnm files recorded in this folder and would send back a bounce message to most of them (but not to the bounce messages senders, ie mailer-daemon) and then would delete those files, the program would run each hour as a scheduled task.

Regards

Hi there

My Mercury32 is connected to a domain mailbox : all the messages to an address belonging to my domain are delivered to a single mailbox (at my isp), mercury downloads the emails messages and delivers each one to the proper mailbox (ie user1@domain.org is delivered to user1 mailbox etc).*

When the user does not exist, Mercury put the message in a trash mailbox (name "misc").

I'd like to find a solution not to put the undelivered mails in the trash mailbox but to reply to the sender that the mailbox does not exist, is there a simple one?

I was thinking to create a script run every hour which would open each .cnm file and would send a reply to the sender saying the mailbox does not exist and then delete the .cnm file, is there something simpler ?

TIA

Setting an autoreply for the misc mailbox could solve the notification part. Messages would still be in the mailbox, which is either a good or a bad thing, depending on your expectations. (I would probably like to have it that way so I could check what is being rejected.) Another option could be to replace the misc mailbox with an alias pointing to a general rule set.

/Rolf 

[quote user="Rolf Lindby"]

Setting an autoreply for the misc mailbox could solve the notification part. Messages would still be in the mailbox, which is either a good or a bad thing, depending on your expectations. (I would probably like to have it that way so I could check what is being rejected.) Another option could be to replace the misc mailbox with an alias pointing to a general rule set.

/Rolf 

[/quote]

The solution to have a general rule set linked to this mailbox seems to me to be the best one, but I can't succeed to do it, I'm wondering if it's possible.

I can't test this right now, but Mercury will usually allow an alias as a valid address. To find out if it works or if this is an exception you could perhaps try pointing the alias to a regular mailbox instead of the general rule set and see what happens.

/Rolf 

[quote user="Phil"] When the user does not exist, Mercury put the message in a trash mailbox (name "misc").

I'd like to find a solution not to put the undelivered mails in the trash mailbox but to reply to the sender that the mailbox does not exist, is there a simple one?[/quote]

But how can you avoid creating backscatter - sending a reply to a 'spoofed' address?