A tad confused about mapping virtual users to system users in Dovecot
What I hope to do:
- Use getmail to grab emails from several of my accounts (gmail, fastmail, Yahoo etc) ->
- deliver to an instance of Dovecot running locally ->
- from which I'll use a mail client to access my emails
Sending isn't a goal for now.
What I don't know: how to map account1@gmail.com and myveryoldaccount@yahoo.com to iain the system account.
I'm looking at virtual users but every discussion either mentions:
- Postfix, which I'm not using (as yet)
- Editing /etc/passwd
Focussing on (2), I've already set up authentication via PAM and I'm not really interested in fiddling around with /etc/passwd. Is there not something available like?
# Some barely spoken about file
iain: account1@gmail.com, myveryoldaccount@yahoo.com
# dovecot.conf
address_mapping: use_barely_spoken_about_file
My conf.d/auth-system.conf.ext has the following (I'm not sure it's relevant or not):
passdb {
driver = pam
args = dovecot
}
userdb {
# <doc/wiki/AuthDatabase.Passwd.txt>
driver = passwd
# [blocking=no]
# see https://trac.macports.org/wiki/howto/SetupDovecot
args =
}
The Macports link has:
Together, these prevent the need for hardcoded passwd.dovecot and
userdb.dovecot files, and don't require any knowledge of LDAP.
However, they only support system usernames, and not virtual
mailboxes. I have tested this with IMAP and the dovecot LDA (deliver)
successfully.
Should I simply replace getmail with Postfix? That seems like a lot of extra work, getmail is simple to setup.
Does the barely_spoken_about_file exist, or is it really /etc/passwd?
Can I still authenticate via PAM?
Any help or insight, or just a nudge towards to right article would be much appreciated.
email dovecot
|
show 1 more comment
What I hope to do:
- Use getmail to grab emails from several of my accounts (gmail, fastmail, Yahoo etc) ->
- deliver to an instance of Dovecot running locally ->
- from which I'll use a mail client to access my emails
Sending isn't a goal for now.
What I don't know: how to map account1@gmail.com and myveryoldaccount@yahoo.com to iain the system account.
I'm looking at virtual users but every discussion either mentions:
- Postfix, which I'm not using (as yet)
- Editing /etc/passwd
Focussing on (2), I've already set up authentication via PAM and I'm not really interested in fiddling around with /etc/passwd. Is there not something available like?
# Some barely spoken about file
iain: account1@gmail.com, myveryoldaccount@yahoo.com
# dovecot.conf
address_mapping: use_barely_spoken_about_file
My conf.d/auth-system.conf.ext has the following (I'm not sure it's relevant or not):
passdb {
driver = pam
args = dovecot
}
userdb {
# <doc/wiki/AuthDatabase.Passwd.txt>
driver = passwd
# [blocking=no]
# see https://trac.macports.org/wiki/howto/SetupDovecot
args =
}
The Macports link has:
Together, these prevent the need for hardcoded passwd.dovecot and
userdb.dovecot files, and don't require any knowledge of LDAP.
However, they only support system usernames, and not virtual
mailboxes. I have tested this with IMAP and the dovecot LDA (deliver)
successfully.
Should I simply replace getmail with Postfix? That seems like a lot of extra work, getmail is simple to setup.
Does the barely_spoken_about_file exist, or is it really /etc/passwd?
Can I still authenticate via PAM?
Any help or insight, or just a nudge towards to right article would be much appreciated.
email dovecot
I'm not sure why you're trying to map mailboxes that don't belong to your server in the first place? Is that something getmail requires? (If it did, most people would have been unable to use it...)
– grawity
Jan 28 at 8:59
Reading the getmail man oage I would be very surprised if getmail is deliverjng mail through dovecot - in fact I dont think dovecot supports this. I expect its simlly writing mail in a standard firnat and dovecot reads it. This neans looking to dovecot is looking in the wrong place.
– davidgo
Jan 28 at 9:14
@davidgo getmail is acting as the Mail Retrieval Agent and Dovecot is acting as the Local Delivery agent. I can invoke getmail to deliver to a directory on my box but then messages are siloed and I lose the things that Dovecot can do, like filtering and funneling the messages to one receiver.
– Iain
Jan 28 at 14:58
@grawity getmail will simply fetch mail given the address and account details. What I want is to take those disparate accounts and funnel them to one recipient who owns the accounts. I believe (because I've seen some articles where people do something similar but not quite, for example) Dovecot should be able to take the messages from getmail and do this, but I'm not sure how to configure the mapping.
– Iain
Jan 28 at 15:02
Ah, if it works anything likefetchmail
used to, then I don't think you need to map these addresses as accounts at all; getmail delivers everything via LDA to a single regular Dovecot account. Instead, I think you need to use Dovecot's Sieve module to filter/sort based on "Delivered-To:" or similar headers.
– grawity
Jan 28 at 15:31
|
show 1 more comment
What I hope to do:
- Use getmail to grab emails from several of my accounts (gmail, fastmail, Yahoo etc) ->
- deliver to an instance of Dovecot running locally ->
- from which I'll use a mail client to access my emails
Sending isn't a goal for now.
What I don't know: how to map account1@gmail.com and myveryoldaccount@yahoo.com to iain the system account.
I'm looking at virtual users but every discussion either mentions:
- Postfix, which I'm not using (as yet)
- Editing /etc/passwd
Focussing on (2), I've already set up authentication via PAM and I'm not really interested in fiddling around with /etc/passwd. Is there not something available like?
# Some barely spoken about file
iain: account1@gmail.com, myveryoldaccount@yahoo.com
# dovecot.conf
address_mapping: use_barely_spoken_about_file
My conf.d/auth-system.conf.ext has the following (I'm not sure it's relevant or not):
passdb {
driver = pam
args = dovecot
}
userdb {
# <doc/wiki/AuthDatabase.Passwd.txt>
driver = passwd
# [blocking=no]
# see https://trac.macports.org/wiki/howto/SetupDovecot
args =
}
The Macports link has:
Together, these prevent the need for hardcoded passwd.dovecot and
userdb.dovecot files, and don't require any knowledge of LDAP.
However, they only support system usernames, and not virtual
mailboxes. I have tested this with IMAP and the dovecot LDA (deliver)
successfully.
Should I simply replace getmail with Postfix? That seems like a lot of extra work, getmail is simple to setup.
Does the barely_spoken_about_file exist, or is it really /etc/passwd?
Can I still authenticate via PAM?
Any help or insight, or just a nudge towards to right article would be much appreciated.
email dovecot
What I hope to do:
- Use getmail to grab emails from several of my accounts (gmail, fastmail, Yahoo etc) ->
- deliver to an instance of Dovecot running locally ->
- from which I'll use a mail client to access my emails
Sending isn't a goal for now.
What I don't know: how to map account1@gmail.com and myveryoldaccount@yahoo.com to iain the system account.
I'm looking at virtual users but every discussion either mentions:
- Postfix, which I'm not using (as yet)
- Editing /etc/passwd
Focussing on (2), I've already set up authentication via PAM and I'm not really interested in fiddling around with /etc/passwd. Is there not something available like?
# Some barely spoken about file
iain: account1@gmail.com, myveryoldaccount@yahoo.com
# dovecot.conf
address_mapping: use_barely_spoken_about_file
My conf.d/auth-system.conf.ext has the following (I'm not sure it's relevant or not):
passdb {
driver = pam
args = dovecot
}
userdb {
# <doc/wiki/AuthDatabase.Passwd.txt>
driver = passwd
# [blocking=no]
# see https://trac.macports.org/wiki/howto/SetupDovecot
args =
}
The Macports link has:
Together, these prevent the need for hardcoded passwd.dovecot and
userdb.dovecot files, and don't require any knowledge of LDAP.
However, they only support system usernames, and not virtual
mailboxes. I have tested this with IMAP and the dovecot LDA (deliver)
successfully.
Should I simply replace getmail with Postfix? That seems like a lot of extra work, getmail is simple to setup.
Does the barely_spoken_about_file exist, or is it really /etc/passwd?
Can I still authenticate via PAM?
Any help or insight, or just a nudge towards to right article would be much appreciated.
email dovecot
email dovecot
asked Jan 28 at 8:53
IainIain
136312
136312
I'm not sure why you're trying to map mailboxes that don't belong to your server in the first place? Is that something getmail requires? (If it did, most people would have been unable to use it...)
– grawity
Jan 28 at 8:59
Reading the getmail man oage I would be very surprised if getmail is deliverjng mail through dovecot - in fact I dont think dovecot supports this. I expect its simlly writing mail in a standard firnat and dovecot reads it. This neans looking to dovecot is looking in the wrong place.
– davidgo
Jan 28 at 9:14
@davidgo getmail is acting as the Mail Retrieval Agent and Dovecot is acting as the Local Delivery agent. I can invoke getmail to deliver to a directory on my box but then messages are siloed and I lose the things that Dovecot can do, like filtering and funneling the messages to one receiver.
– Iain
Jan 28 at 14:58
@grawity getmail will simply fetch mail given the address and account details. What I want is to take those disparate accounts and funnel them to one recipient who owns the accounts. I believe (because I've seen some articles where people do something similar but not quite, for example) Dovecot should be able to take the messages from getmail and do this, but I'm not sure how to configure the mapping.
– Iain
Jan 28 at 15:02
Ah, if it works anything likefetchmail
used to, then I don't think you need to map these addresses as accounts at all; getmail delivers everything via LDA to a single regular Dovecot account. Instead, I think you need to use Dovecot's Sieve module to filter/sort based on "Delivered-To:" or similar headers.
– grawity
Jan 28 at 15:31
|
show 1 more comment
I'm not sure why you're trying to map mailboxes that don't belong to your server in the first place? Is that something getmail requires? (If it did, most people would have been unable to use it...)
– grawity
Jan 28 at 8:59
Reading the getmail man oage I would be very surprised if getmail is deliverjng mail through dovecot - in fact I dont think dovecot supports this. I expect its simlly writing mail in a standard firnat and dovecot reads it. This neans looking to dovecot is looking in the wrong place.
– davidgo
Jan 28 at 9:14
@davidgo getmail is acting as the Mail Retrieval Agent and Dovecot is acting as the Local Delivery agent. I can invoke getmail to deliver to a directory on my box but then messages are siloed and I lose the things that Dovecot can do, like filtering and funneling the messages to one receiver.
– Iain
Jan 28 at 14:58
@grawity getmail will simply fetch mail given the address and account details. What I want is to take those disparate accounts and funnel them to one recipient who owns the accounts. I believe (because I've seen some articles where people do something similar but not quite, for example) Dovecot should be able to take the messages from getmail and do this, but I'm not sure how to configure the mapping.
– Iain
Jan 28 at 15:02
Ah, if it works anything likefetchmail
used to, then I don't think you need to map these addresses as accounts at all; getmail delivers everything via LDA to a single regular Dovecot account. Instead, I think you need to use Dovecot's Sieve module to filter/sort based on "Delivered-To:" or similar headers.
– grawity
Jan 28 at 15:31
I'm not sure why you're trying to map mailboxes that don't belong to your server in the first place? Is that something getmail requires? (If it did, most people would have been unable to use it...)
– grawity
Jan 28 at 8:59
I'm not sure why you're trying to map mailboxes that don't belong to your server in the first place? Is that something getmail requires? (If it did, most people would have been unable to use it...)
– grawity
Jan 28 at 8:59
Reading the getmail man oage I would be very surprised if getmail is deliverjng mail through dovecot - in fact I dont think dovecot supports this. I expect its simlly writing mail in a standard firnat and dovecot reads it. This neans looking to dovecot is looking in the wrong place.
– davidgo
Jan 28 at 9:14
Reading the getmail man oage I would be very surprised if getmail is deliverjng mail through dovecot - in fact I dont think dovecot supports this. I expect its simlly writing mail in a standard firnat and dovecot reads it. This neans looking to dovecot is looking in the wrong place.
– davidgo
Jan 28 at 9:14
@davidgo getmail is acting as the Mail Retrieval Agent and Dovecot is acting as the Local Delivery agent. I can invoke getmail to deliver to a directory on my box but then messages are siloed and I lose the things that Dovecot can do, like filtering and funneling the messages to one receiver.
– Iain
Jan 28 at 14:58
@davidgo getmail is acting as the Mail Retrieval Agent and Dovecot is acting as the Local Delivery agent. I can invoke getmail to deliver to a directory on my box but then messages are siloed and I lose the things that Dovecot can do, like filtering and funneling the messages to one receiver.
– Iain
Jan 28 at 14:58
@grawity getmail will simply fetch mail given the address and account details. What I want is to take those disparate accounts and funnel them to one recipient who owns the accounts. I believe (because I've seen some articles where people do something similar but not quite, for example) Dovecot should be able to take the messages from getmail and do this, but I'm not sure how to configure the mapping.
– Iain
Jan 28 at 15:02
@grawity getmail will simply fetch mail given the address and account details. What I want is to take those disparate accounts and funnel them to one recipient who owns the accounts. I believe (because I've seen some articles where people do something similar but not quite, for example) Dovecot should be able to take the messages from getmail and do this, but I'm not sure how to configure the mapping.
– Iain
Jan 28 at 15:02
Ah, if it works anything like
fetchmail
used to, then I don't think you need to map these addresses as accounts at all; getmail delivers everything via LDA to a single regular Dovecot account. Instead, I think you need to use Dovecot's Sieve module to filter/sort based on "Delivered-To:" or similar headers.– grawity
Jan 28 at 15:31
Ah, if it works anything like
fetchmail
used to, then I don't think you need to map these addresses as accounts at all; getmail delivers everything via LDA to a single regular Dovecot account. Instead, I think you need to use Dovecot's Sieve module to filter/sort based on "Delivered-To:" or similar headers.– grawity
Jan 28 at 15:31
|
show 1 more comment
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399160%2fa-tad-confused-about-mapping-virtual-users-to-system-users-in-dovecot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1399160%2fa-tad-confused-about-mapping-virtual-users-to-system-users-in-dovecot%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I'm not sure why you're trying to map mailboxes that don't belong to your server in the first place? Is that something getmail requires? (If it did, most people would have been unable to use it...)
– grawity
Jan 28 at 8:59
Reading the getmail man oage I would be very surprised if getmail is deliverjng mail through dovecot - in fact I dont think dovecot supports this. I expect its simlly writing mail in a standard firnat and dovecot reads it. This neans looking to dovecot is looking in the wrong place.
– davidgo
Jan 28 at 9:14
@davidgo getmail is acting as the Mail Retrieval Agent and Dovecot is acting as the Local Delivery agent. I can invoke getmail to deliver to a directory on my box but then messages are siloed and I lose the things that Dovecot can do, like filtering and funneling the messages to one receiver.
– Iain
Jan 28 at 14:58
@grawity getmail will simply fetch mail given the address and account details. What I want is to take those disparate accounts and funnel them to one recipient who owns the accounts. I believe (because I've seen some articles where people do something similar but not quite, for example) Dovecot should be able to take the messages from getmail and do this, but I'm not sure how to configure the mapping.
– Iain
Jan 28 at 15:02
Ah, if it works anything like
fetchmail
used to, then I don't think you need to map these addresses as accounts at all; getmail delivers everything via LDA to a single regular Dovecot account. Instead, I think you need to use Dovecot's Sieve module to filter/sort based on "Delivered-To:" or similar headers.– grawity
Jan 28 at 15:31