Re: Design Check
On Thu, 28 Oct 2021 at 08:29, Felix Ingram wrote:
> On Thu, 28 Oct 2021 at 00:15, wrote:
>
>> [...]
>
> > I think my "creating users" was me wanting to make sure that when
>> > postfix
>> > passes an email for "bar...@mydomain.com" to Dovecot, then Dovecot
>> will
>> > store it and wait for
>> > someone to come along and impersonate barbaz. i.e. "barbaz" doesn't
>> > have to exist as a user
>> > already before Dovecot will store the mail.
>>
>> If you are using LMTP dovecot will only accept emails from postfix that
>> it can lookup the /directory/path to from one of the userdb{} or
>> passdb{} sections. If dovecot can not find a match in any of the
>> userdb{} or passdb{} it will reject the email as user unknown causing
>> postfix to send a undeliverable notice email back to the envelope sender
>> address, also known as back-scatter. I am not aware of a way to use
>> wildcard addresses in dovecot userdb{}, i don't think its possible but i
>> don't know what i don't know.
>>
>
> So I think this will be the main issue now - there's no way of knowing the
> addresses ahead of time, so it sounds like I'll need to add them to
> userdb{} when they
> hit postfix and before they get passed to dovecot.
>
Just to close the loop on this - I managed to get this working using
postfix's virtual aliases. I use
a postgresql function in the alias lookup that transforms '
tes...@foobar.mydomain.com' into
'foo...@mydomain.com' and at the same time inserts 'foo...@mydomain.com'
into the
Dovecot users table. I then have a separate passdb for master users that
can log in and
impersonate the foobar user.
So far this seems to work.
Thanks again to everyone for the help.
Felix
Re: Design Check
On Thu, 28 Oct 2021 at 00:15, wrote:
> > I think your approach would work, however, if I set
> > up aliases similar to:
> >
> > @barbaz.mydomain.com -> bar...@mydomain.com.
> >
> > I believe I can do that in postfix with some regex magic.
>
> Yes, that would work perfectly without any regex.
> You just point the catchall alias to the "user".
> @barbaz.mydomain.com -> bar...@mydomain.com
>
>
I've managed to get this working in postfix - I needed the regex rather
than
a static map, as I need to extract the unknown subdomain portion but it
seems
to be working. I have been able to get postfix to save it to a file as well
and it seems
to work as I expected.
> [..]
> > The purpose of the system is that users can create disposable/temporary
> > email addresses for various testing jobs.
>
> Are you aware of postfix recipient_delimiter? It allows for disposable /
> wild card addresses. If enabled in postfix, you setup a mailbox user
> like bar...@mydomain.com and any address with that user and the
> delimiter would still get delivered to that user.
>
> bar...@mydomain.com -> bar...@mydomain.com
> barbaz+randomt...@mydomain.com -> bar...@mydomain.com
> barbaz+te...@mydomain.com -> bar...@mydomain.com
>
> You can change the + to any symbol you want postfix to look out for.
>
We were using this approach on a different domain but our issue was that we
have
multiple people on the same piece of work and so they needed to share
access to
all of the mails. We decided on the approach I'm describing as we also
wanted to
have control at the DNS level to do this such as expiring addresses.
>
> > I think my "creating users" was me wanting to make sure that when
> > postfix
> > passes an email for "bar...@mydomain.com" to Dovecot, then Dovecot will
> > store it and wait for
> > someone to come along and impersonate barbaz. i.e. "barbaz" doesn't
> > have to exist as a user
> > already before Dovecot will store the mail.
>
> If you are using LMTP dovecot will only accept emails from postfix that
> it can lookup the /directory/path to from one of the userdb{} or
> passdb{} sections. If dovecot can not find a match in any of the
> userdb{} or passdb{} it will reject the email as user unknown causing
> postfix to send a undeliverable notice email back to the envelope sender
> address, also known as back-scatter. I am not aware of a way to use
> wildcard addresses in dovecot userdb{}, i don't think its possible but i
> don't know what i don't know.
>
So I think this will be the main issue now - there's no way of knowing the
addresses ahead of time, so it sounds like I'll need to add them to
userdb{} when they
hit postfix and before they get passed to dovecot.
For my sins I'm building this on Kubernetes so dovecot is on a separate
"machine" at the
moment. The userdb will be in postgres, as I'm using that for other things,
so I guess I'll need
to update that in postfix somewhere. This is a fairly low volume system, so
I can probably take
the hit of a DB query per email.
Currently postfix doesn't even seem to be attempting to talk to dovecot but
that's one for the
postfix list.
Thanks again for the help.
Cheers,
Felix
Re: Design Check
On Thu, 28 Oct 2021 at 07:40, Bernardo Reino wrote:
>
> > [...]
>
> Further to the responses you have received already, I'd like to note that
> if you
> want to receive mail at {alias}@{user}.mydomain.com then, at the time of
> *sending* the e-mail there needs to be an MX record for user, as otherwise
> the
> sender won't be able to connect to your (postfix) server.
>
> That means that the users will have to exist *before* postfix receives the
> message, and thus clearly before dovecot receives it.. so you may have to
> reconsider your requirement of adding users of on-the-fly.
>
Excellent point. So we are also using a DNS server with this (CoreDNS with
some custom plugins).
This means we are able to handle the dynamic MX records (plus also allowing
us to expire domains if
we need to).
Cheers,
Felix
Re: Design Check
On Wed, 27 Oct 2021, Felix Ingram wrote:
[...]
People would be able to send email to addresses that match the following
format:
us...@foobar.mydomain.com
us...@foobar.mydomain.com
us...@barbaz.mydomain.com
us...@barbaz.mydomain.com
[...]
I will be creating a web interface for users to get/set their credentials,
so can add those users on an adhoc basis, but I will need to have the
"foobar", "barbaz", etc users created whenever an email arrives (we won't
know ahead of time).
[...]
Further to the responses you have received already, I'd like to note that if you
want to receive mail at {alias}@{user}.mydomain.com then, at the time of
*sending* the e-mail there needs to be an MX record for user, as otherwise the
sender won't be able to connect to your (postfix) server.
That means that the users will have to exist *before* postfix receives the
message, and thus clearly before dovecot receives it.. so you may have to
reconsider your requirement of adding users of on-the-fly.
Of course, you could use a wildcard MX, but my understanding is that this can
cause problems (but I'd have to check in RFC1912 and RFC4592).
Cheers.
Re: Design Check
On 10-27-2021 11:10 pm, justina colmena ~biz wrote: Interesting. Have you looked at this? https://serverfault.com/questions/133190/host-wildcard-subdomains-using-postfix That makes sense and would work, setting domains and user addresses with perl regex expressions.
Re: Design Check
Interesting. Have you looked at this?
https://serverfault.com/questions/133190/host-wildcard-subdomains-using-postfix
[People have too much "flair" and rep points and I can't participate in those
stackexchange discussions or ask or answer like I used to.]
On October 27, 2021 3:15:01 PM AKDT, dove...@ptld.com wrote:
>> I think your approach would work, however, if I set
>> up aliases similar to:
>>
>> @barbaz.mydomain.com -> bar...@mydomain.com.
>>
>> I believe I can do that in postfix with some regex magic.
>
>Yes, that would work perfectly without any regex.
>You just point the catchall alias to the "user".
>@barbaz.mydomain.com -> bar...@mydomain.com
>
>
>
>> one stumbling block could be that we don't
>> know the various subdomains ahead of time.
>>
>> The subdomain can be any value that the user
>> wants, and we don't want them to have to
>> precreate them before they can use an address
>
>Best to my knowledge this is not possible with postfix. But ask the
>postfix mailing list to get a definitive answer. In postfix you have to
>tell it the domains it accepts mail for, anything else it considers
>relaying. Otherwise how does postfix know that email is meant to be
>saved here or it is just passing through and you want postfix to query
>DNS to find out where it goes (if relaying is even allowed).
>
>
>
>> The purpose of the system is that users can create disposable/temporary
>> email addresses for various testing jobs.
>
>Are you aware of postfix recipient_delimiter? It allows for disposable /
>wild card addresses. If enabled in postfix, you setup a mailbox user
>like bar...@mydomain.com and any address with that user and the
>delimiter would still get delivered to that user.
>
>bar...@mydomain.com -> bar...@mydomain.com
>barbaz+randomt...@mydomain.com -> bar...@mydomain.com
>barbaz+te...@mydomain.com -> bar...@mydomain.com
>
>You can change the + to any symbol you want postfix to look out for.
>
>
>
>> I think my "creating users" was me wanting to make sure that when
>> postfix
>> passes an email for "bar...@mydomain.com" to Dovecot, then Dovecot will
>> store it and wait for
>> someone to come along and impersonate barbaz. i.e. "barbaz" doesn't
>> have to exist as a user
>> already before Dovecot will store the mail.
>
>If you are using LMTP dovecot will only accept emails from postfix that
>it can lookup the /directory/path to from one of the userdb{} or
>passdb{} sections. If dovecot can not find a match in any of the
>userdb{} or passdb{} it will reject the email as user unknown causing
>postfix to send a undeliverable notice email back to the envelope sender
>address, also known as back-scatter. I am not aware of a way to use
>wildcard addresses in dovecot userdb{}, i don't think its possible but i
>don't know what i don't know.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: Design Check
I think your approach would work, however, if I set
up aliases similar to:
@barbaz.mydomain.com -> bar...@mydomain.com.
I believe I can do that in postfix with some regex magic.
Yes, that would work perfectly without any regex.
You just point the catchall alias to the "user".
@barbaz.mydomain.com -> bar...@mydomain.com
one stumbling block could be that we don't
know the various subdomains ahead of time.
The subdomain can be any value that the user
wants, and we don't want them to have to
precreate them before they can use an address
Best to my knowledge this is not possible with postfix. But ask the
postfix mailing list to get a definitive answer. In postfix you have to
tell it the domains it accepts mail for, anything else it considers
relaying. Otherwise how does postfix know that email is meant to be
saved here or it is just passing through and you want postfix to query
DNS to find out where it goes (if relaying is even allowed).
The purpose of the system is that users can create disposable/temporary
email addresses for various testing jobs.
Are you aware of postfix recipient_delimiter? It allows for disposable /
wild card addresses. If enabled in postfix, you setup a mailbox user
like bar...@mydomain.com and any address with that user and the
delimiter would still get delivered to that user.
bar...@mydomain.com -> bar...@mydomain.com
barbaz+randomt...@mydomain.com -> bar...@mydomain.com
barbaz+te...@mydomain.com -> bar...@mydomain.com
You can change the + to any symbol you want postfix to look out for.
I think my "creating users" was me wanting to make sure that when
postfix
passes an email for "bar...@mydomain.com" to Dovecot, then Dovecot will
store it and wait for
someone to come along and impersonate barbaz. i.e. "barbaz" doesn't
have to exist as a user
already before Dovecot will store the mail.
If you are using LMTP dovecot will only accept emails from postfix that
it can lookup the /directory/path to from one of the userdb{} or
passdb{} sections. If dovecot can not find a match in any of the
userdb{} or passdb{} it will reject the email as user unknown causing
postfix to send a undeliverable notice email back to the envelope sender
address, also known as back-scatter. I am not aware of a way to use
wildcard addresses in dovecot userdb{}, i don't think its possible but i
don't know what i don't know.
Re: Design Check
On Wed, 27 Oct 2021 at 18:27, wrote: > > On 10-27-2021 12:06 pm, Felix Ingram wrote: > > > > us...@foobar.mydomain.com > > us...@foobar.mydomain.com > > us...@barbaz.mydomain.com > > us...@barbaz.mydomain.com > > > > I would like all emails to the "foobar" subdomain to end up in their > > own mailbox and all emails to the "barbaz" subdomain to go to their own > > mailbox. > > Your question might be more suited to the postfix mailing list. Dovecot > doesn't receive mail from the internet, which i believe you understand > as you said "have postfix accepting the emails before passing them to > Dovecot". > > On the postfix side, one option would be using one mailbox and one > catchall for each subdomain. > > Setup a user: catch...@foobar.mydomain.com > Setup an alias: @foobar.mydomain.com -> catch...@foobar.mydomain.com > > Setup a user: catch...@barbaz.mydomain.com > Setup an alias: @barbaz.mydomain.com -> catch...@barbaz.mydomain.com > > On the dovecot side, you can setup each person with their own login user > and all of those users access the same IMAP inbox. Or you could just > give everyone the password to the same one mailbox > catch...@foobar.mydomain.com. > > So I think this would make sense, though one stumbling block could be that we don't know the various subdomains ahead of time. The purpose of the system is that users can create disposable/temporary email addresses for various testing jobs. The subdomain can be any value that the user wants, and we don't want them to have to precreate them before they can use an address (we have an existing system that works this way, and so we want to keep that behaviour). I think your approach would work, however, if I set up aliases similar to: @barbaz.mydomain.com -> bar...@mydomain.com. I believe I can do that in postfix with some regex magic. I would then want users to log in as "barbaz", and get access to all of the emails. I believe that if I create Dovecot users for my system users, and then set them as master users, then they will be able to log into Dovecot with something like: barbaz* as their username. Not sure "dovecot creating users" is the right way to think about it. > Dovecot simply looks for IMAP files where its told to look. In dovecot > config you setup flat files or databases that tell dovecot if someone > logs in with this user:pass then look in this /server/path for emails. > Other than that config, which you could point to a different > /server/path changing their inbox, there are no "accounts". > I think my "creating users" was me wanting to make sure that when postfix passes an email for "bar...@mydomain.com" to Dovecot, then Dovecot will store it and wait for someone to come along and impersonate barbaz. i.e. "barbaz" doesn't have to exist as a user already before Dovecot will store the mail. Thanks again for the pointers - I shall play with postfix local delivery before trying to wire up Dovecot. Regards, Felix
Re: Design Check
On 10-27-2021 12:06 pm, Felix Ingram wrote: us...@foobar.mydomain.com us...@foobar.mydomain.com us...@barbaz.mydomain.com us...@barbaz.mydomain.com I would like all emails to the "foobar" subdomain to end up in their own mailbox and all emails to the "barbaz" subdomain to go to their own mailbox. Your question might be more suited to the postfix mailing list. Dovecot doesn't receive mail from the internet, which i believe you understand as you said "have postfix accepting the emails before passing them to Dovecot". On the postfix side, one option would be using one mailbox and one catchall for each subdomain. Setup a user: catch...@foobar.mydomain.com Setup an alias: @foobar.mydomain.com -> catch...@foobar.mydomain.com Setup a user: catch...@barbaz.mydomain.com Setup an alias: @barbaz.mydomain.com -> catch...@barbaz.mydomain.com On the dovecot side, you can setup each person with their own login user and all of those users access the same IMAP inbox. Or you could just give everyone the password to the same one mailbox catch...@foobar.mydomain.com. Not sure "dovecot creating users" is the right way to think about it. Dovecot simply looks for IMAP files where its told to look. In dovecot config you setup flat files or databases that tell dovecot if someone logs in with this user:pass then look in this /server/path for emails. Other than that config, which you could point to a different /server/path changing their inbox, there are no "accounts".
