Re: Email migration and MX records

2023-01-06 Thread Bruce Johnson via bind-users
y, January 4, 2023 7:17 AM To: bind-users@lists.isc.org<mailto:bind-users@lists.isc.org> Subject: Re: Email migration and MX records This email originated from outside of the organization. Use caution when replying, opening attachment(s), and/or clicking on URL's.

Re: Email migration and MX records

2023-01-06 Thread Mark Andrews
24 hours before returning as > undeliverable. > > > -- > William Brown > WNYRIC/Erie 1 BOCES > > -Original Message- > From: bind-users On Behalf Of Marcus Kool > Sent: Wednesday, January 4, 2023 7:17 AM > To: bind-users@lists.isc.org >

RE: Email migration and MX records

2023-01-06 Thread Brown, William
migration and MX records This email originated from outside of the organization. Use caution when replying, opening attachment(s), and/or clicking on URL's. SMTP is a wonderful protocol that queues messages and retries delivery for 5 days so a non-responsive email server is no

Re: Email migration and MX records

2023-01-04 Thread Matthew Richardson
Bruce Johnson via bind-users wrote:- >We’re making an O365 tenant switchover for our domain (a subdomain of the >arizona.edu domain) and moving from our Barracuda cloud email SMTP to the >University’s tenant, but email cannot flow until the Arizona.edu O365 tenant >can take over our email doma

RE: Email migration and MX records

2023-01-04 Thread E R
Bruce, I would push back and ask for more information from whomever is leading you down that path as it does not sound right to me although others more familiar with DNS magic might have better suggestions to DNS changes. But if Barracuda is just a front-end for email that does antivirus/spam filte

Re: Email migration and MX records

2023-01-04 Thread Marcus Kool
SMTP is a wonderful protocol that queues messages and retries delivery for 5 days so a non-responsive email server is no issue. Just do not have a temporary solution that bounces emails since those will never arrive (the sender is notified about the bounce). Marcus On 03/01/2023 21:31, Bruce J

RE: Email migration and MX records

2023-01-03 Thread John W. Blue via bind-users
Hi Bruce, It would be better to have an SMTP server return 421 "4.3.0" or 421 "4.7.0" while the migration is under way instead of bouncing the connection. 421 will tell all SMTP servers everywhere to "try again later". The 421 error is a proven greylisting configuration. Not knowing what is

RE: Email migration and MX records

2023-01-03 Thread Richard T.A. Neal
Hi Bruce, This is something I'm presently battling with as well. My current previously tested plan is: 1. Create all user accounts (with NEW email addresses) on the new email system 2. Setup a temporary forwarder on an existing *temporary* email server (we use hMail) which forwards all email se