Hi,
Cannot receive email from ansmtp.ariba.com[216.109.104.12]
The following error is in the log.
--- start --
Feb 14 18:26:22 mail postfix/smtpd[210806]: SSL_accept:SSLv3/TLS write
server done
Feb 14 18:26:22 mail postfix/smtpd[210806]: SSL_accept:error in
SSLv3/TLS write
Viktor Dukhovni:
>
>
> > On 16 Feb 2022, at 3:49 pm, Wietse Venema wrote:
> >
> >> Can Postfix accept (without mangling) (with representing
> >> the underlying character) any of:
> >>
> >>Server:
> >>MAIL FROM:<"foo+\bar"@example.com>
> >>RCPT TO:<"foo+\bar"@example.com>
>
On Wed, Feb 16, 2022 at 05:05:39PM -0500, Viktor Dukhovni wrote:
> > There is a mandatory printable() filter in the bounce daemon after
> > it reads a request, before it writes the bounce/defer/etc log (look
> > for the VS_NEUTER macro). ESC does not count as a printable character.
>
> Are envelo
> On 16 Feb 2022, at 3:49 pm, Wietse Venema wrote:
>
>> Can Postfix accept (without mangling) (with representing
>> the underlying character) any of:
>>
>>Server:
>>MAIL FROM:<"foo+\bar"@example.com>
>>RCPT TO:<"foo+\bar"@example.com>
>
> Accepted, and preserved in SMTP/
Viktor Dukhovni:
> Are we sure that presently, even without sanitisation there are no
> valid cases in which the output of "postqueue -j" would contain
> strings with non-printable content?
Definitely no newlines. Because those change the structure of text.
> Can Postfix accept (without mangling)
On Wed, Feb 16, 2022 at 02:15:31PM -0500, Wietse Venema wrote:
> > Well, if a message contains non-printable characters in the sender,
> > one of the recipient addresses, or delay reason, and I process the
> > output of "postqueue -j" in a language that supports JSON ("jq",
> > "python", "perl", .
Wietse Venema:
> Viktor Dukhovni:
> > > On 16 Feb 2022, at 1:20 pm, Wietse Venema wrote:
> > >
> > >> Actually, no, with "-r" not only are quotes removed, but also escaped
> > >> forms are converted back to the underlying UTF-8 form, and control
> > >> characters are output verbatim (as newlines,
Viktor Dukhovni:
> > On 16 Feb 2022, at 1:20 pm, Wietse Venema wrote:
> >
> >> Actually, no, with "-r" not only are quotes removed, but also escaped
> >> forms are converted back to the underlying UTF-8 form, and control
> >> characters are output verbatim (as newlines, ESC, ...).
> >
> > Oops,
> On 16 Feb 2022, at 1:20 pm, Wietse Venema wrote:
>
>> Actually, no, with "-r" not only are quotes removed, but also escaped
>> forms are converted back to the underlying UTF-8 form, and control
>> characters are output verbatim (as newlines, ESC, ...).
>
> Oops, I did an incorrect experiment.
Viktor Dukhovni:
> > On 16 Feb 2022, at 11:43 am, Wietse Venema wrote:
> >
> >> Users who want an unsanitised form of the queue content should
> >> consume JSON.
> >
> > Unsanitized but json-escaped. If people want to unescape that, then
> > they have to write extra code, so 'unsanitized' would
On Wed, Feb 16, 2022 at 12:09:24PM -0500, Viktor Dukhovni wrote:
> > I think I missed that "jq -r" output is still json-escaped. In that
> > light, is there any need for 3.7-style sanitization of json output?
> > We could still revert that early in 3.7.1; I doubt that this would
> > break things a
> On 16 Feb 2022, at 11:43 am, Wietse Venema wrote:
>
>> Users who want an unsanitised form of the queue content should
>> consume JSON.
>
> Unsanitized but json-escaped. If people want to unescape that, then
> they have to write extra code, so 'unsanitized' would still be safe
> for naive scrip
On 2022 Feb 16, at 09:44, Noel Jones wrote:
> To put everything on hold, insert check_client_access static:hold in one of
> your restrictions. Something like:
>
> smtpd_client_restrictions =
> check_client_access static:hold
> ... stuff you have already ...
Thanks, this is perfect. Will start t
On 2022 Feb 16, at 07:49, Viktor Dukhovni wrote:
> Users who want an unsanitised form of the queue content should consume
> JSON.
This is why I need actual messages in the hold queue so I can test. I do prefer
-j if for nothing else that it returns nothing at all when the queue is empty
while -
On 2/16/2022 10:35 AM, @lbutlr wrote:
On 2022 Feb 16, at 06:37, Wietse Venema wrote:
Wietse Venema:
There is an example in the pistsuper manpage that uses "postqueue
-j | jq" to select messages, and to feed a list of queue IDS into
the postsuper command.
Untested example:
postqueue -j | jq
Viktor Dukhovni:
> On Wed, Feb 16, 2022 at 09:42:51AM -0500, Wietse Venema wrote:
>
> > > Alternatively, perhaps there should be an option to turn off the safety
> > > net. Something like the '-J' option below (with appropriate
> > > documentation and warnings).
> >
> > And what about non-json o
On 2022 Feb 16, at 06:37, Wietse Venema wrote:
> Wietse Venema:
>> There is an example in the pistsuper manpage that uses "postqueue
>> -j | jq" to select messages, and to feed a list of queue IDS into
>> the postsuper command.
>>
>> Untested example:
>>
>> postqueue -j | jq -r '
>> # See JSON O
On Wed, Feb 16, 2022 at 09:42:51AM -0500, Wietse Venema wrote:
> > Alternatively, perhaps there should be an option to turn off the safety
> > net. Something like the '-J' option below (with appropriate
> > documentation and warnings).
>
> And what about non-json output?
My view of "postqueue -
Viktor Dukhovni:
> On 16 Feb 2022, at 8:16 am, Wietse Venema wrote:
>
> > postqueue -j | jq -r '
> > # See JSON OBJECT FORMAT section in the postqueue(1) manpage
> > select(.queue_name == "deferred")
> > | .queue_id
> > ' | postsuper -h -
>
> While we're on the topic of JSON output,
On 16 Feb 2022, at 8:16 am, Wietse Venema wrote:
> postqueue -j | jq -r '
> # See JSON OBJECT FORMAT section in the postqueue(1) manpage
> select(.queue_name == "deferred")
> | .queue_id
> ' | postsuper -h -
While we're on the topic of JSON output, FWIW, I am not convinced that
the
Wietse Venema:
> There is an example in the pistsuper manpage that uses "postqueue
> -j | jq" to select messages, and to feed a list of queue IDS into
> the postsuper command.
>
> Untested example:
>
> postqueue -j | jq -r '
> # See JSON OBJECT FORMAT section in the postqueue(1) manpage
>
There is an example in the pistsuper manpage that uses "postqueue
-j | jq" to select messages, and to feed a list of queue IDS into
the postsuper command.
Untested example:
postqueue -j | jq -r '
# See JSON OBJECT FORMAT section in the postqueue(1) manpage
select(.queue_name == "def
A cleaner solution for queueing messages is putting them on a disabled smtp service, but the OP meant how to HOLD them.Look at the ACCESS readme for examples.Op 16 feb. 2022 13:43 schreef Joachim Lindenberg :Don´t know what exactly you are trying to do, but to monitor the queue, I use postqueue -j
Don´t know what exactly you are trying to do, but to monitor the queue, I use
postqueue -j (for json).
Forcing some messages to remain in the queue is easy: just define a transport
policy like dane-only for a destination that does not support dane.
-- Joachim
-Ursprüngliche Nachricht-
Vo
On 2022 Feb 16, at 05:06, @lbutlr wrote:
> What I would like to do is to execute a command that only returns output if
> there are messages on hold
On a related question, is there a way to tell postfix "put all outbound mail
into the hold queue" so I can test some of this?
I know postsuper -h
The man page on sendmail contains a small section on mailq which explains the
display o family. While the postqueue man page says that postqueue -p
implements the mailq command vi shows().
The only mention of 'hold' on either of these man pages is in the description
of the mailq/postqueue -p ou
26 matches
Mail list logo
