OH yeah, forgot to mention. WIthout anything there in /var/run/saslauthd, saslauthd failed to start and I didn't notice at first so I think my assumption about being open relay a that point was probably not that far from true.

thx for the fast answers ...

but now i am a bit confused ...

i i have done the steps from joe, without the replacement of dovecot ....

but i get the same error message in outlook and outlook express as before

maybe, one of u can give me a step by step instruction, what to do now ( my gf is a bit angry about using webmail all the time and gf angry = no dinner and no ... urgs )

;)

ok, i tried to install dovecot again, like tom did...
made steps joe mentioned

no go :(


dovecot seems to be a real great piece of software, but ... its not useable for me at the moment, cuz all external clients fails to login allways the same error in outlook : network or timeout error.
and i cant tell all people, to use the webmailclient, this is not the intend and the most companys i know, have locked all web ports for their users, without the ports for outlook/outlook-express).

so, the question is , if there is a working solution for this problem, or is there an alternative to dovecot within webmin-virtualmin ( without setting up the whole box again) ?

actually, my mailbox is full of mails releating to the missing outlook support, by my girlfriends company, so that i need to think about an external mailserver and deactivat all email features for domains inside virtualmin-webmin.


greez from switzerland

Hey Richard,

Contact me via email. I can login and straighten it out for you.

Dovecot does work. It's just ornery to configure on Debian/Ubuntu (it doesn't require installing different versions--the stock version works, and any version requires the extra configuration to make them work within the Postfix chroot).

Oops...Silly me. Dovecot doesn't need to be in the chroot. saslauthd is the bit that has to be tweaked for the chroot.

But, nonetheless, we can make Dovecot work--and the bug in Webmin that misdetects the odd default version will be corrected soon (and there is a workaround).

send u an mail with all logins and ports yesterday :)

but i f u are short of time, maybe u can explain me, what to do, to fix this damn problem ..

greez from switzerland :)

hmm, seems, the problem is not solvable at the moment ..... so
i will setup an extra mailserver on a different box , maybe with plesk ( arrghh ) but thx for the help anyway

Hey Richard,

It's solvable. I'm just swamped and working on a dozen different client boxes (so I'm actually losing track of who has what problem!). But I'll get it straightened out for you tonight.

You just had the Dovecot configuration file format confusion issue right?

WIthout anything there in /var/run/saslauthd, saslauthd failed to start and I didn't notice at first so I think my assumption about being open relay a that point was probably not that far from true.

I wanted to reply to this (despite the conversation having moved well past it) as mentions of open relays are nothing to leave hanging.

In this case, you wouldn't have an open relay. Postfix would always fail to authenticate--this wouldn't result in an open relay. Instead it would result in a completely closed relay (except for local clients and those otherwise explicitly allowed by other rules). If you were seeing anything resembling open relay behavior we need to look really closely at your smtpd_recipient_restrictions. Something would have to be wrong with them. Our default is:

permit_mynetworks permit_sasl_authenticated reject_unauth_destination

Anything beyond that (or any change of order) could very well open your server up in unintended ways.