Mail format

16 posts / 0 new
Last post
#1 Fri, 01/06/2017 - 07:51
AqpJoe

Mail format

Hello guys, I explain my problem: every time we create a user in the panel virtualmin is automatically created user.mydominio@mydominio.com .... we want it to have this format user@mydominio.com

Thankful for your help.

Sat, 01/07/2017 - 17:48
unborn
unborn's picture

hi, you looking for Format for usernames that include domain in Server Templates -> Default -> Mail for Domain tab, you can set the username format there. But, that only is changed for new users. If you want to change existing users, you'd need to delete the account and re-add it.

its located at the bottom of the page, you want to change it to same as on picture below.

img

This has been answered here as well.

Configuring/troubleshooting Debian servers is always great fun

Mon, 01/09/2017 - 08:48 (Reply to #2)
AqpJoe

Hi thanks for replying, I already did that, the mails are sent with user@mydomain.com .. but to be answered from any server there is an error:

  ... I'm sorry to have informed you that your message could not Be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do not, please include this problem report. you can Delete your own text from the attached returned message. ....

With the format user.mydominio@mydominio.com the emails are sent and answered without any problem.

Mon, 01/09/2017 - 09:02 (Reply to #3)
unborn
unborn's picture

hi,

well one more time same hint : that only is changed for new users. If you want to change existing users, you'd need to delete the account and re-add it.Once you delete that user and then (re-)add that user to domain for email, the new user login should be automatically in format USERNAME @ domain.com and not user.mydomain @ mydomain.com

Configuring/troubleshooting Debian servers is always great fun

Mon, 01/09/2017 - 09:14 (Reply to #4)
AqpJoe

hi, The commented error is with new users, the previous user accounts were deleted. Also was tried with a new domain with the format user@mydomain.com, the problem persists when replying the mails.

:(

Mon, 01/09/2017 - 09:17 (Reply to #5)
unborn
unborn's picture

well.. what distro is that? also it should work for newly created users.. can you create user like test@yourdomain.com and I can try to send you an email. Perhaps you pop up on irc chat and we can troubleshoot it live.

Configuring/troubleshooting Debian servers is always great fun

Mon, 01/09/2017 - 09:32 (Reply to #6)
AqpJoe

The operating system is Debian 8, we have a test@mygepeese.com account, you can send an email and it will be rejected, but if I can send you an email from that account without problems ... at the moment I can not access a chat Irc

Mon, 01/09/2017 - 09:42 (Reply to #7)
unborn
unborn's picture

sorry I didnt press reply button.. reply is bellow

Configuring/troubleshooting Debian servers is always great fun

Mon, 01/09/2017 - 09:40
unborn
unborn's picture

hi, yes you are correct however the error msgs I recieved was this:

This is the mail system at host server.redampperu.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <test-mygepeese.com@server.redampperu.com> (expanded from <test@mygepeese.com>): mail for server.redampperu.com loops back to myself Reporting-MTA: dns; server.redampperu.com X-Postfix-Queue-ID: E01D221875 X-Postfix-Sender: rfc822; [hidden]@gmail.com Arrival-Date: Mon, 9 Jan 2017 10:32:57 -0500 (PET) Final-Recipient: rfc822; test-mygepeese.com@server.redampperu.com Original-Recipient: rfc822;test@mygepeese.com Action: failed Status: 5.4.6 Diagnostic-Code: X-Postfix; mail for server.redampperu.com loops back to myself

I think your config is messed up a bit, did you changed any settings? perhaps dns or some config in postfix if you done manual changes to them.. I also run debian (latest version) and have no issues.. also does command hostname and hostname -f respond with same output?

Configuring/troubleshooting Debian servers is always great fun

Mon, 01/09/2017 - 09:47
AqpJoe

The output of the hostname is: root@server:~# hostname -f server.redampperu.com Our company will host 3 virtual servers for its services, the configuration of mail is the one that comes by default when installing virtualmin / webmin

When it has the format user.mydomain@mydomain.com there is no problem in sending and receiving mail.

Mon, 01/09/2017 - 10:06 (Reply to #10)
unborn
unborn's picture

sure then it could be dns issue.. in mean time commands should respond like this:

:~# hostname server.redampperu.com :~# hostname -f server.redampperu.com

If they dont, then its not set up correctly which could lead to funny issues. Your issue is that mail for server.redampperu.com loops back to myself. You can search on google but mostly FQDN causes those issues.

Configuring/troubleshooting Debian servers is always great fun

Mon, 01/09/2017 - 17:46
Diabolico
Diabolico's picture

If mygepeese.com is your domain you have a nice mess with your settings, Bind to point on one.

For mygepeese.com - https://intodns.com/mygepeese.com

  • several problems what must be sorted and can affect a lot of things, email is for sure one of them

But mygepeese.com is using nameservers of redampperu.com and here we have even more DNS probelms - https://intodns.com/redampperu.com

- just to begin this domain doesnt resolve to any IP:

Host Name  : redampperu.com
IP Address : redampperu.com cannot be resolved to an IP Address
Location   : Unknown

Before email and whatever other problem you must start with Bind. Both domains reported some serious problems and its hard to pinpoint to any other problem if Bind is wrongly configured. Start from here and then go step by step to remove other problems but i'm sure just with Bind configured properly some of the problems will vanish.

Last but not least, domain mygepeese.com is blacklisted at spameatingmonkey.net. Not a major RBL still many are using them to check incoming emails. Either way you have open relay there, someone hacked your website or server or you are the one spamming. Not big chance because it would require a lot of emails still it could be because of wrongly configured Bind.

AqpJoe i think you have a lot of work in front of you if you want that server to function properly.

- I often come to the conclusion that my brain has too many tabs open. -
Failing at desktop publishing & graphic design since 1994.

Mon, 01/09/2017 - 17:57
AqpJoe

Hi, in the last hour was reconfiguring everything, so nothing works. XD .. changed to the dns, I will be commenting on the result of the reconfigurations.

Mon, 01/09/2017 - 19:16
Diabolico
Diabolico's picture

Fine but good part of your problems isnt Virtualmin related and a lot of info can be found on google, especially Bind, Apache and Postfix. It would be better if you sort everything and come back with Virtualmin (or Webmin) related problems. In case all this is too much for your you could pay Virtualmin devs to install Virtualmin and check if everything works properly.

- I often come to the conclusion that my brain has too many tabs open. -
Failing at desktop publishing & graphic design since 1994.

Wed, 01/11/2017 - 09:58
AqpJoe

Hello guys, I solved my problem by changing the domain of my server and I did configure the reverse dns with my ISP, I'm not sure if that was the problem but the mails are already working ..... Now I have a couple of doubts , I have two web applications in Python - Django, could you run them each for different domains? .. when I run an application the following happens:

Domainone: 8990

Domaintwo: 8990

.. both open the same application.

Thu, 01/12/2017 - 02:37 (Reply to #15)
unborn
unborn's picture

glad to hear that you resolved your problem.. as I said dns can give out lot of funny issues. Regards your apps, sure you can! run one app on port 8990 and second app on different port aka 8991 or something. then in apache create two subservers like app1.domain.com and app2.domain.com then edit apache proxy on those.. in proxy settings just point them to localhost:8990 and on another subserver to localhost:8991. Restart the apache (just to make sure new settings are loaded) and visit app1.domain.com . it should serve app1 right a way without :portnumber.

Configuring/troubleshooting Debian servers is always great fun