[Dovecot] LDA alias resolution problems..
I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine.
Dovecot is 2.0.beta6 (3156315704ef)
Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine.
Now I get these sort of errors from the LDA:
Feb 27 11:54:03 cluster2 postfix/pipe[31267]: 866F0A41173: to=<virusalert@mobilia.it>, relay=dovecot, delay=357414, delays=357413/0.79/0/0.05, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Fatal: Unknown user )
Other aliases work perfectly, the only difference is that these emails are of local origin, (they're messages from Amavisd) I'm not sure why this has started to be a problem.
Can anyone give me an idea where I should start looking?
Nick
On 2012-02-27 6:06 AM, Nick Warr <nick@mobilia.it> wrote:
Dovecot is 2.0.beta6 (3156315704ef)
Seriously? You're having problems with an ancient pre-release/beta?
Upgrade to the most recent 2.0, or better yet, 2.1.1 (be sure to read all of the upgrading docs on the wiki), then try again...
--
Best regards,
Charles
Il 27/02/2012 12.58, Charles Marcus ha scritto:
On 2012-02-27 6:06 AM, Nick Warr <nick@mobilia.it> wrote:
Dovecot is 2.0.beta6 (3156315704ef)
Seriously? You're having problems with an ancient pre-release/beta?
Upgrade to the most recent 2.0, or better yet, 2.1.1 (be sure to read all of the upgrading docs on the wiki), then try again...
dovecot --version 2.0.9
Same exact problem.
any suggestions?
On 2012-02-27 9:24 AM, Nick Warr <nick@mobilia.it> wrote:
Il 27/02/2012 12.58, Charles Marcus ha scritto:
Upgrade to the most recent 2.0, or better yet, 2.1.1 (be sure to read all of the upgrading docs on the wiki), then try again...
dovecot --version 2.0.9
Same exact problem.
any suggestions?
Update to the *latest* version - for 2.0, that would be 2.0.18, for 2.1, it is 2.1.1
I'm not necessarily saying this will solve your problems (in fact, in your case it probably won't), but upgrading to the latest version should *always* be step #1 before asking for help (at least in my book)...
--
Best regards,
Charles
Il 27/02/2012 15.58, Charles Marcus ha scritto:
On 2012-02-27 9:24 AM, Nick Warr <nick@mobilia.it> wrote:
Il 27/02/2012 12.58, Charles Marcus ha scritto:
Upgrade to the most recent 2.0, or better yet, 2.1.1 (be sure to read all of the upgrading docs on the wiki), then try again...
dovecot --version 2.0.9
Same exact problem.
any suggestions?
Update to the *latest* version - for 2.0, that would be 2.0.18, for 2.1, it is 2.1.1
I'm not necessarily saying this will solve your problems (in fact, in your case it probably won't), but upgrading to the latest version should *always* be step #1 before asking for help (at least in my book)...
Talk to the CentOS guys for me, and tell em to get on the ball :)
On 2012-02-27 10:10 AM, Nick Warr <nick@mobilia.it> wrote:
Il 27/02/2012 15.58, Charles Marcus ha scritto:
Update to the *latest* version - for 2.0, that would be 2.0.18, for 2.1, it is 2.1.1
Talk to the CentOS guys for me, and tell em to get on the ball :)
Don't point fingers - this is why I would never use a distro that locks you into ancient/unsupported versions of mission critical software.
That said, there is usually a viable solution - I'm sure there are alternative CentOS repositories that offer up to date versions of things like postfix, dovecot, apache and other mission critical software. Even Debian stable (worst offender for locking you into ancient versions of software) offers such repositories.
--
Best regards,
Charles
On 27/02/12 12:06, Nick Warr wrote:
I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine.
Dovecot is 2.0.beta6 (3156315704ef)
Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine.
Now I get these sort of errors from the LDA:
Feb 27 11:54:03 cluster2 postfix/pipe[31267]: 866F0A41173: to=<virusalert@mobilia.it>, relay=dovecot, delay=357414, delays=357413/0.79/0/0.05, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Fatal: Unknown user )
Other aliases work perfectly, the only difference is that these emails are of local origin, (they're messages from Amavisd) I'm not sure why this has started to be a problem.
Usually, aliases are processed by postfix, and dovecot only gets e-mail for actual users, not aliases. Depending on how your mail processing flow works, mail generated by amavis might not visit postfix before it hits dovecot...
-- Regards, Tom
Il 27/02/2012 15.26, Tom Hendrikx ha scritto:
On 27/02/12 12:06, Nick Warr wrote:
I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine.
Dovecot is 2.0.beta6 (3156315704ef)
Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine.
Now I get these sort of errors from the LDA:
Feb 27 11:54:03 cluster2 postfix/pipe[31267]: 866F0A41173: to=<virusalert@mobilia.it>, relay=dovecot, delay=357414, delays=357413/0.79/0/0.05, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Fatal: Unknown user )
Other aliases work perfectly, the only difference is that these emails are of local origin, (they're messages from Amavisd) I'm not sure why this has started to be a problem.
Usually, aliases are processed by postfix, and dovecot only gets e-mail for actual users, not aliases. Depending on how your mail processing flow works, mail generated by amavis might not visit postfix before it hits dovecot...
-- Regards, Tom That does seem to be logical, since amavis is generating the email.
Normal emails go postfix -> amavis -> postfix -> dovecot
These go amavis -> postfix -> dovecot if this is so, I may need to talk to the postfix list, thanks!
Give this a try. Find out the location of the verify cache file and delete it.
This is my setting in main.cf address_verify_map = btree:$data_directory/verify_cache
On 2/27/2012 6:06 AM, Nick Warr wrote:
I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine.
Dovecot is 2.0.beta6 (3156315704ef)
Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine.
Now I get these sort of errors from the LDA:
Feb 27 11:54:03 cluster2 postfix/pipe[31267]: 866F0A41173: to=<virusalert@mobilia.it>, relay=dovecot, delay=357414, delays=357413/0.79/0/0.05, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Fatal: Unknown user )
Other aliases work perfectly, the only difference is that these emails are of local origin, (they're messages from Amavisd) I'm not sure why this has started to be a problem.
Can anyone give me an idea where I should start looking?
Nick
Il 27/02/2012 22.52, Pierre Chiu ha scritto:
Give this a try. Find out the location of the verify cache file and delete it.
This is my setting in main.cf address_verify_map = btree:$data_directory/verify_cache
On 2/27/2012 6:06 AM, Nick Warr wrote:
I use postfix + dovecot LDA + mysql virtual users and up til friday, everything was working just fine.
Dovecot is 2.0.beta6 (3156315704ef)
Like I said, up til friday, when I added a vacation entry into postfix (which I have now removed to see if it was the reason) mails to the alias virusalert (which is aliased to me) went through just fine.
Now I get these sort of errors from the LDA:
Feb 27 11:54:03 cluster2 postfix/pipe[31267]: 866F0A41173: to=<virusalert@mobilia.it>, relay=dovecot, delay=357414, delays=357413/0.79/0/0.05, dsn=4.3.0, status=deferred (temporary failure. Command output: lda: Fatal: Unknown user )
Other aliases work perfectly, the only difference is that these emails are of local origin, (they're messages from Amavisd) I'm not sure why this has started to be a problem.
Can anyone give me an idea where I should start looking?
Nick Thanks, though I actually understood where the problem originated after explaining where the email was injected, it was a postfix configuration issue (the vacation script has you configure the amavis line in master.cf to not expand aliases, so it doesn't send multiple vacation replies.. I hadn't considered mail not originating from postfix) , it was just that dovecot was the one who had to deal with the error. Thanks to Tom Hendrikx for the clue.
participants (4)
-
Charles Marcus
-
Nick Warr
-
Pierre Chiu
-
Tom Hendrikx