Good Morning,
I am currently trying to restructure the way emails are received. Currently we have a setup with @domain1.com working perfectly fine, but now we want people to be able to send emails to @domain2.com instead of @domain1.com. Since everything would be staying the same except for the domain switch, I figured I could setup like an email distribution list under the new domain the forwards to the old domain. I am looking to configure distribution list on domain2 that sends email to actual email on domain1. Currently with everything I have configured, I am receiving this error message from Gmail:
552 Mail rejected by the processing module: Message posting request rejected by mailing list. Reason: message received has invalid format.
If there is a more appropriate method to accomplish what I want to achieve, I am always open to suggestions. Any help that can be provided is greatly appreciated.
Best Regards.
Hello,
The error you mention is generated by the value of “Allow only messages with the following content type” parameter set for your mailing list that by default is set to “Text/Plain”. The option is available in Webadmin -> Domain & Accounts -> Mailiing lists -> edit your list -> Subscription and Posting
An alternate solution for your account to receive the messages that are received using @domain2.com is to add @domain2.com as alias of @domain1.com.
Regards,
Florin
Florin,
Thanks! That seems to have resolved the issue.
The domain alias solution you recommended, would that work even if the two domains are @domain1.com and @domain2.net? When I try to add the alias it allows me to put the front portion, but not the .net. Is there something I’m doing wrong there? Please let me know, thanks.
Best Regards,
Hello,
Yes, will work with .net or any other top level domain (.ro, .co uk, .org., etc). An error will occur if you are trying to add domain2.net as alias of domain1.com and this domain (domain2.net) is also configured as a standalone domain.
Regards,
Florin
Florin,
You are correct. I stumbled across this solution yesterday, but when I wasn’t able to add the second domain as an alias, I just moved on. The issue is that I had already added the domain as a standalone. I’ve since went in and corrected this. Thanks for all of your help.
Best Regards,
