On Thu, Sep 20, 2012 at 09:46:22PM +, Jan Johansson wrote:
Wietse:
> Jan Johansson:
> >> >/^451 PLESK reply text here/ 551 5.2.2 Mailbox full
> > ^SPACE HERE
> >
> >> >Make the PCRE pattern as specific as possible, so that it
> >> >matches only PLESK respo
Jan Johansson:
>> >/^451 PLESK reply text here/ 551 5.2.2 Mailbox full
> ^SPACE HERE
>
>> >Make the PCRE pattern as specific as possible, so that it matches only
>> >PLESK responses.
>>
>> I must be missing something, but with the following pcre-entry
>>
>>
Jan Johansson:
> >/^451 PLESK reply text here/ 551 5.2.2 Mailbox full
^SPACE HERE
> >Make the PCRE pattern as specific as possible, so that it matches only PLESK
> >responses.
>
> I must be missing something, but with the following pcre-entry
>
> /^451 4.5
>>Make the PCRE pattern as specific as possible, so that it matches only PLESK
>>responses.
>
>I must be missing something, but with the following pcre-entry
>
>/^451 4.5.1 Mailbox full/551 5.2.2 Mailbox full
>
>Everything gets rejected with:
>Sep 20 23:19:03 laundromat postfix/smtpd[4083]: NOQUEU
>Otherwise you can try to use the smtp_reply_filter feature. This is an
>incedibly sharp knife for desperate situations. Use at your own risk.
>
>Untested example:
>
>/etc/postfix/main.cf:
>smtp_reply_filter = /etc/postfix/smtp_reply_filter.pcre
>
>/etc/postfix/smtp_reply_filter.pcre:
># T
On Sun, Sep 16, 2012 at 09:16:03AM -0500, Chris Adams wrote:
> Once upon a time, Wietse Venema said:
> > I think he refers to this:
> > This sits among other headers that were added by your Mutt/1.4.2.2i
> > mail reader.
> Ah, that looks like a bug in mutt. It isn't supposed to put the
> sender's
Once upon a time, Wietse Venema said:
> Chris Adams:
> > > P.S.: I complied with your Reply-To: and sent the Cc:. It will fail
> > > SPF, if you're checking that.
> >
> > That's not me; that's the list.
>
> I think he refers to this:
>
> Mail-Followup-To: Chris Adams ,
> Postfix u
Chris Adams:
> > P.S.: I complied with your Reply-To: and sent the Cc:. It will fail
> > SPF, if you're checking that.
>
> That's not me; that's the list.
I think he refers to this:
Mail-Followup-To: Chris Adams ,
Postfix users
This sits among other headers that were added by y
>Maybe PLESK has an option to make "mailbox full" a hard error (to be honest,
>Postfix's own "mailbox full" action is not configurable).
No it appears from googling that this is a "know irk" of the PLESK-community.
>Otherwise you can try to use the smtp_reply_filter feature. This is an
>incedi
Once upon a time, /dev/rob0 said:
> On Sat, Sep 15, 2012 at 06:50:38PM -0500, Chris Adams wrote:
> > I wrote a milter for our Plesk servers to check quota at RCPT TO
> > time instead (and return a permanent error for over-quota) to fix
> > the bad behavior.
>
> Unfortunately that only replaces
On Sat, Sep 15, 2012 at 06:50:38PM -0500, Chris Adams wrote:
> Once upon a time, Wietse Venema said:
> > Maybe PLESK has an option to make "mailbox full" a hard error
> > (to be honest, Postfix's own "mailbox full" action is not
> > configurable).
>
> Unfortunately, no, it isn't. Plesk uses a m
Once upon a time, Wietse Venema said:
> Maybe PLESK has an option to make "mailbox full" a hard error (to be
> honest, Postfix's own "mailbox full" action is not configurable).
Unfortunately, no, it isn't. Plesk uses a milter to check delivery
status during SMTP (which is nice, since that way it
Jan Johansson:
> Ok, I am seeing a lot of mail on one of our machines. They are all
> headed for a few servers running PLESK.
>
> It appears that (from google'ing) that this software generates a
> 451 error when a recipients mailbox is full It is possible to have
> postfix kill of these messages an
13 matches
Mail list logo
