Hi,
I have a seen a few of these messages popping up in the mail.log
over the past weeks. Would someone tell me whether this is a
configuration problem with my server, or a remote site? The 451 error
has appeared from a couple of sites, hence I wonder if the problem lies
with my site. In
Am 13.09.2011 10:54, schrieb Simon Loewenthal/NL/Tele2:
> I have a seen a few of these messages popping up in the mail.log
> over the past weeks. Would someone tell me whether this is a
> configuration problem with my server, or a remote site? The 451 error
> has appeared from a couple of sites
Simon Loewenthal/NL/Tele2:
>
> Hi,
>
> I have a seen a few of these messages popping up in the mail.log
> over the past weeks. Would someone tell me whether this is a
> configuration problem with my server, or a remote site? The 451 error
> has appeared from a couple of sites, hence I won
On 09/13/2011 02:11 PM, Wietse Venema wrote:
> Simon Loewenthal/NL/Tele2:
>>
>> Hi,
>>
>> I have a seen a few of these messages popping up in the mail.log
>> over the past weeks. Would someone tell me whether this is a
>> configuration problem with my server, or a remote site? The 451 erro
Am 13.09.2011 14:34, schrieb Simon Loewenthal/NL/Tele2:
> On 09/13/2011 02:11 PM, Wietse Venema wrote:
>> Simon Loewenthal/NL/Tele2:
>>>
>>> Hi,
>>>
>>> I have a seen a few of these messages popping up in the mail.log
>>> over the past weeks. Would someone tell me whether this is a
>>> co
On 09/13/2011 02:38 PM, Reindl Harald wrote:
>
> Am 13.09.2011 14:34, schrieb Simon Loewenthal/NL/Tele2:
>> On 09/13/2011 02:11 PM, Wietse Venema wrote:
>>> Simon Loewenthal/NL/Tele2:
Hi,
I have a seen a few of these messages popping up in the mail.log
over the past
Hi,
I'm using postfix 2.8.4 and trying to select smtpd_milter based on
sender address.
My check_sender_access is SELECT 'FILTER smtp:[127.0.0.1]:2525'
and using it under smtpd_recipient_restrictions
My master.cf is
127.0.0.1:2525 inet n - n - - smtpd
Jeetu:
> Hi,
>
> I'm using postfix 2.8.4 and trying to select smtpd_milter based on
> sender address.
This is simply not possible, because Milters must see the complete
SMTP session. Postfix will not turn on a Milter in the middle of a
session and replay previous commands to catch up.
W
On 9/13/2011 7:47 AM, Simon Loewenthal/NL/Tele2 wrote:
On 09/13/2011 02:38 PM, Reindl Harald wrote:
why is YOUR server broken if the REMOTE server says "configuration problem"?
Because I had mis-read the the statement back-to-front. Now I
understand it the right way around. :}
You still
Jeetu:
> I get this in logs
> Sep 13 18:41:50 outbound2 postfix/smtpd[29888]: NOQUEUE: filter: RCPT
> from unknown[xx.xx.xx.xx]: : Sender address triggers
> FILTER smtp:[127.0.0.1]:2525; from= to=
> proto=ESMTP helo=
>
> The milter is not getting called.
Your filter on [127.0.0.1]:2525 will be
Jeroen Geilman wrote:
> Bob Proulx wrote:
> >The mail queue has messages addressed to unreachable addresses. I
> >know that if I do nothing that eventually they will expire normally
> >...
>
> Altering the status in-queue will be difficult, so you will have to
> devise a trick.
>
> You can try se
Wietse Venema wrote:
> Bob Proulx:
> > I have been trying to deduce if it is possible to force a message
> > waiting in the mail queue with temporary errors (domain name
> > resolution failures) to bounce right now instead of waiting for the
> > timeout.
>
> It would be incorrect to force a messag
> place an 'n' in the chroot column for each service
Sounds good.
On your advice, I went and turned off chroot, then ran "saslfinger -s" again
(output attached).
I restarted the saslauthd and postfix services before doing so.
You can see that chroot is off for all components.
Further, based on
On 2011-09-13 00:42, mouss wrote:
Le 13/09/2011 00:04, Jeroen Geilman a écrit :
On 2011-09-12 06:21, Alex wrote:
Hi,
I'm trying to configure a disclaimer footer using altermime with
postfix-2.7.5, amavisd-new-2.6.4. I've tried to follow the examples
for creating a new filter, but the messages
Crazedfred:
> > place an 'n' in the chroot column for each service
>
> Sounds good.
>
> On your advice, I went and turned off chroot, then ran "saslfinger -s" again
> (output attached).
> I restarted the saslauthd and postfix services before doing so.
> You can see that chroot is off for all com
Sorry for the delay.
* Crazedfred :
> I ran "saslfinger -c" and "saslfinger -s" and it does appear that many of
> the relevant services are chrooted. I wasn't quite sure, however, so I
> attached the full output of both commands.
You want server-side debug output, which is 'saslfinger -s'.
> Of
16 matches
Mail list logo
