Sean McBride via Postfix-users:
> Hi all,
>
> I've been setting up a fresh postfix server, and I've really appreciated
> how great the docs are. In the spirit of making them even better, I'd
> like to share a comment/suggestion.
>
> If I correctly underst
Hi all,
I've been setting up a fresh postfix server, and I've really appreciated
how great the docs are. In the spirit of making them even better, I'd
like to share a comment/suggestion.
If I correctly understand the messy history of port 465 vs 587, for
submission port 58
Thomas Landauer via Postfix-users:
> A detail first:
> At
> http://www.postfix.org/postconf.5.html#smtpd_delay_open_until_valid_rcpt
> please change "mail transaction ID" to "queue ID" for consistency here:
> > The downside is that rejected recipients are logged with NOQUEUE instead of
> > a mai
Hi,
thanks!
A detail first:
At
http://www.postfix.org/postconf.5.html#smtpd_delay_open_until_valid_rcpt
please change "mail transaction ID" to "queue ID" for consistency here:
The downside is that rejected recipients are logged with NOQUEUE instead of a
mail transaction ID
About DSN:
Thank
Thomas Landauer via Postfix-users:
> Since you're creating the queue ID only after `RCPT TO`, we have the
> sender's and the main recipient's address at hand - that would be enough
> to set up something like a `queue_id_prefix_map` :-)
First, the queue ID is not the place for this information. T
always did), so that
delivery notifications were never delegated to remote systems, but
rather confirmed only that the message was transfered to the resposible
remote system successfully.
smtp_discard_ehlo_keywords = dsn,silent-discard
> So coming back to my initial suggestion, after thinking
#x27;s exactly how I'm doing it :-)
Request DSN's from recipient servers:
I already tried this, but it's not really working in practice, since not
all mailservers support DSN :-(
So coming back to my initial suggestion, after thinking some more about it:
Right now, the queue ID
On Tue, Nov 05, 2024 at 12:50:53AM +0100, Thomas Landauer via Postfix-users
wrote:
> my use case: I want to find out if outgoing messages were delivered
> successfully, so I'm looking at the lines containing `status=` in the
> logfile.
>
> But I need this only for some mails (not all). To find ou
Again, use Viktor's collate tool.
Wietse
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
Thomas Landauer via Postfix-users:
> Hi,
>
> my use case: I want to find out if outgoing messages were delivered
> successfully, so I'm looking at the lines containing `status=` in the
> logfile.
>
> But I need this only for some mails (not all). To find out, I have to
> query the database for
Is it true that the Queue-ID is generated before Postfix receives the
message content? After which SMTP command?
By default during the RCPT TO stage. But can be changed to happen earlier
during the MAIL FROM stage with performance trade offs.
http://www.postfix.org/postconf.5.html#smtpd_
my use case: I want to find out if outgoing messages were delivered
successfully, so I'm looking at the lines containing `status=` in the
logfile.
But I need this only for some mails (not all). To find out, I have to query
the database for the Queue-ID. This step could be skipped if it would b
Hi,
my use case (same as in previous thread): I want to find out if outgoing
messages were delivered successfully, so I'm looking at the lines
containing `status=` in the logfile.
Problem: I'm running several domains/projects on the same server, so I
need to query multiple databases with the
Hi,
my use case: I want to find out if outgoing messages were delivered
successfully, so I'm looking at the lines containing `status=` in the
logfile.
But I need this only for some mails (not all). To find out, I have to
query the database for the Queue-ID. This step could be skipped if it
Hi,
thanks for the hints, guys - I went for rsyslog omprog and it looks good
so far :-)
--
Cheers,
Thomas
___
Postfix-users mailing list -- postfix-users@postfix.org
To unsubscribe send an email to postfix-users-le...@postfix.org
I need to find out if an outgoing message was successfully delivered or not.
I know this can be achieved by setting up some filesystem watcher for the
logfile, and/or by having a cronjob searching through the logfile for the
line containing `status=`.
But it would be so much nicer if Postfix wou
Thomas Landauer via Postfix-users:
> Hi,
>
> my use case:
> I need to find out if an outgoing message was successfully delivered or not.
> I know this can be achieved by setting up some filesystem watcher for
> the logfile, and/or by having a cronjob searching through the logfile
> for the line
Hi,
my use case:
I need to find out if an outgoing message was successfully delivered or not.
I know this can be achieved by setting up some filesystem watcher for
the logfile, and/or by having a cronjob searching through the logfile
for the line containing `status=`.
But it would be so much ni
Jim Garrison:
> Under the `-n` option, the man page currently says
>
> To show settings that differ from built-in defaults only,
> use the following bash syntax:
> comm -23 <(postconf -n) <(postconf -d)
> Replace "-23" with "-12" to show settings that duplicate built-in
>
Under the `-n` option, the man page currently says
To show settings that differ from built-in defaults only,
use the following bash syntax:
comm -23 <(postconf -n) <(postconf -d)
Replace "-23" with "-12" to show settings that duplicate built-in
defaults.
Curiously, with
On 2022-05-04 20:37, li...@lazygranch.com wrote:
Quad 9 uses a number of DNS servers with different names but I guess
that isn't good enough. I had set up unbound on the VPS used for my VPN
when I set up dnscrypt. I don't recall why I pulled it. I am going to
give systemd resolved a try. I suspec
On Wed, 4 May 2022 20:47:16 +0200
Arrigo Triulzi wrote:
> On 4 May 2022, at 20:40, li...@lazygranch.com wrote:
> >
> > Though not currently bouncing my maillog had this message
> > (sanitized because of Google):
> >
> > NOQUEUE: reject: RCPT from avasout-peh-001.plus.net[212.159.14.17]:
> >
If spamhaus gets too many queries from a particular DNS server it issues
a response of 127.255.255.X (where X can be any number from 1 - 255).
This does not indicate SPAM but rather it indicates an overusage
condition of Spamhaus. the warn if reject line is intending to warn the
email admin of
On 4 May 2022, at 20:40, li...@lazygranch.com wrote:
>
> Though not currently bouncing my maillog had this message (sanitized
> because of Google):
>
> NOQUEUE: reject: RCPT from avasout-peh-001.plus.net[212.159.14.17]: 554 5.7.1
> Service unavailable; Client host [212.159.14.17] blocked using
Though not currently bouncing my maillog had this message (sanitized
because of Google):
NOQUEUE: reject: RCPT from avasout-peh-001.plus.net[212.159.14.17]: 554 5.7.1
Service unavailable; Client host [212.159.14.17] blocked using
zen.spamhaus.org; Error: open resolver;
https://www.spamhaus.org
Adrian van Bloois:
> Hi,
> Recently I was confronted with an error message like:
> Can't write to /var/spool/mail/BLADDDIBLA
> It took me another hour or so to find out why not.
> It would be helpful if the error message would read something like:
> Can't wite to /var/spool/mail/BLADIBLA, mailboxsi
Hi,
Recently I was confronted with an error message like:
Can't write to /var/spool/mail/BLADDDIBLA
It took me another hour or so to find out why not.
It would be helpful if the error message would read something like:
Can't wite to /var/spool/mail/BLADIBLA, mailboxsize exceeded
This would make so
On 2/19/21 1:51 PM, Wietse Venema wrote:
Postfix CIDR maps support CIDR. I don't understand how one
would implement CIDR lookup keys in a hash: map.
me either, thanks and to others who replied also
It would be handy if postmap hash:foo printed a warning if it encountered
CIDR or any other pro
Wietse Venema wrote in
<4bcx7t0nfyzj...@spike.porcupine.org>:
|Steffen Nurpmeso:
|> Wietse Venema wrote in
|> <4bcnlx0tr4zj...@spike.porcupine.org>:
|>|Steffen Nurpmeso:
|>|> Wietse Venema wrote in
|>|> <4bcgr00pr0zj...@spike.porcupine.org>:
|>|>|Steffen Nurpmeso:
|>|>|> It would be grea
Steffen Nurpmeso:
> Wietse Venema wrote in
> <4bcnlx0tr4zj...@spike.porcupine.org>:
> |Steffen Nurpmeso:
> |> Wietse Venema wrote in
> |> <4bcgr00pr0zj...@spike.porcupine.org>:
> |>|Steffen Nurpmeso:
> |>|> It would be great if a hook could be called for such events. Even
> |>|> a simple f
Wietse Venema wrote in
<4bcnlx0tr4zj...@spike.porcupine.org>:
|Steffen Nurpmeso:
|> Wietse Venema wrote in
|> <4bcgr00pr0zj...@spike.porcupine.org>:
|>|Steffen Nurpmeso:
|>|> It would be great if a hook could be called for such events. Even
|>|> a simple fork+detach+exec+forget approach wo
On 26 Aug 2020, at 14:48, Phil Stracchino wrote:
> On 2020-08-26 16:03, Viktor Dukhovni wrote:
>> On Wed, Aug 26, 2020 at 09:59:34PM +0200, Jaroslaw Rafa wrote:
>>
>>> Dnia 27.08.2020 o godz. 07:53:05 Peter pisze:
>>>
>>> Or just use fail2ban.
>>
>> Yes, but the whole point is that fail2ban is
Steffen Nurpmeso:
> Wietse Venema wrote in
> <4bcgr00pr0zj...@spike.porcupine.org>:
> |Steffen Nurpmeso:
> |> It would be great if a hook could be called for such events. Even
> |> a simple fork+detach+exec+forget approach would be really great,
> |> with an event indicator and an IP address
Viktor Dukhovni wrote in
<20200826195500.gc37...@straasha.imrryr.org>:
|On Wed, Aug 26, 2020 at 08:41:14PM +0200, Steffen Nurpmeso wrote:
|> One more thing i could contribute, just in case you do not know
|> about it. Christos Zoulas of NetBSD has written a blocklist (it
|> was blacklist for
Peter wrote in
:
|On 27/08/20 6:41 am, Steffen Nurpmeso wrote:
|> You know, i always could not understand why people use expensive
|> logfile parsers to reach out for state that the server(s) had once
|> they made their decision, which resulted in the logfile entry.
|> That is just grazy. Ta
Wietse Venema wrote in
<4bcgr00pr0zj...@spike.porcupine.org>:
|Steffen Nurpmeso:
|> It would be great if a hook could be called for such events. Even
|> a simple fork+detach+exec+forget approach would be really great,
|> with an event indicator and an IP address as an argument.
|
|We don't
Hi Phil,
I presume you mean fail2ban here…if so, I must respectfully dissent… :=)
I agree that early on, the docs were horrible (to say the least) but more
recently, I think the dev has done a fair job making f2b easier to implement
and use.
Now granted, I do only use it for checking SASL a
On 2020-08-26 17:01, Benny Pedersen wrote:
> Phil Stracchino skrev den 2020-08-26 22:48:
>
>> This is why I keep thinking about writing my own single-purpose tool
>> that does NOTHING BUT monitor mail.log for abusive IPs and remotely
>> tell
>> the firewall to banhammer them.
>
> try keep it smt
Phil Stracchino skrev den 2020-08-26 22:48:
This is why I keep thinking about writing my own single-purpose tool
that does NOTHING BUT monitor mail.log for abusive IPs and remotely
tell
the firewall to banhammer them.
try keep it smtp atleast, postscreen is not that bad
add abusive ips to s
On 2020-08-26 16:03, Viktor Dukhovni wrote:
> On Wed, Aug 26, 2020 at 09:59:34PM +0200, Jaroslaw Rafa wrote:
>
>> Dnia 27.08.2020 o godz. 07:53:05 Peter pisze:
>>
>> Or just use fail2ban.
>
> Yes, but the whole point is that fail2ban is rather a hack, and NetBSD
> actually has a decent framework
On Wed, Aug 26, 2020 at 09:59:34PM +0200, Jaroslaw Rafa wrote:
> Dnia 27.08.2020 o godz. 07:53:05 Peter pisze:
> >
> > You can go a level up without having to involve Postfix and it's not
> > so expensive. many syslog daemons allow you to match certain lines
> > and do a call out to a shell func
Dnia 27.08.2020 o godz. 07:53:05 Peter pisze:
>
> You can go a level up without having to involve Postfix and it's not
> so expensive. many syslog daemons allow you to match certain lines
> and do a call out to a shell function exactly the way you're asking.
> for example, rsyslog has a "Shell ex
On Wed, Aug 26, 2020 at 08:41:14PM +0200, Steffen Nurpmeso wrote:
> One more thing i could contribute, just in case you do not know
> about it. Christos Zoulas of NetBSD has written a blocklist (it
> was blacklist for quite some years, but it losts it colour), and
> patched the postfix (among oth
On 27/08/20 6:41 am, Steffen Nurpmeso wrote:
You know, i always could not understand why people use expensive
logfile parsers to reach out for state that the server(s) had once
they made their decision, which resulted in the logfile entry.
That is just grazy. Take this for example
You can go a
Steffen Nurpmeso:
> It would be great if a hook could be called for such events. Even
> a simple fork+detach+exec+forget approach would be really great,
> with an event indicator and an IP address as an argument.
We don't do ad-hoc special-case solutions.
Wietse
Hello.
One more thing i could contribute, just in case you do not know
about it. Christos Zoulas of NetBSD has written a blocklist (it
was blacklist for quite some years, but it losts it colour), and
patched the postfix (among others) that is in the NetBSD base
system to reach out and call a hook
John Fawcett:
> On 01/01/2019 17:56, Wietse Venema wrote:
> > John Fawcett:
> JFTR, this is what a full implementation would look like.
> A full implementation would update a new SMTP_STATE violation_mask
> field for specific violation categories (syntax, pipelining,
> plaintext
On 01/01/2019 17:56, Wietse Venema wrote:
> John Fawcett:
JFTR, this is what a full implementation would look like.
A full implementation would update a new SMTP_STATE violation_mask
field for specific violation categories (syntax, pipelining,
plaintext, relay, unverified-addres
John Fawcett:
> >> JFTR, this is what a full implementation would look like.
> >> A full implementation would update a new SMTP_STATE violation_mask
> >> field for specific violation categories (syntax, pipelining,
> >> plaintext, relay, unverified-address, unknown-user, access-deny,
> >> dnsbl, tl
On 30/12/2018 20:20, John Fawcett wrote:
> On 30/12/2018 18:05, Wietse Venema wrote:
>> John Fawcett:
>>> On 30/12/2018 01:19, Wietse Venema wrote:
>>> Here's a revised patch implementing the above logging.
>>>
>>> I did not take out the existing pipelining logging since it provides
>>> additional
On 30/12/2018 18:05, Wietse Venema wrote:
> John Fawcett:
>> On 30/12/2018 01:19, Wietse Venema wrote:
>> Here's a revised patch implementing the above logging.
>>
>> I did not take out the existing pipelining logging since it provides
>> additional info over the new error summary in the disconnect
John Fawcett:
> On 30/12/2018 01:19, Wietse Venema wrote:
> > John Fawcett:
> >>> I would not log this for EVERY command. Especially because the
> >>> logged text size by far exceeds the command size (each logfile
> >>> record takes ~100 bytes, while the client needs to send only four
> >>> charact
On 30/12/2018 01:19, Wietse Venema wrote:
> John Fawcett:
>>> I would not log this for EVERY command. Especially because the
>>> logged text size by far exceeds the command size (each logfile
>>> record takes ~100 bytes, while the client needs to send only four
>>> characters plus CRLF.
>>>
>>> For
John Fawcett:
> > I would not log this for EVERY command. Especially because the
> > logged text size by far exceeds the command size (each logfile
> > record takes ~100 bytes, while the client needs to send only four
> > characters plus CRLF.
> >
> > For example, Postfix logs pipelining errors inc
On 29/12/2018 23:20, Wietse Venema wrote:
> Sorry, I did not recognize the diff because all whitespace was using
> UTF8 code points, and I read mail with a text editor that is optimized
> for programing, not for text processing.
>
> After fixing the whitespace:
Thanks for reviewing it further. I've
Sorry, I did not recognize the diff because all whitespace was using
UTF8 code points, and I read mail with a text editor that is optimized
for programing, not for text processing.
After fixing the whitespace:
> --- smtpd/smtpd.c.orig2018-12-28 13:18:55.427162049 +0100
> +++ smtpd/smtpd.c
John Fawcett:
> Hi
>
> I'd like to make two suggestions for additional logging.
>
> The first one is to leave an explicit trace in the log when starttls is
> enforced (for example on the submission port) but the client does not
> issue STARTTLS.
There is no code in Postfix to log something that
On 29/12/2018 13:59, Patrick Ben Koetter wrote:
> * John Fawcett :
>> The first one is to leave an explicit trace in the log when starttls is
>> enforced (for example on the submission port) but the client does not
>> issue STARTTLS.
> Have you tried to set reject_plaintext_session and trace its er
* John Fawcett :
> The first one is to leave an explicit trace in the log when starttls is
> enforced (for example on the submission port) but the client does not
> issue STARTTLS.
Have you tried to set reject_plaintext_session and trace its error message in
the log?
p@rick
--
[*] sys4 AG
h
Hi
I'd like to make two suggestions for additional logging.
The first one is to leave an explicit trace in the log when starttls is
enforced (for example on the submission port) but the client does not
issue STARTTLS.
The second one is to explicitly log that a protocol error has occurred.
Curren
Folks, if you build Postfix from source code, then it needs UNIX
tools including a compiler and various scripting languages.
Such a configuration is fundamentally in conflict with the idea of
running a minimal system.
I have added a check for a missing 'm4' command, but I do not expect
to enumera
On 02/25/2018 09:52 PM, @lbutlr wrote:
Really? What runs services automatically? The last time I setup freeeBSD 11.1
(last month) it wasn't even running sshd until I specifically enabled it.
There are other distributions of POSIX-compliant operating systems.
(Let's forego the religious war ab
On 26 Feb 2018, at 0:52, @lbutlr wrote:
Really? What runs services automatically?
The whole RedHat family, even Fedora Core through last month. SLES &
openSUSE at least through 11.1. Whatever the current stable Ubuntu was
about a year ago.
The last time I setup freeeBSD 11.1 (last month) i
On 02/25/2018 07:17 PM, Bill Cole wrote:
The package that don't matter are just taking a little bit of space,
and it is hardly worth building a system by hand to save a tiny amount
(percentage-wise) of space.
But storage footprint is re-emerging as an issue with the rise of
"cloud" systems li
On 2018-02-25 (20:17 MST), Bill Cole
wrote:
>
> On 25 Feb 2018, at 2:54 (-0500), @lbutlr wrote:
>
>> I used to do the same back int eh 90s where trying to slim down the OS was
>> really worth the effort. Now though, a full base install is well under a
>> handful of GB, or less than 1% of a
On 25 Feb 2018, at 2:54 (-0500), @lbutlr wrote:
I used to do the same back int eh 90s where trying to slim down the
OS was really worth the effort. Now though, a full base install is
well under a handful of GB, or less than 1% of a small hard drive.
There is also the independent issue of sec
On 25/02/18 01:18, Wietse Venema wrote:
> John Fawcett:
>> I was wondering if it might be wise to make m4 a mandatory prerequisite,
>> without which compilation would fail.?
> We could add this at the top of the script:
>
> m4
> but that would be a point solution. For a dependency list someone
On 25/02/18 08:54, @lbutlr wrote:
> On 2018-02-25 (00:37 MST), John Fawcett wrote:
>> I normally start out with the minimal set of packages and only add
>> software that I need to those. While make was already there, the
>> compiler and m4 were missing. I installed the compiler but forgot m4, so
>
On 25/02/18 09:07, Peter wrote:
> On 25/02/18 19:27, Bastian Blank wrote:
>> On Sat, Feb 24, 2018 at 07:18:32PM -0500, Wietse Venema wrote:
>>> We could add this at the top of the script:
>>> m4 > Using "set -e" is much more effective and finds all errors.
> Please no. set -e is an attempt to
On 25/02/18 19:27, Bastian Blank wrote:
> On Sat, Feb 24, 2018 at 07:18:32PM -0500, Wietse Venema wrote:
>> We could add this at the top of the script:
>> m4
> Using "set -e" is much more effective and finds all errors.
Please no. set -e is an attempt to cover all error cases without
bailin
On 2018-02-25 (00:37 MST), John Fawcett wrote:
>
> On 25/02/18 01:18, Wietse Venema wrote:
>> John Fawcett:
>>>
>>> I was wondering if it might be wise to make m4 a mandatory prerequisite,
>>> without which compilation would fail.?
>> We could add this at the top of the script:
>>
>>m4
On 25/02/18 01:18, Wietse Venema wrote:
> John Fawcett:
>>
>> I was wondering if it might be wise to make m4 a mandatory prerequisite,
>> without which compilation would fail.?
> We could add this at the top of the script:
>
> m4
> but that would be a point solution. For a dependency list
On 25/02/18 03:09, @lbutlr wrote:
> On 2018-02-24 (09:44 MST), John Fawcett wrote:
>> due to the fact I had forgotten to install m4.
> Interesting. m4 is part of my base install. At least I think it is, it's not
> in /usr/local/... and i don't remember installing it.
>
In this case I didn't chose
On Sat, Feb 24, 2018 at 07:18:32PM -0500, Wietse Venema wrote:
> We could add this at the top of the script:
> m4 I find it sad that systems have make but not m4. That tool has been
> around as part of the UNIX toolkit for over 30 years, on all the
> systems that I have played with.
| $ dpkg
On 2018-02-24 (09:44 MST), John Fawcett wrote:
>
> due to the fact I had forgotten to install m4.
Interesting. m4 is part of my base install. At least I think it is, it's not in
/usr/local/... and i don't remember installing it.
--
Everywhere is walking distance if you have the time.
John Fawcett:
> Hi
>
> this is a strange error. I just had the chance to reinstall postfix from
> latest snapshot source on a new centos 7 server.
>
> When running postconf -n I was getting various errors relating to unused
> parameters from mysql map configuration files. This is an example of th
Hi
this is a strange error. I just had the chance to reinstall postfix from
latest snapshot source on a new centos 7 server.
When running postconf -n I was getting various errors relating to unused
parameters from mysql map configuration files. This is an example of the
message:
postconf: warnin
On Mon, 2015-06-08 at 16:32 +, Viktor Dukhovni wrote:
> Note that "smtp_use_tls = yes" is obsolete, the preferred interface
> is:
>
> http://www.postfix.org/postconf.5.html#smtp_tls_security_level
Thanks Viktor, I've updated my config to use that.
Andy
On Mon, 2015-06-08 at 14:59 -0400, Wietse Venema wrote:
> Andrew Beverley:
> > On Mon, 2015-06-08 at 11:58 -0400, Wietse Venema wrote:
> > > What other TLS settings do you consider required? Postfix does not
> > > need a client certificate for sending email.
> >
> > My mistake. I'd added in some o
Andrew Beverley:
> On Mon, 2015-06-08 at 11:58 -0400, Wietse Venema wrote:
> > What other TLS settings do you consider required? Postfix does not
> > need a client certificate for sending email.
>
> My mistake. I'd added in some of those settings when I couldn't get it
> working. In actual fact I
On Mon, Jun 08, 2015 at 04:35:01PM +0100, Andrew Beverley wrote:
> Given that SASL authentication over TLS is becoming more prevalent, I
> think it would be worth adding a small note to this section:
>
> http://www.postfix.org/SOHO_README.html#client_sasl_enable
>
> stating that "smtp_use_tls =
On Mon, 2015-06-08 at 11:58 -0400, Wietse Venema wrote:
> What other TLS settings do you consider required? Postfix does not
> need a client certificate for sending email.
My mistake. I'd added in some of those settings when I couldn't get it
working. In actual fact I was missing:
smtp_sasl_tls_s
Andrew Beverley:
> Hi,
>
> Just a quick suggestion for the excellent Postfix documentation.
>
> Given that SASL authentication over TLS is becoming more prevalent, I
> think it would be worth adding a small note to this section:
>
> http://www.postfix.org/SOHO_README
Hi,
Just a quick suggestion for the excellent Postfix documentation.
Given that SASL authentication over TLS is becoming more prevalent, I
think it would be worth adding a small note to this section:
http://www.postfix.org/SOHO_README.html#client_sasl_enable
stating that "smtp_use_tls
Hello,
the last day I had to search messages in our "poor man's second
chance" storage.
( an always_bcc solution ). *finding* messages was painful.
using my logging I could follow any message by its queueid. But
finally messages
are delivered by a local transport telling 10 times: yes, I
does.
Suggestion:
- In other words, with the smtp_reply_filter listed below, the delivery
chances are significantly increased and might be a good idea to implement a
smtp_(cisco?)_workaround_(harderror?) = yes/no.
Here is my smtp_reply_filter (first in line works in real case, the others
are
On Mon, 2 Jun 2014 11:38:27 +0300
"Marius Gologan" wrote:
> Where can I make a suggestion?
>
What kind suggestion? You can post here..
Hi,
Where can I make a suggestion?
Regards,
Marius.
On 2/13/2014 9:12 AM, Fabio Sangiovanni wrote:
> Hi everybody,
>
> I'm looking for a software to perform URIBLDNS body checks to use as
> a before-queue filter.
> The main requirement is massive speed (<100ms scan time), thus I am
> avoiding amavisd-new + spamassassin, even with tuned rules, in fa
Am 13.02.2014 16:12, schrieb Fabio Sangiovanni:
> Hi everybody,
>
> I'm looking for a software to perform URIBLDNS body checks to use as a
> before-queue filter.
> The main requirement is massive speed (<100ms scan time), thus I am
> avoiding amavisd-new + spamassassin, even with tuned rules, in f
Fabio Sangiovanni:
> Hi everybody,
>
> I'm looking for a software to perform URIBLDNS body checks to use as a
> before-queue filter.
You could use body_checks with a tcp: or socketmap: server. The
socketmap protocol originates from Sendmail, and therefore I expect
that there are socketmap server
Hi everybody,
I'm looking for a software to perform URIBLDNS body checks to use as a
before-queue filter.
The main requirement is massive speed (<100ms scan time), thus I am
avoiding amavisd-new + spamassassin, even with tuned rules, in favor of
something written in a compiled language. Suppor
Wietse Venema:
> Peter:
> > The downside to this is if there's any % characters in the username or
> > password it will come out wrong. I recommend instead:
> >
> > $ printf '\0%s\0%s' 'username' 'password' | openssl base64
> > AHVzZXJuYW1lAHBhc3N3b3Jk
>
> That is a good point. In particular % w
Jerry:
> On Tue, 21 Jun 2011 20:07:02 -0400 (EDT)
> Wietse Venema articulated:
>
> > > Using FreeBSD-8.2 with GNU bash, version 4.1.10(1)-release
> > > (amd64-portbld-freebsd8.2) as the default shell.
> > >
> > > echo -ne '\000username\000password' | openssl base64
> > > AHVzZXJuYW1lAHBhc3N3b3Jk
On Tue, 21 Jun 2011 20:07:02 -0400 (EDT)
Wietse Venema articulated:
> > Using FreeBSD-8.2 with GNU bash, version 4.1.10(1)-release
> > (amd64-portbld-freebsd8.2) as the default shell.
> >
> > echo -ne '\000username\000password' | openssl base64
> > AHVzZXJuYW1lAHBhc3N3b3Jk
>
> This does not work
On Tue, 2011-06-21 at 19:20:52 -0400, Wietse Venema wrote:
> Sahil Tandon:
> > Appears to work in bash and zsh; not in (t)csh. I quickly tested on
> > FreeBSD and Darwin. Likely related to handling of null byte/char.
>
> I'm away from home, so I can't quickly fire up a ksh box. It certainly
>
On 06/22/2011 08:07 AM, Wietse Venema wrote:
>>>
>>> I'm away from home, so I can't quickly fire up a ksh box. It certainly
>>> does not work with FreeBSD8 /bin/sh.
Since I always have one:
works perfectly well in ksh
Uwe
a special utility to generate the auth string and the other
> > > > > requires installing a perl module. I have a third suggestion:
> > > > >
> > > > > echo -ne '\000username\000password' | openssl base64
> > > > >
> >
AIN SASL authentication. There are some methods suggested
> > > > for generating the base64 hash required to do the
> > > > authentication, Of those two methods one requires downloading
> > > > a special utility to generate the auth string and the other
> >
On Tue, 21 Jun 2011, Rich Wales wrote:
printf '\000user\000pass' | openssl base64
This appears to work OK in tcsh and sh on Linux (Ubuntu Maverick).
It also works if I write "\0" instead of "\000".
Careful, that won't do the right thing if either string starts with a
valid octal digit. Eit
1 - 100 of 132 matches
Mail list logo
