Always accept postmaster email for virtual domains

[rimas-kudelis]

I wonder what currently happens if we accept an e-mail to postmaster for a virtual domain which doesn't have a postmaster mailbox/forward. When I fix #218, we'll probably start rejecting such e-mails instead. Since RFC's require us to have such address, I'm thinking what options we have.

1. We could create the postmaster address automatically, and not allow deleting it. This would however make it impossible to turn it into a forward using conventional means.
2. We could redirect all our postmaster email to the main postmaster address on localhost, or at least fall back to that.
3. We could test if the postmaster address exists when domain admin logs in, and if it doesn't, display a big fat red warning on top of the page. This would act as a reminder, but wouldn't be strictly enforcing. Although we could also disallow creation of any other mailboxes/aliases until postmaster is created.
4. Combine 3 and 2 ?

[Udera]

Is there a problem keeping a postmaster account? You can even forward
mails to other addresses if you want. This way we would not need to
check anything in exim or forward mails to an admin account in case no
postmaster is defined.

A fallback to the localhost is not so good either because some people
only use virtual domains and may not check localhost-mails.

On 2016-09-15 15:55, Rimas Kudelis wrote:

I wonder what currently happens if we accept an e-mail to postmaster
for a virtual domain which doesn't have a postmaster mailbox/forward.
When I fix #218 [1], we'll probably start rejecting such e-mails
instead. Since RFC's require us to have such address, I'm thinking
what options we have.

• We could create the postmaster address automatically, and not
  allow deleting it. This would however make it impossible to turn it
  into a forward using conventional means.
• We could redirect all our postmaster email to the main postmaster
  address on localhost, or at least fall back to that.
• We could test if the postmaster address exists when domain admin
  logs in, and if it doesn't, display a big fat red warning on top of
  the page. This would act as a reminder, but wouldn't be strictly
  enforcing. Although we could also disallow creation of any other
  mailboxes/aliases until postmaster is created.
• Combine 3 and 2 ?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [2], or mute the
thread [3].

Links:

[1] #218
[2] #228
[3]
https://github.com/notifications/unsubscribe-auth/AGCFFKor-S86_yHDEoChSZFIKoqJPIDAks5qqU41gaJpZM4J95cJ

[rimas-kudelis]

The problem is that the postmaster account can be deleted and not re-created.

[Udera]

I understand the initial issue and we need to do something about it. I
was only thinking if there might be a legitimate reason to delete the
account and use a simple forwarder instead (you can forward mail from an
account as well).

On 2016-09-15 17:25, Rimas Kudelis wrote:

On 2016 m. rugsėjis 15 d. 18:16:42 EEST, Udera
notifications@github.com wrote:

Is there a problem keeping a postmaster account? You can even forward

mails to other addresses if you want. This way we would not need to
check anything in exim or forward mails to an admin account in case
no
postmaster is defined.

A fallback to the localhost is not so good either because some people

only use virtual domains and may not check localhost-mails.

On 2016-09-15 15:55, Rimas Kudelis wrote:

I wonder what currently happens if we accept an e-mail to
postmaster
for a virtual domain which doesn't have a postmaster
mailbox/forward.
When I fix #218 [1], we'll probably start rejecting such e-mails
instead. Since RFC's require us to have such address, I'm thinking
what options we have.

• We could create the postmaster address automatically, and not
  allow deleting it. This would however make it impossible to turn it
  into a forward using conventional means.
• We could redirect all our postmaster email to the main postmaster
  address on localhost, or at least fall back to that.
• We could test if the postmaster address exists when domain admin
  logs in, and if it doesn't, display a big fat red warning on top of
  the page. This would act as a reminder, but wouldn't be strictly
  enforcing. Although we could also disallow creation of any other
  mailboxes/aliases until postmaster is created.
• Combine 3 and 2 ?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [2], or mute the
thread [3].

Links:

[1] #218
[2] #228
[3]

https://github.com/notifications/unsubscribe-auth/AGCFFKor-S86_yHDEoChSZFIKoqJPIDAks5qqU41gaJpZM4J95cJ

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#228 (comment)

The problem is that the postmaster account can be deleted and not

re-created.

Rimas
Sent from a mobile phone, please excuse potential typos in this
message

You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].

Links:

[1] #228 (comment)
[2]
https://github.com/notifications/unsubscribe-auth/AGCFFOCgvBThY1W4LF0pPfBLZhj71wWiks5qqWNygaJpZM4J95cJ

[rimas-kudelis]

Of course, wanting to re-create the account as an alias is a valid reason. That's why I don't want to just block deleting it. :-)

