What we have is :
nothing listening on port 25, 465(?), 587.
master does not appear in the output of ps, if Postfix is running
I would assume we should see it
if you run "ps -A | grep master"
So what evidence is there that it was ever started, has it been added
to the init.
At th
On 2/2/2013 3:50 PM, Viktor Dukhovni wrote:
> On Sat, Feb 02, 2013 at 03:34:30PM -0600, Stan Hoeppner wrote:
>
>>check_client_access pcre:/etc/postfix/client_access
>>...
>>
>> /etc/postfix/client_access:
>> /.*facebook\.com$/ permit
>
> This is not robust for two reason
On Sat, Feb 02, 2013 at 03:34:30PM -0600, Stan Hoeppner wrote:
>check_client_access pcre:/etc/postfix/client_access
>...
>
> /etc/postfix/client_access:
> /.*facebook\.com$/permit
This is not robust for two reasons, the first is a simple oversight,
replace:
/
On 2/2/2013 1:55 PM, Gerben Wierda wrote:
> Just so there is no misunderstanding: I am unhappy running an older version
> that is not updated with security fixes anymore and I had planned to upgrade
> before now (but not immediately when 10.8 came out as 10.8.0 Server was not
> what you say trus
On 2/2/2013 11:10 AM, Gerben Wierda wrote:
> Dag & Dank Wietse,
>
> Can I do perl regex, e.g.
>
> outmail\d\d\d.snc\d.facebook.com permit
>
> or globbing like
>
> outmail*.snc4*.facebook.com
/etc/postfix/main.cf:
smtpd_recipient_restrictions =
...
reject_unauth_destina
Just so there is no misunderstanding: I am unhappy running an older version
that is not updated with security fixes anymore and I had planned to upgrade
before now (but not immediately when 10.8 came out as 10.8.0 Server was not
what you say trustworthy. I skipped 10.7 server altogether because
--> Gerben Wierda [2013-02-02 19:37:41 +0100]:
> Actually, I'm still on /usr/libexec/postfix/greylist.pl
> as I am using Mac OS X Server 10.6.8 and I haven't dared to upgrade
> to a higher version of OS X Server as they were busy crippling it
> in many respects.
It's actually very easy to upgra
On 02/02/2013 1:16 PM, Reindl Harald wrote:
Am 02.02.2013 18:45, schrieb John Allen:
How about a simple test to see if it running, ps -A | grep master
no, it isn't running:
There is not much point in looking anywhere for a solution for problems, until
you have Postfix running.
Try "
Am 02.02.2013 19:37, schrieb Gerben Wierda:
> Actually, I'm still on
>
> /usr/libexec/postfix/greylist.pl
>
> as I am using Mac OS X Server 10.6.8 and I haven't dared to upgrade to a
> higher version of OS X Server as they were busy crippling it in many respects.
you are aware that OSX 10.6
Actually, I'm still on
/usr/libexec/postfix/greylist.pl
as I am using Mac OS X Server 10.6.8 and I haven't dared to upgrade to a higher
version of OS X Server as they were busy crippling it in many respects.
G
On 2 Feb 2013, at 18:51, John Allen wrote:
> On 02/02/2013 11:25 AM, Gerben Wierd
Am 02.02.2013 18:45, schrieb John Allen:
>>> How about a simple test to see if it running, ps -A | grep master
>>no, it isn't running:
>
> There is not much point in looking anywhere for a solution for problems,
> until you have Postfix running.
> Try "service postfix start" what
On 02/02/2013 11:25 AM, Gerben Wierda wrote:
So, I need a whitelist. But how?
If you are using postgrey then you can add something to the white list
which can be found in/etc/postgrey (debian).
Might help
John A
>> How about a simple test to see if it running, ps -A | grep master
>no, it isn't running:
There is not much point in looking anywhere for a solution for problems,
until you have Postfix running.
Try "service postfix start" what happens?
John A
Dag & Dank Wietse,
Can I do perl regex, e.g.
outmail\d\d\d.snc\d.facebook.compermit
or globbing like
outmail*.snc4*.facebook.com
And secondly, I also get mail I want to leave through where the sender is an
operation like messagelabs, but I want to accept only certain senders using
me
On 2/2/2013 at 9:52 AM Sahil Tandon wrote:
|On Wed, 2013-01-30 at 14:23:19 -0500, Mike. wrote:
|
|> I made some changes to the script based upon the excellent feedback
I
|> received here.
|>
|> The script no longer wanders beyond the postscreen log records in
|> order to gather the information
Gerben Wierda:
> smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks
> reject_unauth_destination check_policy_service unix:private/policy permit
>
To exclude some site from greylist checks, use an access table
*after* reject_unauth_destination and before the check_policy_
I have set up my smtpd restrictions as follows:
smtpd_client_restrictions = permit_mynetworks permit_sasl_authenticated
check_sender_access hash:/etc/postfix/whitelist reject_rbl_client
zen.spamhaus.org permit
smtpd_recipient_restrictions = permit_sasl_authenticated permit_mynetworks
reject_un
# postfix -v start
postfix: name_mask: ipv4
postfix: inet_addr_local: configured 5 IPv4 addresses
# ps -e | grep master
#
Is this pipe character really there? It should not be.
no, it's artefact from mail, there is no such pipe characted in config
You do NOT want verbose logs. Remove the -v
On Wed, 2013-01-30 at 14:23:19 -0500, Mike. wrote:
> I made some changes to the script based upon the excellent feedback I
> received here.
>
> The script no longer wanders beyond the postscreen log records in
> order to gather the information needed to determine the postscreen
> rejection rate
||
What I should check in the first place?
I don't see any sign that postfix is running.
How about a simple test to see if it running, most distro have the
"service" command so start with
service postfix status
this should tell you if postfix is running or not. if your distro does
not have
* arsen.shnurkov [2013-02-02 08:00:28 +0400]:
> When I try to start, it writes "ok":
>
> | # /etc/init.d/postfix start
> * Starting postfix ...
> [
> ok ]
> |
>
>
21 matches
Mail list logo
