Vacation/Autoreply plugin question using Virtual Users And Domains with Postfix

[falko]

That should be correct. But $1 is ${extension} ans $2 is ${recipient}.

You can add

echo "$2" > /tmp/testfile

to your maildroprc. Then you can check if the correct recipient email address is written to /tmp/testfile.

[MarcelDeR]

Originally Posted by triak

I will attach my maildroprc and master.cf configuration files.

The holidays here in Finland are just starting and I'm in a bit of trouble here...
Plz help a bit :=)

Add in maildroprc between "sendmail" and "-f" a "-t" to tell sendmail to look in to the message for the addresses.

Greetings from Holland

[triak]

I added the -t option to sendmail in maildroprc and changed the $FROM variable to $RECIPIENT at the bottom of the script. And now it works!!

I ran into another problem. Maildrop should auto-create maildirs and vacation directory when mail arrives. Can't figure out why the directory creation fails.
In the same script the "test" command works fine with vacation messages and maildrop parses theese messages.

mkdir -p /var/vmail/$HOST/$USER does not work. Maildrop complains about not beeing able to change to home directory.
Is there a difference in wich stage of the script this command is run?

.j

[falko]

I guess this is some kind of permissions problem.

[todgerme]

triak, have you tried a simple maildrop filter yet, not globally to test maildrop is working correctly, like the one I placed in the guide to filter spam? better to crawl before you can walk.

after that i would modify that script, try piping to the vacation (apt-get install vacation) program with vacation.msg files instead of having different files for subject etc etc and using sendmail as I saw looking at your maildroprc file.

otherwise if you are struggling to get an autoreponder working, use yaa and write a quick gui for users to setup the autoresponder.

let me know how you get on with the basic spam filter first.

[triak]

It seems that the virtual transport method was responsible of forwardings using this setup. How can i implement simple forwardings to my maildroprc?
They are not so many so I can wrtite them straight to the script.
Or maybe use the existing mysql forward table?
And another bug that appeared after switching to maildrop, mail for user@mail.abc.fi (mail is the servers hostname) that should go to user@abc.fi does not get delivered anymore. How can i address all mail for mail.abs.fi to abc.fi? Theese are important mail's such as root, postmaster etc.

tia. Johannes

[falko]

Originally Posted by triak

It seems that the virtual transport method was responsible of forwardings using this setup. How can i implement simple forwardings to my maildroprc?
They are not so many so I can wrtite them straight to the script.
Or maybe use the existing mysql forward table?

Did you have a look here? http://www.courier-mta.org/?maildrop.html

Originally Posted by triak

And another bug that appeared after switching to maildrop, mail for user@mail.abc.fi (mail is the servers hostname) that should go to user@abc.fi does not get delivered anymore. How can i address all mail for mail.abs.fi to abc.fi? Theese are important mail's such as root, postmaster etc.

tia. Johannes

I think you can do that with transports.

[todgerme]

i am not entirely sure what you by transports but if you look at the mail filter guide for maildrop, you will see you can simply transport any email address ot the maildrop transport when required.

instead of having a global maildroprc to handle autoresponders have individualised ones, with something similar to:

logfile "/u0/vmail/.mailfilters/mailfilter-log.txt"
| /usr/bin/vacation
log "Firstly piped mail to vacation program "
cc "/home/vmail/example.com/user/new"
log "deliver mail to users mailbox aswell! "

i hope it helps.

[wierben]

Did anyone got this working? I tried and tried, can't get the mail to go through the maildrop pipe. Is there a setting i'mn ot seeing?