Alexey Mishustin writes:
And then:Sep 18 21:57:58 mydomain courierlocal: id=0000000000056A05.0000000055FA7989.000015C7,from=<spammer@email>,addr=<mail@mydomain>: maildrop: Home directory owned by wrong user. (My maildrop works in delivery mode) And then: Sep 18 21:52:58 mydomain courierlocal: id=0000000000056A05. 0000000055FA7989.000015C7,from=<spammer@email>,addr=<mail@mydomain>,status: deferred Sep 18 21:52:58 mydomain courierd: completed,id=0000000000056A05.0000000055FA7989.000015C7 Why owned by wrong user - it's the second question. (And which user?)
The one that you configured for your "mail" account. What you wrote was: "My courier aliases don't include "mail" address."You did not explain your complete configuration. Your mention of "aliases" suggests that you have a default account configured of some kind, and the configured home directory's actual ownership doesn't match its configuration. You've implemented "aliases" of some sort, that are set up correctly, pointing to home directories and mailboxes with the right ownership or permissions, so that works, but if the recipient address doesn't match any of them, the default address gets looked up, and its configuration is broken.
On a properly-configured system, mail addressed to a non-existent mailbox does NOT get rejected with a
456 Address temporarily unavailable.On a properly-configured system, mail addressed to a non-existent mailbox does will get rejected with a
550 User <"address"> unknownI'm guessing that what's happening is that you have configured Courier to send mail for all addresses in your domain to maildrop, with some custom maildrop configuration to sort it out into the right mailboxes. But when mail gets addressed to a nonexistent account, your custom maildrop configuration breaks down, resulting in a mail delivery failure. At this point, Courier's default backscatter protection kicks in, suppressing the bounce and temporarily refusing to accept any more mail to the nonexistent address with a 456, for some period of time. Which is a good thing, because otherwise your mail server can be hijacked as a bandwidth amplifier in denial-of-service attacks.
But as the first question I'd like to ask: Why a message from a spammer to non-existing address mail@mydomain (addr=<mail> means mail@mydomain, doesn't it?) is being handled in other way than mine and going to be delivered to /var/spool/mail? And why there is no a record from courieresmtpd in the log?
Because something is wrong with your configuration. Unfortunately, it's not possible to say anything more, without reviewing the actual configuration settings you are using.
pgp3IFvHksdo6.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
