Displaying 20 results from an estimated 10000 matches similar to: "Feature wishlist: Allow to hide client IP/host in submission service"
2019 Aug 27
0
Feature wishlist: Allow to hide client IP/host in submission service
On 2019-08-25 20:51, Sebastian Krause via dovecot wrote:
> Hi,
>
> In many mail setups a required feature (for privacy reasons) is to
> hide the host and IP of clients (in the "Received" header) that use
> the authenticated submission over port 587. In Postfix that's
> possible (https://serverfault.com/q/413533/86332), but not very nice
> to configure especially
2019 Aug 28
0
Feature wishlist: Allow to hide client IP/host in submission service
On 25 Aug 2019, at 21.51, Sebastian Krause via dovecot <dovecot at dovecot.org> wrote:
>
> Hi,
>
> In many mail setups a required feature (for privacy reasons) is to
> hide the host and IP of clients (in the "Received" header) that use
> the authenticated submission over port 587. In Postfix that's
> possible (https://serverfault.com/q/413533/86332), but
2018 Oct 19
2
Request: option to hide user IP/HELO content from mail sent via submissiond
For reasons of user privacy and security I usually configure submission servers to not include accurate IP address and HELO information of authenticated users. (Usually replacing it with a private-use domain / IPv6 address.)
Dovecot submission (2.3.2) will produce a header something like this (where ?10.22.36.10" is a public IP address)
Received: from [192.168.1.184] ([10.22.36.10])
by
2019 Jul 27
2
submission configuration issues
> Le 27 juil. 2019 ? 14:30, Stephan Bosch <stephan at rename-it.nl> a ?crit :
>
> On 23/07/2019 17:13, Jean-Daniel Dupas via dovecot wrote:
>> Hello,
>>
>> I'm having trouble configuring the submission proxy.
>>
>> I have configured the submission service as follow:
>>
>> submission_host = smtp.example.com
>>
2020 Aug 31
3
Dovecot Proxy
Hello everyone,
it's my first post here on this mailing list and I hope, I make it right.
I posted a question on
https://serverfault.com/questions/1031441/dovecot-as-proxy-with-submission
and nobody was able to answer it. So I decided to push that question
here (I'm talking about any new dovecot version and I've tested it with
2.3.4.1 (f79e8e7e4)).
I try to run a dovecot proxy
2020 Sep 01
1
Dovecot Proxy
Hi Philon,
now, it's time for "Mahlzeit" ;-)
Sorry, that I read the wiki1 instead of wiki2. I thought the 1 means
that it is server one of ... my fault. Also not reading the first line
above the menu. My focus was really on the content. ;-)
Also my problem with the doc of Dovecot2 proxy is, that the document
https://doc.dovecot.org/configuration_manual/authentication/proxies/
2019 Jul 23
5
submission configuration issues
Hello,
I'm having trouble configuring the submission proxy.
I have configured the submission service as follow:
submission_host = smtp.example.com
submission_relay_host = localhost
submission_relay_port = 8587
submission_relay_rawlog_dir = /var/log/dovecot/
submission_relay_trusted = yes
My main issue is that until I login, dovecot-submission won't connect to the backend and query the
2018 Jan 03
2
sieve/internal error/detail subaddress and IMAP4FLAGS.
I'm trying to set an IMAP Flag with the detail part of an address, but getting
an internal error:
an 3 13:37:27 thebighonker exim[537]: 1eWoqt-00008f-4u <= ler at lerctr.org H=(lrosenman.local) [74.203.163.58]:4650 I=[192.147.25.65]:587 P=esmtpsa X=TLSv1.2:ECDHE-RSA-AES256-GCM-SHA3
84:256 CV=no SNI="smtp.lerctr.org" A=dovecot_login:ler S=769 id=20180103193716.oofszdaxopnkgfvd at
2014 Jan 16
1
Received: header showing 127.0.0.1 after switch to dovecot LDA?
Hi all,
I'm guessing this is correct behavior, but wanted to make sure...
I noticed that for locally delivered messages (between 2 local users
inside our domain, so they never leave the server), the first Received:
header line content changed after I switched to the dovecot LDA.
Before, using postfix/virtual for delivery, the header looked like this:
Received:
from [192.168.1.25]
2019 Apr 30
1
regression with lmtp_hdr_delivery_address in 2.3
Hi,
In my LMTP config, I have
lmtp_hdr_delivery_address = none.
Under 2.2, Received headers looked like this:
Received: from smtp.example.com
by lmtp.example.com with LMTP id +IVdKS81cFwWagAAGhmRSA
; Fri, 22 Feb 2019 17:45:19 +0000
After the update to 2.3, they look like this:
Received: from smtp.example.com
by lmtp.example.com with LMTP
id MJbKAMFEclyKCQAAGhmRSA
2015 Jun 18
3
What does the socks function of openssh hide?
Salutations,
I was recently using openssh 6.8p1-3 for socks tunelling with a public wifi
hotspot. I attempted to watch youtube but was notified that it was not allowed
in my area. The socks server I was connected to definitely had the ability to
connect to youtube, so I concluded the issue was with the public wifi hotspot.
How much does socks tunneling with openssh obscure?
Command : ssh -ND
2019 Jun 09
1
RFC 8314 § 3.3 support at Dovecot submission proxy service?
Hello all,
I'm currently wondering whether Dovecot submission proxy service supports
RFC 8314 ? 3.3 as well, which means implicit TLS for SMTP submission.
https://github.com/dovecot/core/blob/2cbbe9b4829adb184c83dbf780316f4144559054/doc/example-config/conf.d/10-master.conf#L48
from Git master just mentions port 587 like this:
service submission-login {
inet_listener submission {
#port
2007 Jan 11
2
Wishlist: Sweave: allow line breaks after forward slashes (PR#9443)
Full_Name: Arne Henningsen
Version: 2.4.0
OS: Linux
Submission from: (NULL) (134.245.140.242)
Sweave does not allow line breaks after forward slashes ("/"). This might lead
to a long "substring" of a command that cannot be wrapped. Hence, Sweave either
keeps this long "substring" in the current line and produces a too long line or
it moves the entire
2004 Sep 13
1
Wishlist: axis() and line widths (PR#7223)
Full_Name: Tom Short
Version: 1.9.1
OS: Win2000 & Debian
Submission from: (NULL) (64.65.255.41)
WISHLIST:
axis() has a default parameter of "lwd = 1". I want skinnier lines as the
default. If I change the default lty, it doesn't change what axis uses.
The following code produces a graph with a box around it, but the axis lines are
twice as thick as the box around the plot, so
2003 Oct 29
1
Wishlist: user-specified color names for palette() (PR#4836)
Full_Name: Hsiu-Khuern Tang
Version: 1.8.0
OS: GNU/Linux (Debian unstable)
Submission from: (NULL) (156.153.255.243)
Hi,
I use palette(rgb(red=..., green=..., blue=..., names=mycolors)) to define my
own color palette. After doing this, the names `mycolors' are not stored in
palette() anymore, so that palette() returns a mix of built-in color names and
RGB values.
Eg:
> palette()
2008 Nov 21
1
Wishlist: fix error in documentation for body<- (PR#13318)
Full_Name: Fabian Scheipl
Version: 2.8.0
OS: Windows, Linux
Submission from: (NULL) (138.246.7.150)
It seems to me that the documentation for body<- is wrong.
The help file for
body(fun, envir = environment(fun)) <- value
says that:
value can be an expression or a list of R expressions.
This produces errors however:
################################
> f <- function(x){}
>
2007 Dec 04
2
Wishlist: mention Vectorize in 'outer' man page (PR#10490)
Full_Name: Antonio, Fabio Di Narzo
Version: 2.6.1
OS: linux
Submission from: (NULL) (213.140.16.187)
In 'outer' man page, there is no mention of the Vectorize function.
Moreover, I think it isn't underlined enough that the FUN argument to 'outer'
must be a vectorized function (doc speaks about a function which has to 'operate
elementwise').
A cross-reference from
2006 Nov 13
1
wishlist: xlim in lines.polynomial (PR#9362)
Full_Name: Tamas K Papp
Version: 2.4.0
OS: linux
Submission from: (NULL) (140.180.166.160)
I was using the lines.polynomial method for plotting piecewise polynomials
(parts of splines). I needed a feature to limit the range of plotting using a
parameter given to the function (as opposed to par("usr")). I think that the
following changes would be a nice addition:
lines.polynomial
2007 Mar 20
1
wishlist -- Fix for major format.pval limitation (PR#9574)
Full_Name: Charles Dupont
Version: 2.4.1
OS: linux 2.6.18
Submission from: (NULL) (160.129.129.136)
'format.pval' has a major limitation in its implementation. For example
suppose a person had a vector like 'a' and the error being ?0.001.
> a <- c(0.1, 0.3, 0.4, 0.5, 0.3, 0.0001)
> format.pval(a, eps=0.01)
If that person wants to have the 'format.pval'
2004 Dec 02
3
Wishlist: simple legend options (PR#7400)
Full_Name: Elizabeth Purdom
Version: 1.9.1
OS: Windows XP
Submission from: (NULL) (171.64.102.199)
It would be nice if legend had the option of some default locations you could
choose instead of entering specific coordinates, like "topleft",
"topright","topcenter", etc. based on par("usr") coordinates. I know I've wanted
it so often I've made my