How to set up sending by webmail.domain.com via smtp, not locally localhost ([127.0.0.1]

Community Support Mail
1

Hello!
Could you help to setup:

  1. if i use webmail.domain.com via roundcube, letter goes to spam folder in global mail providers, and i see in body
    Received: from localhost ([127.0.0.1] helo=…)

  2. I use mail client and everything is ok, in body i see
    Received: from [NORMAL IP] (helo=[10.8.1.3])

  3. How to configure roundcube web interface for using smtp or not local sending as script

Thanks for advises!

2

Both header lines that you are referecing do not matter. Those are the connection between the MUA, or email client and the MTA, or mail server. In one example the MUA is Roundcube and the other is Thunderbird or another program running on your local device. Neither of those received headers’ contents should be evaluated by the receiving MTA for a variety of reasons.

I don’t use HestiaCP for email, and don’t use exim, either, but in my Postfix configuration I strip the MUA received headers for privacy reasons before relaying outbound SMTP. You may be able to do the same in exim if you don’t want those headers included in your sent messages. Unfortunately I can’t walk you through the process since I don’t know exim well enough.

1 Like
3

Good point mate. I actually was trying to figure it myself how to stop relaying my IP & have more privacy. Since I use HCP for emails as well.
@sahsanu any help on how not to leak IP & any personal identifying details over EXIM. I found we need to add this REMOTE_SMTP_TRANSPORTS_HEADERS_REMOVE = Received to /etc/exim4/exim4.conf.localmacros, but there is no localmacros or any such file. Also, in the file, where would one add the same?

4

Thaks for advise!
But main global problem are:

  1. Send letters via webmail.
    gmail
    hotmail and many others pass letter to spam
  2. If i send same letter from post client via smtp, all ok
  3. Globally webmail roundcube is useless due to this issue((
5

I use this directive on remote_smtp transport:

  headers_remove = Received : X-Originating-IP

@saleseo try it, modify /etc/exim4/exim4.conf.template and add above directive at the end of remote_smtp transport, restart exim4 and try again.

2 Likes
6

Thanks. I followed your advice, but I think it still sends the received header:
Received: from panel.domain (panel.domain [SERVER IP HERE])

Also, what else can we hide?

:frowning:

Edit: Or when it says originating, is it the server IP we are hiding or my local machine IP? Sorry, I am just confused here, so asking this.

7

Yes, that Received header is correct and must be in the headers (those are added by the mail server receiving the mail, not by Exim). The header you removed is the Received header of your user connecting to your mail server (using their own mail client or using the webmail).

Do you think you must hide anything else? :wink:

2 Likes
8

Yes, I just edited my comments above with local isp ip vs server ip. I think, server ip is sent normally, but my local ip is hidden. Nice.

I am not sure what else should be hidden. I am traversing this locality with this forum and trying to understand.

I guess any ports or maybe user agent should be hidden as well?

I will search www as well 2mrw. :slight_smile:

Edit: One separate query (do not wish to create a post unnecessarily for that).

List of errors
--------------

    4 [email protected]: retry timeout exceeded

Errors encountered: 4
---------------------

This shows and has been showing regularly. Not sure what it means tbvh and how to solve it as well.

9

If you want to hide/remove User-Agent, just add it to headers_remove directive:

  headers_remove = Received : X-Originating-IP : User-Agent

Those are system messages sent to the root user. What I recommend and what I personally do, is create a mail domain, panel.domain, and add a user postmaster with the aliases hostmaster, admin, abuse, and root, so all those emails will reach the inbox [email protected]. You can also forward these emails to another email address you use frequently.

2 Likes
10

Wow, works well))) thanks!

3 Likes
11

Thanks. I tried. But it keeps saying mail domain does not exist when I try to create via webui.
Will see if I can get my laptop to work today and try via terminal.
Thanks again. :upside_down_face:

12

But panel.domain must exist, also the dns records for mail.panel.domain and webmail.panel.domain, the mx record for panel.domain pointing to mail.panel.domain… just like any other mail domain.

2 Likes