3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Non delivery to users...
FromSent OnAttachments
JoeDec 26, 2004 10:32 am 
Sam VarshavchikDec 26, 2004 11:22 am 
JoeDec 26, 2004 12:36 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Non delivery to users without login shellActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Dec 26, 2004 11:22:38 am
List:net.sourceforge.lists.courier-maildrop

Joe writes:

I had first created a new user, emailcatchall, and as with most new accounts I set the shell to be /sbin/nologin. I also added a always_bcc to main.cf expecting this to work. When it didn't, I tried adding a cc "!emailcatchall" to the start of maildroprc but this didn't work either. Both ways lead to no mail being delivered by maildrop with an error talking about the filter file. In my efforts to trouble shoot the problem, I eventually gave the account a /bin/sh shell and 'boom', it all worked.

So, my question is: Is this normal?

Yes. "!address" executes the command "sendmail address", via the shell.

My concern is that I won't be able to assign my users (all are real unix users) with a /sbin/nologin or a /bin/ftponly shell and still have them receive email. I'm sure this shouldn't be the case so how do I enable users to receive emails yet restrict their ability to log into the server using ssh or ftp? The first part of the postfix-maildrop howto is for virtual users but in my case they are real accounts. By not giving them shell rights, does that make them 'virtual' to maildrop and I have to do something differently?

Explicitly set the SHELL variable in the maildrop recipe.