Am 09.02.2011 02:50, schrieb Sahil Tandon:
> On Tue, 2011-02-08 at 22:04:38 +0100, Robert Schetterer wrote:
>
>> Hi, geotrust
>> has changed ssl procedures
>> for this in i.e apache
>> i have to add intermediate in a extra
>> SSLCACertificateFile
>
> [ .. ]
>
>> i am not quite sure if or how i s
Am 09.02.2011 09:03, schrieb Robert Schetterer:
> Am 09.02.2011 02:50, schrieb Sahil Tandon:
>> On Tue, 2011-02-08 at 22:04:38 +0100, Robert Schetterer wrote:
>>
>>> Hi, geotrust
>>> has changed ssl procedures
>>> for this in i.e apache
>>> i have to add intermediate in a extra
>>> SSLCACertificate
I kept the same files, but updated all the binariesthe clause works if the
mail needs to send the mail elsewhere So instead of using relahost it uses
the relay defined in the sender_relay file
When the mail is destined to the main relay then it does normal routine of
looking in transpo
meyer-jor...@t-online.de:
> > I'm afraid Wolfgang's method is the only one, then - you'd have to
> > correlate all recipients by incoming queue-id.
> > A perl array could probably do this moderately efficiently, but I know
> > of no ready-made tools that do this - especially since, as you said, t
On Wed, 9 Feb 2011 08:26:35 -0500 (EST)
Wietse Venema articulated:
> meyer-jor...@t-online.de:
> > > I'm afraid Wolfgang's method is the only one, then - you'd have
> > > to correlate all recipients by incoming queue-id.
> > > A perl array could probably do this moderately efficiently, but I
> >
Is it possible to disable header checks based on the IP of the client
connecting to the postfix server?
A search on Google produces this link
http://www.seaglass.com/postfix/turning-off-body-checks.html which is
helpful but the idea for me is to disable header checking from trusted
outside sources
This is not supported (and will not be supported). You will need
to use an external content filter.
Wietse
On 2/9/2011 9:12 AM, Mike A. Leonetti wrote:
> Is it possible to disable header checks based on the IP of the client
> connecting to the postfix server?
>
> A search on Google produces this link
> http://www.seaglass.com/postfix/turning-off-body-checks.html which is
> helpful but the idea for me i
Hi , i have relay which smtp transports
to an internal mail server ( work wonderfull )
now i want to use always_bcc
to a local user
seems not work any idea how to solve this?
--
Best Regards
MfG Robert Schetterer
Germany/Munich/Bavaria
(2011年02月09日 10:23), Wietse Venema wrote:
> This is not supported (and will not be supported). You will need
> to use an external content filter.
>
> Wietse
Believe it or not we're going to an external content filter and that's
why the change. I guess the next step would be asking if it's pos
Robert Schetterer:
> Hi , i have relay which smtp transports
> to an internal mail server ( work wonderfull )
> now i want to use always_bcc
> to a local user
> seems not work any idea how to solve this?
You need to specify:
/etc/postfix/main.cf:
always_bcc = user@localhost
Instead of localh
On 2/9/2011 9:29 AM, Mike A. Leonetti wrote:
(2011年02月09日 10:23), Wietse Venema wrote:
This is not supported (and will not be supported). You will need
to use an external content filter.
Wietse
Believe it or not we're going to an external content filter and that's
why the change. I gue
Am 09.02.2011 16:56, schrieb Wietse Venema:
> Robert Schetterer:
>> Hi , i have relay which smtp transports
>> to an internal mail server ( work wonderfull )
>> now i want to use always_bcc
>> to a local user
>> seems not work any idea how to solve this?
>
> You need to specify:
>
> /etc/postfix/
Dear
For some reasons :
- mistakes
- bug inside a sender robot
- emailing application that going to be crazy,
- Internal infected network with an SMTP worm,
...
i would like send a "freeze" command to postfix that stopping the
routing process for a period or wat other command to release/contin
Robert Schetterer:
> Am 09.02.2011 16:56, schrieb Wietse Venema:
> > Robert Schetterer:
> >> Hi , i have relay which smtp transports
> >> to an internal mail server ( work wonderfull )
> >> now i want to use always_bcc
> >> to a local user
> >> seems not work any idea how to solve this?
> >
> > Yo
Am 09.02.2011 17:09, schrieb Robert Schetterer:
> Am 09.02.2011 16:56, schrieb Wietse Venema:
>> Robert Schetterer:
>>> Hi , i have relay which smtp transports
>>> to an internal mail server ( work wonderfull )
>>> now i want to use always_bcc
>>> to a local user
>>> seems not work any idea how to
David Touzeau:
> Dear
>
> For some reasons :
> - mistakes
> - bug inside a sender robot
> - emailing application that going to be crazy,
> - Internal infected network with an SMTP worm,
> ...
>
> i would like send a "freeze" command to postfix that stopping the
> routing process for a period o
You may want to try pflogsumm. It's a perl script. See
http://jimsun.linxnet.com/postfix_contrib.html.
Nick
On 9/2/2011 7:59 πμ, meyer-jor...@t-online.de wrote:
I would be surprised if no one before was interested in clearly
readable and
complete mail lists...
H.
sending mail with mutt started failing yesterday with:
postdrop: fatal: getrlimit: Operation not permitted
sendmail: warning: command "/usr/sbin/postdrop -r" exited with status 1
sendmail: fatal: rthompso(303): unable to execute /usr/sbin/postdrop -r: Success
I'm running gentoo, and tend to keep m
Wietse Venema:
> David Touzeau:
> > Dear
> >
> > For some reasons :
> > - mistakes
> > - bug inside a sender robot
> > - emailing application that going to be crazy,
> > - Internal infected network with an SMTP worm,
> > ...
> >
> > i would like send a "freeze" command to postfix that stopping
Reid Thompson:
> sending mail with mutt started failing yesterday with:
> postdrop: fatal: getrlimit: Operation not permitted
Do you have AppArmor/SeLinux/other "security" software enabled?
Wietse
Hi All,
I would like to have suggestion or send me link for migrating to new domain
from old domain.
we have taken subdomain service from ISP
subdomain.xyz.com mail server configured using postfix.
we have registered our domain abc.com
i would like to know how to configure all email coming to
On 2/9/2011 11:12 AM, Ramesh wrote:
Hi All,
I would like to have suggestion or send me link for migrating to new domain
from old domain.
we have taken subdomain service from ISP
subdomain.xyz.com mail server configured using postfix.
we have registered our domain abc.com
i would like to kno
On 2/9/2011 11:33 AM, Reid Thompson wrote:
> sending mail with mutt started failing yesterday with:
> postdrop: fatal: getrlimit: Operation not permitted
> sendmail: warning: command "/usr/sbin/postdrop -r" exited with status 1
> sendmail: fatal: rthompso(303): unable to execute /usr/sbin/postdrop
On 02/09/2011 11:39 AM, Wietse Venema wrote:
> Reid Thompson:
>> sending mail with mutt started failing yesterday with:
>> postdrop: fatal: getrlimit: Operation not permitted
>
> Do you have AppArmor/SeLinux/other "security" software enabled?
>
> Wietse
not intentionally -- ;) i've been us
On 02/09/2011 12:36 PM, Brian Evans - Postfix List wrote:
> On 2/9/2011 11:33 AM, Reid Thompson wrote:
>> sending mail with mutt started failing yesterday with:
>> postdrop: fatal: getrlimit: Operation not permitted
>> sendmail: warning: command "/usr/sbin/postdrop -r" exited with status 1
>> sendm
On 02/09/2011 12:36 PM, Brian Evans - Postfix List wrote:
> On 2/9/2011 11:33 AM, Reid Thompson wrote:
> This was one symptom caused by updating glibc to 2.13
> (http://bugs.gentoo.org/show_bug.cgi?id=354041)
>
> There seems to be a lot of issues with glibc 2.13, particularly on
> 32-bit x86 and e
On 02/09/2011 12:57 PM, Reid Thompson wrote:
> On 02/09/2011 12:36 PM, Brian Evans - Postfix List wrote:
>> On 2/9/2011 11:33 AM, Reid Thompson wrote:
>>> sending mail with mutt started failing yesterday with:
>>> postdrop: fatal: getrlimit: Operation not permitted
>>> sendmail: warning: command "/
Reid Thompson:
> sending mail with mutt started failing yesterday with:
> postdrop: fatal: getrlimit: Operation not permitted
Wietse:
> > Do you have AppArmor/SeLinux/other "security" software enabled?
Reid Thompson:
> not intentionally -- ;) i've been using this system for several
> years with
Hello list,
The things that I miss from OpenBSD are spamd and pf (iptables are
almost there).
It seems that postscreen has the potential to, finally, replace spamd.
So, my question is:
How would one configure postscreen's parameters to act like the spamd
defaults, i.e., passtime = 25 m, gre
On 02/09/2011 01:07 PM, Reid Thompson wrote:
>
> I am running 2.13 glibc as of yesterday which does appear to coincide with my
> issue
Wietse/Brian, thanks for the insight.
Luckily it appears that I have only a hand full of non-essential packages built
against the new glibc.
That being the cas
Mark Alan:
> Hello list,
>
> The things that I miss from OpenBSD are spamd and pf (iptables are
> almost there).
>
> It seems that postscreen has the potential to, finally, replace spamd.
postscreen currently does not implement greylisting - smtpd(8)
currently can do that with policy daemons.
On 2/9/2011 1:16 PM, Mark Alan wrote:
Hello list,
The things that I miss from OpenBSD are spamd and pf (iptables are
almost there).
It seems that postscreen has the potential to, finally, replace spamd.
So, my question is:
How would one configure postscreen's parameters to act like the spa
Le mercredi 09 février 2011 à 11:37 -0500, Wietse Venema a écrit :
> Wietse Venema:
> > David Touzeau:
> > > Dear
> > >
> > > For some reasons :
> > > - mistakes
> > > - bug inside a sender robot
> > > - emailing application that going to be crazy,
> > > - Internal infected network with an SMTP
On Fri, 2011-02-04 at 14:54 -0800, Gary Smith wrote:
> I have a client who sends about 600mgs/week total from their SBS server
> through our email relays. The relay IP has a positive reputation and
> isn't flagged for spam on any of the lists. Recently they had an issue
> in which email they sen
Le 08/02/2011 00:44, Reindl Harald a écrit :
> Am 07.02.2011 22:56, schrieb lst_ho...@kwsoft.de:
>
>> This is your source of recipient checking...
>> So it matters what you get from this by querying with "postmap -q
>>
>> mysql:/etc/postfix/mysql-recipients.cf
>
> exactly this is the reason why
Le 07/02/2011 19:18, Nikolaos Milas a écrit :
> OK Brian,
>
> Per your advice, I modified it as below:
>
>smtpd_restriction_classes = allowed_list1
>allowed_list1= check_client_access cidr:/etc/postfix/client.cidr,reject
>smtpd_recipient_restrictions =
>
> hash:/etc/postfix/protect
37 matches
Mail list logo
