Erroneously I tried to use the option 'delete' instead of 'destroy' when I ran
the postmulti-command. My fault, but then the output - among many other
options - stated, I should use 'delete' instead of 'delete':
# postmulti -i postfix-test -e delete
postmulti: fatal: Invalid '-e' edit action 'dele
I am using Postfix as personal mailserver, with very light traffic.
I do, however, get a lot of open-relay attacks.
Often, these attacks come in bursts, tens of attacks within couple of
seconds, from the same IP.
Would this situation be a good use of "rate_limits" ?
Any suggestion how I should f
Hello,
smtpd_tls_security_level = encrypt
smtp_tls_security_level = encrypt
I configured postfix to use encryption for incoming and outgoing emails.
but incase the receipt has untrusted certificate or self signed
certificate, postfix still deliver the email.
How to enforce postfix not to send
Hi everybody,
First of all, sorry for my bad english.
Since yesterday, I have an issue with my dedicated server provider.
They consider my bounce emails as spam.
They said that my bounces have an empty "from" so they are considered as
spam by their "anti-spam" system.
They ask me to define
Baptiste Lhoste:
> Hi everybody,
>
> First of all, sorry for my bad english.
>
> Since yesterday, I have an issue with my dedicated server provider.
>
> They consider my bounce emails as spam.
>
> They said that my bounces have an empty "from" so they are considered as
> spam by their "anti-sp
Thanks for the response.
Since I can not specify the MAIL FROM address for bounce emails, how can
I log theirs headers and content to give them to my dedicated server
provider ?
Baptiste
On 24/09/2015 12:25, Wietse Venema wrote:
Baptiste Lhoste:
Hi everybody,
First of all, sorry for my ba
Hi,
Please try this.
Wietse
[patch]
Works like a charm! I couldn't just patch our live server of course but I
grabbed the ubuntu 14.04 postfix 2.11.0 source package on a VM, and the
haproxy1.5 from trusty-backports and it works.
Thanks for the prompt support! Will you be merging t
Zitat von Michael Peter :
Hello,
smtpd_tls_security_level = encrypt
smtp_tls_security_level = encrypt
I configured postfix to use encryption for incoming and outgoing emails.
but incase the receipt has untrusted certificate or self signed
certificate, postfix still deliver the email.
How t
Hi All,
I just installed, configured and have working OpenDKIM. I can see
outgoing email is being properly signed, but not certain what it's doing
for me on the receiving side of things?
All the searching and reading I've done talks all about how to get it
going, and how to test your outgoing em
Lukas Erlacher:
> Hi,
>
> > Please try this.
> >
> > Wietse
> >
> > [patch]
>
> Works like a charm! I couldn't just patch our live server of course
> but I grabbed the ubuntu 14.04 postfix 2.11.0 source package on a
> VM, and the haproxy1.5 from trusty-backports and it works.
>
> Thanks for t
Tell them that the SMTP protocol requires support for the MAIL FROM null sender.
https://tools.ietf.org/html/rfc5321#section-4.5.5
Wietse
Baptiste Lhoste:
> Thanks for the response.
>
> Since I can not specify the MAIL FROM address for bounce emails, how can
> I log theirs headers and co
Jim Seymour:
> Hi All,
>
> I just installed, configured and have working OpenDKIM. I can see
> outgoing email is being properly signed, but not certain what it's doing
> for me on the receiving side of things?
>
> All the searching and reading I've done talks all about how to get it
> going, and
Hi
I have a server NIS that has a wrong domain name, therefore, everytime that
I am receiving an email the user is changed as user@NISDOMAIN despite the
fact that my postfix is configured with a mydomain variable.
I tried to modify the domain with
recipient_canonical_maps or smtp_generic_maps or he
Thanks for the prompt support! Will you be merging this?
In the next 3.1 development release, and in a month or so, in the next
stable releases (2.9 .. 3.0).
Wietse
That's great to hear!
Best,
Luke
smime.p7s
Description: S/MIME Cryptographic Signature
On Thu, Sep 24, 2015 at 09:12:00AM -0400, Il Neofita wrote:
> I have a server NIS that has a wrong domain name, therefore, everytime that
> I am receiving an email the user is changed as user@NISDOMAIN despite the
> fact that my postfix is configured with a mydomain variable.
The "mydomain" param
Il Neofita:
> Hi
> I have a server NIS that has a wrong domain name, therefore, everytime that
> I am receiving an email the user is changed as user@NISDOMAIN despite the
> fact that my postfix is configured with a mydomain variable.
> I tried to modify the domain with
> recipient_canonical_maps or
Wietse Venema:
> Il Neofita:
> > Hi
> > I have a server NIS that has a wrong domain name, therefore, everytime that
> > I am receiving an email the user is changed as user@NISDOMAIN despite the
> > fact that my postfix is configured with a mydomain variable.
> > I tried to modify the domain with
>
On Thu, 24 Sep 2015 08:48:24 -0400 (EDT)
wie...@porcupine.org (Wietse Venema) wrote:
> Jim Seymour:
> > Hi All,
> >
> > I just installed, configured and have working OpenDKIM. I can see
> > outgoing email is being properly signed, but not certain what it's
> > doing for me on the receiving side
On Thu, Sep 24, 2015 at 02:14:47PM +0200, lst_ho...@kwsoft.de wrote:
> >How to enforce postfix not to send the email incase the receipt
> >certificate is untrusted or self signed?
>
> You will need "verify" level for this :
> http://www.postfix.org/TLS_README.html#client_tls_verify
The default h
On Thu, Sep 24, 2015 at 08:52:45AM +0200, Patrick Ben Koetter wrote:
> Yesterday I ran into a situation where I tried to create a new postfix
> instance, but the *.proto files where missing (i.e. they were there, but in
> the wrong place):
Distribution packaging problem? With Postfix 3.0 and lat
On Thu, Sep 24, 2015 at 09:00:43AM +0200, Patrick Ben Koetter wrote:
> Erroneously I tried to use the option 'delete' instead of 'destroy' when I ran
> the postmulti-command. My fault, but then the output - among many other
> options - stated, I should use 'delete' instead of 'delete':
>
> # post
* Viktor Dukhovni :
> On Thu, Sep 24, 2015 at 08:52:45AM +0200, Patrick Ben Koetter wrote:
>
> > Yesterday I ran into a situation where I tried to create a new postfix
> > instance, but the *.proto files where missing (i.e. they were there, but in
> > the wrong place):
>
> Distribution packaging
On Thu, Sep 24, 2015 at 05:05:34PM +0200, Patrick Ben Koetter wrote:
> > That can happen. We could test more pre-conditions, but ultimately,
> > the administrator may need to recover from situations where automated
> > deletion is risky.
>
> Agreed. I wouldn't reach out to test any thinkable sit
The problem is with the forward using the aliases, therefore, should be
postfix
If I change the domainname I will have problem with the nis
the nisdomain is using capital letter, and mydomain is using lower letter
therefore, the to is changed during the forward with capital letter
On Thu, Sep 2
On Thu, Sep 24, 2015 at 12:03:16PM -0400, Il Neofita wrote:
> The problem is with the forward using the aliases, therefore, should be
> postfix
>
> If I change the domainname I will have problem with the nis
>
> the nisdomain is using capital letter, and mydomain is using lower letter
> therefor
On 9/24/2015 3:28 AM, Thomas Keller wrote:
> I am using Postfix as personal mailserver, with very light traffic.
>
> I do, however, get a lot of open-relay attacks.
> Often, these attacks come in bursts, tens of attacks within couple of
> seconds, from the same IP.
>
> Would this situation be a g
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
command_directory = /usr/sbin
daemon_directory = /usr/libexec/postfix
data_directory = /var/lib/postfix
debug_peer_level = 2
debugger_command = PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin ddd
$daemon_directory/$process_name $pro
On Thu, Sep 24, 2015 at 12:54:37PM -0400, Il Neofita wrote:
> alias_maps = hash:/etc/aliases
> forward_path = /etc/postfix/destination
> mailbox_command = /usr/libexec/dovecot/deliver
> mydomain = aaa.aaa
> myorigin = $mydomain
> relayhost = aaa.a.aa
The above are potentially rele
Thank you for the reply, I tried without the relayhost, also check in the
alias,and mydomain is wrote correctly and I remove forward_path since the
file was empty
I have also tried to put the forward in the alias
therefore,
pluto: a...@gmail.com
however, in the header the from on the message recei
On Thu, Sep 24, 2015 at 01:40:21PM -0400, Il Neofita wrote:
> In the header the from on the message received by gmail is in
> capital letters and dovecot is not involved in that transfer.
> I tought that mydomain was suppose to overwrite the unix domainname
It appears you're unable to explain th
When the server receive an email, the TO field is changed using the domain
from the system and not the domain configured in postfix.
Therefore, if the server receive an email with the field u...@a.aa is
changed in u...@a.aa, which A.AA is the nis domain.
On Thu, Sep 24, 2015 at 1:55
On Thu, Sep 24, 2015 at 05:15:03PM -0400, Il Neofita wrote:
> When the server receive an email, the TO field is changed using the domain
> from the system and not the domain configured in postfix.
> Therefore, if the server receive an email with the field u...@a.aa is
> changed in u...@a.a
Hello,
I have configured postfix to check CAfile which contains only Godaddy root
certificate as follow
smtp_tls_CAfile = /etc/certs/go-daddy-root-ca.crt
my surpirse that still postfix trust the server certificates when email is
sent to Yahoo or Gmail.. although the CAfile contains only the goda
33 matches
Mail list logo