[Udera]

Why is it a valid reason. What can the redirect do what a real account
cannot? You can forward mails to different addresses without keeping a
local copy.

On 2016-09-15 18:10, Rimas Kudelis wrote:

On 2016 m. rugsėjis 15 d. 18:55:33 EEST, Udera
notifications@github.com wrote:

I understand the initial issue and we need to do something about it.
I
was only thinking if there might be a legitimate reason to delete the

account and use a simple forwarder instead (you can forward mail from
an
account as well).

On 2016-09-15 17:25, Rimas Kudelis wrote:

On 2016 m. rugsėjis 15 d. 18:16:42 EEST, Udera
notifications@github.com wrote:

Is there a problem keeping a postmaster account? You can even
forward

mails to other addresses if you want. This way we would not need
to
check anything in exim or forward mails to an admin account in
case
no
postmaster is defined.

A fallback to the localhost is not so good either because some
people

only use virtual domains and may not check localhost-mails.

On 2016-09-15 15:55, Rimas Kudelis wrote:

I wonder what currently happens if we accept an e-mail to
postmaster
for a virtual domain which doesn't have a postmaster
mailbox/forward.
When I fix #218 [1], we'll probably start rejecting such e-mails
instead. Since RFC's require us to have such address, I'm
thinking
what options we have.

• We could create the postmaster address automatically, and not
  allow deleting it. This would however make it impossible to turn
  it
  into a forward using conventional means.
• We could redirect all our postmaster email to the main
  postmaster
  address on localhost, or at least fall back to that.
• We could test if the postmaster address exists when domain
  admin
  logs in, and if it doesn't, display a big fat red warning on top
  of
  the page. This would act as a reminder, but wouldn't be strictly
  enforcing. Although we could also disallow creation of any other
  mailboxes/aliases until postmaster is created.
• Combine 3 and 2 ?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [2], or mute the
thread [3].

Links:

[1] #218
[2] #228
[3]

https://github.com/notifications/unsubscribe-auth/AGCFFKor-S86_yHDEoChSZFIKoqJPIDAks5qqU41gaJpZM4J95cJ

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#228 (comment)

The problem is that the postmaster account can be deleted and not

re-created.

Rimas
Sent from a mobile phone, please excuse potential typos in this
message

You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].

Links:

[1]
#228 (comment)
[2]

https://github.com/notifications/unsubscribe-auth/AGCFFOCgvBThY1W4LF0pPfBLZhj71wWiks5qqWNygaJpZM4J95cJ

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#228 (comment)

Of course, wanting to re-create the account as an alias is a valid

reason. That's why I don't want to just block deleting it. :-)

Rimas
Sent from a mobile phone, please excuse potential typos in this
message

You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or mute the
thread [2].

Links:

[1] #228 (comment)
[2]
https://github.com/notifications/unsubscribe-auth/AGCFFHejPMlR4dkUpOcc6-NOc_c2iLeOks5qqW31gaJpZM4J95cJ

[rimas-kudelis]

OK, I misunderstood your comments. I didn't think about this. Indeed, even a conventional account can act as a forward. Should we block deleting postmasters then?

[Udera]

Should we block deleting postmasters then?

Yes, it's probably the easiest. How do we handle migrated setups that already deleted the postmaster account? Just create it, or enforce it in some way?

[rimas-kudelis]

This is almost the same question as what I asked initially. :)
If we choose to just nag the admins, then there's no reason not to allow deleting that account and creating it anew. Creating the account automatically is an interesting idea. When and how would you do that?

[Udera]

I would do a postmaster-check after the login of a domain-admin. It checks if there is either

• postmaster-account
• postmaster-redirect
• catchall-account

If there isn't, it either

• redirects you to the adminuseradd to create a postmaster@yourdomain
• directly creates the account with a random password (just use the sql-insert from adminuseraddsubmit)

I tend to use the second option because it doesn't disturb the admin so much (if you only want to reset a password for a user, you don't want to deal with such stuff). However, we risk that the new postmaster-account will not be noticed.

[rimas-kudelis]

We could also create postmaster as an alias to this current admin account.

But I'm not sure if any of that is the best approach, because you never know when the admin is about to log in, and this doesn't ensure that postmaster will be available when necessary.

Maybe a yet another option would be to create a new router which would deliver postmaster e-mails to all admins of the affected domain? It will only be reached when explicit postmaster account doesn't exist, so seems like quite an elegant solution to me. This way we would also not have to block deletion and creation of postmaster account in the UI.

Of course it's possible for a domain to have no admins at all, but highly unlikely.