Hi friends,
Following the Workaround tutorial for Jessie
(https://workaround.org/ispmail/jessie ) I've set up six month ago my
first Postfix email server and all works very fine, except for the
ability from the user to encrypt login password.
I can use the encrypted password with smtp, but not
On Thu, Feb 09, 2017 at 06:16:36PM +0800, P.V.Anthony wrote:
> Just got an scam email that looks like from paypal.
>
> It passed dkim and spf.
>
> dkim=pass (1024-bit key) header.d=service2.sdmone.email
> header.i=sdmone@service2.sdmone.email header.b="adXLiw9w";
> dkim=pass (1024-bit key
> On Feb 10, 2017, at 8:04 PM, Patrik wrote:
>
> Do you know how I can change the service users?
No idea what you mean when you say that. You have not described
any problem that requires changes related to "users".
> or is it a linux info?
No idea.
> I thought by default it is secure, i gue
do you know how i can change the service users?
or is it a linux info?
i thought by default it is secure, i guess i have to change by hand right?
*Patrik*
*GTalk: *alab...@gmail.com
*Web:*
http://www.patrikx3.tk
*Mobile:*
+36 20 342 8046 <+36+20+342+8046>
On Sat, Feb 11, 2017 at 1:55 AM, V
On Sat, Feb 11, 2017 at 01:43:43AM +0100, Patrik wrote:
> what does this mean?
> proxymapunix
> proxywrite unix
> local unix
> virtual unix
These identify entries in master.cf by name and type:
http://www.postfix.org/master.5.html
They should not be chrooted even when some or
yes those 2 service as you told me.
i dont want to use chroot at all. usually other user.
what does this mean?
proxymapunix
proxywrite unix
local unix
virtual unix
my service for dovecot and postfix:
root@server:~# ps -aux | grep postfix
root 5829 0.0 0.1 75704 4164 ?
On Sat, Feb 11, 2017 at 01:26:15AM +0100, Patrik wrote:
> That's all?
Do read what I wrote. You'll need both services.
> smtp unix - - n - - smtp
> lmtp unix - - n - - lmtp
You should probably be consistent about whether y
that's all??
you saved me my stress!! you are the king!!! I had to moved from lmtp smtp
to lmtp!!!
lmtp unix - - y - - smtp
to
lmtp unix - - n - - lmtp
that's all!!!
for sure?? nothing else???
*Patrik*
*GTalk: *ala
On Sat, Feb 11, 2017 at 01:13:35AM +0100, Patrik Laszlo wrote:
> root@server:~/email# postcat -eq 87EF33004CC | grep content_filter
> root@server:~/email# postcat -eq 19F213004D8 | grep content_filter
> root@server:~/email# postcat -eq 671FF3004D7 | grep content_filter
Good, no problem content_fi
*nothing!*
*also to send from to gmail works, from gmail to my email not working.*
root@server:~/email# postcat -eq 87EF33004CC | grep content_filter
root@server:~/email# postcat -eq 19F213004D8 | grep content_filter
root@server:~/email# postcat -eq 671FF3004D7 | grep content_filter
*all empty
like this?
On 02/11/2017 01:06 AM, Viktor Dukhovni wrote:
On Sat, Feb 11, 2017 at 01:00:51AM +0100, Patrik Laszlo wrote:
But where? I don't know Postfix, sorry.
http://www.postfix.org/DEBUG_README.html#mail
Post the output of:
$ postconf -n
$ postconf -Mf
Find a messa
attach or inline?
On 02/11/2017 01:06 AM, Viktor Dukhovni wrote:
postconf -n
On Sat, Feb 11, 2017 at 01:00:51AM +0100, Patrik Laszlo wrote:
> But where? I don't know Postfix, sorry.
http://www.postfix.org/DEBUG_README.html#mail
Post the output of:
$ postconf -n
$ postconf -Mf
Find a message in the queue that is deferred due to this
problem. As root
*which should i change?
*
*i get this:*
smtpd_banner = ESMTP mail.patrikx3.tk
biff = no
append_dot_mydomain = no
readme_directory = no
compatibility_level = 2
smtpd_tls_cert_file= /etc/ssl/acme/mail.patrikx3.tk/fullchain.cer
smtpd_tls_key_file=/etc/ssl/acme/mail.patrikx3.tk/mail.patrikx3.tk.key
but where? i dont no postfix, sorry.
where? please help me, i have been trying for a week.
which setting? master.cf but which?
On 02/11/2017 12:58 AM, Viktor Dukhovni wrote:
On Sat, Feb 11, 2017 at 12:51:10AM +0100, Patrik wrote:
this?
smtp inet n - y - -
On Sat, Feb 11, 2017 at 12:51:10AM +0100, Patrik wrote:
> this?
> smtp inet n - y - - smtpd
> to
> smtp unix n - y - - smtpd
No, it would have been the one that says "dovecot-lmtp", but you
don't have one at all apparently.
this?
smtp inet n - y - - smtpd
to
smtp unix n - y - - smtpd
or which?
#
# Postfix master process configuration file. For details on the format
# of the file, see the master(5) manual page (command: "man 5 master" or
# on-li
On Sat, Feb 11, 2017 at 12:28:13AM +0100, Patrik wrote:
>
> could you help how to work it with dovecot? i can use any other solution as
> well. if you have a quick fix or is it in the docs somewhere?
>
> i get no error except this:
>
> Feb 9 23:34:33 server postfix/smtp[2606]: fatal: unknown s
hello!
could you help how to work it with dovecot? i can use any other solution as
well. if you have a quick fix or is it in the docs somewhere?
i get no error except this:
Feb 9 23:34:33 server postfix/smtp[2606]: fatal: unknown service:
private/dovecot-lmtp/tcp
Feb 9 23:34:34 server postfix/
On Feb 9, 2017, at 11:35 AM, Noel Jones wrote:
> I think you'll have to nest more if..endif statements
Oh. right. Of course. Brain Cloud is strong today.
--
Apple broke AppleScripting signatures in Mail.app, so no random signatures.
I am using ldap:
I will try using it as proxy:ldap: instead as well as your script suggestion
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Viktor Dukhovni
Sent: Friday, February 10, 2017 2:43 PM
To: Postfix users
Subject:
> On Feb 10, 2017, at 2:27 PM, Gomes, Rich wrote:
>
> The reason the query is setup like that is we have several internal
> domains and a user may have an alias for one or all of them depending
> on their employment history.
You've failed to understand my response. The "proxyAddresses" attribu
On Sun, Feb 5, 2017 at 7:58 PM, Viktor Dukhovni
wrote:
>
> > On Feb 5, 2017, at 6:49 PM, Jaime Hablutzel Egoavil <
> hablutz...@gmail.com> wrote:
> >
> > Here is one valid use case, the mail service operator
> > doesn't manage or participate in the certificate issuance
> > itself but he expects t
The reason the query is setup like that is we have several internal domains and
a user may have an alias for one or all of them depending on their employment
history.
Since it is working as expected, I'd rather leave it as is, unless you feel it
may be a contributor to the issue I am seeing.
> On Feb 10, 2017, at 1:15 PM, Gomes, Rich wrote:
>
> domain = first.com, second.com, third.com, fourth.com, fifth.com, sixth.com
> server_host = pool.internal.domain.com
> search_base = dc=internal, dc=domain, dc=com
> version = 3
>
> # Filter
> query_filter = (&(objectclass=person)(proxyAddre
Confident because I was part of their setup. ; )
* Use queries that are implemented efficiently on the AD side.
Done
* Use LDAP servers that are not already struggling with processing
other queries.
This is a load balanced pool of (hardware load balanced, not round
On Fri, Feb 10, 2017 at 05:37:36PM +, Gomes, Rich wrote:
> It's going against MS AD, I am sure indexing is configured correctly there.
That rather depends on what query you're sending, and how AD is
configured. Your confidence does not inspire confidence. :-(
> What can I do on my postfix s
It's going against MS AD, I am sure indexing is configured correctly there.
What can I do on my postfix server to alleviate this issue?
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Viktor Dukhovni
Sent: Friday, February
On Fri, Feb 10, 2017 at 05:21:18PM +, Gomes, Rich wrote:
> Can you point me in the right direction for indexing?
> All I can find is adding this line to the config:
> result_attribute = memberaddr (this was in an expanding groups thread)
LDAP data indexing is something that happens in the LD
Ok, thank you.
Can you point me in the right direction for indexing?
All I can find is adding this line to the config:
result_attribute = memberaddr (this was in an expanding groups thread)
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.o
> On Feb 10, 2017, at 12:01 PM, Gomes, Rich wrote:
>
> warning: dict_ldap_lookup: Search error -5: Timed out
You've probably neglected to index the appropriate attributes.
Fix the indexing, and the timeouts will likely go away.
> Is this simply a matter of increasing the timeout?
No your LDAP
I've started to see a lot of these errors, albeit intermittently:
warning: dict_ldap_lookup: Search error -5: Timed out
Followed by these:
NOQUEUE: reject: RCPT from unknown[x.x.x.x]: 451 4.3.0
: Temporary lookup failure
This server is functioning as an internal relay (no local users) and is
32 matches
Mail list logo
