Notification email cannot be the same as reply by email


(Andrew Stroup) #1

I’ve setup the reply by email address settings as listed in the thread below, EXCEPT I’m unable to change the reply by email address

NOTE: I’ve setup everything else according to the post, to include the correct polling port (995), polling host ( and the accurate username/password combo (plus SSL enabled).

The field contains the following


When I try to change it to


I receive the following error

I’m currently receiving a polling error via AWS SES (our transactional email service) every 5m (POP3 polling frequency) and I’m guessing it’s because the reply by email address is incorrect, BUT I can’t change it. Help?

(Andrew Stroup) #2

Verified bug …

I can add BUT not a

Any idea on the time horizon to fix? Thanks!

(jaming) #3

Is the email you are trying to change it to the same as the SiteSetting.notification_email?

For example:
SiteSetting.notification_email = and you are trying to set it to “foo+%{reply_key}

(Andrew Stroup) #4

Hey @jaming that isn’t the issue. The issue is that the ranges of accepted domains in that field box doesn’t include .gov :frowning:

However, I assume, as long as the transactional email service (e.g. SES, Mandrill) can accept incoming email, it doesn’t matter if the notification_email email is the same as the reply by email address or not

(Jeff Atwood) #5

Weird can you reproduce this @techapj?

(Arpit Jalan) #6

Okay, I can repro this case, and it’s not specific to .gov domain.

@jaming is correct, this is because notification email setting is same as reply by email address.

Let’s say I set notification email to "", now I can’t set reply by email address to “team+%{reply_key}”, it will generate error as per this code:

So, if the notification email is set to "", then it’s not possible to set “team+%{reply_key}” as reply by email address.

Techincally it’s not a bug, it’s a feature which @zogstrip added via:

So I would recommend adding another email (perhaps reply+%{reply_key} for reply by email address setting.

(Jeff Atwood) #7

Can we improve the error message in this case? I agree this is an important safety feature otherwise @stroupaloop would have set up a cascading reply disaster, a sort of … loop :wink:

(Kane York) #8

Uh, I’m pretty sure there used to be a useful error message there. I think that’s a regression.

edit: yes, definitely a regression

(Arpit Jalan) #9

Yes, there was a regression due to this commit. Fixed via:

(Jeff Atwood) #10