Viktor Dukhovni:
> > On Jan 27, 2021, at 9:40 PM, Andy Smith wrote:
> >
> > Correct, its a dynamic value. It can only be known by reading the reply-to
> > value from the headers of the same message.
>
> One way to do this entirely in Postfix is to:
>
> 1. Delete the evil "From:" header that
Andy Smith:
> On 28-01-2021 00:14, Viktor Dukhovni wrote:
>
> > On Wed, Jan 27, 2021 at 05:30:25PM -0500, Wietse Venema wrote:
>
> >
> > Indeed, though I usually avoid falling in that trap, perhaps I failed
> > in
> > this case to consider whether the user is asking the right question.
> >
>
Hi,
I've switched to REDIS for bayesian storage in Spamassassin more than 4 years
ago, and I've never looked back: very good performances and no problem with
files (like locking for a start).
I wrote about it at the time, unfortunately it's in French ;)
On Thu, Jan 28, 2021 at 12:45:30AM +0100, Michael Agbaglo wrote:
> While the test using postmap was successful, the test with sendmail
> fails. The debug show that for some reason '%s' is holding just the
> domain. Why is that?
$ postconf -d virtual_mailbox_domains
> On Jan 27, 2021, at 9:40 PM, Andy Smith wrote:
>
> Correct, its a dynamic value. It can only be known by reading the reply-to
> value from the headers of the same message.
One way to do this entirely in Postfix is to:
1. Delete the evil "From:" header that matches the "www" user
on input
On 27-01-2021 23:26, Patrick Proniewski wrote:
Hi,
I've switched to REDIS for bayesian storage in Spamassassin more than 4
years ago, and I've never looked back: very good performances and no
problem with files (like locking for a start).
I wrote about it at the time, unfortunately it's in
Hi!
Since there is high traffic on this mailing list I am not sure whether
this problem has been discussed already.
I'm having trouble constructing the .cf files for LDAP.
While the test using postmap was successful, the test with sendmail
fails. The debug show that for some reason '%s' is
On 28-01-2021 00:14, Viktor Dukhovni wrote:
On Wed, Jan 27, 2021 at 05:30:25PM -0500, Wietse Venema wrote:
Indeed, though I usually avoid falling in that trap, perhaps I failed
in
this case to consider whether the user is asking the right question.
If the problem value of the "From:"
On Wed, Jan 27, 2021 at 05:30:25PM -0500, Wietse Venema wrote:
> It's simple enough to replace all instances of w...@example.com with
> something else:
>
> /etc/postfix/main.cf:
> canonical_maps =
> inline:{
> { w...@example.com = other@address }
> }
>
> That will
> Date: Wednesday, January 27, 2021 19:17:48 -0300
> From: Daniel Armando Rodriguez
>
> Hi
>
> Suddenly I'm facing tons of this messages
>
> ... bayes: cannot open bayes databases
> /home/spamd/.spamassassin/bayes_* R/W: lock failed: File exists
>
> A 'solution' found on the web says
Andy Smith:
> On 27-01-2021 20:48, Viktor Dukhovni wrote:
>
> > If absolutely every single message is guaranteed to have a "Reply-To:"
> > that can safely replace "From:", then you could in theory forcibly
> > remove "From:" from every message, and upon encountering "Reply-To:"
> > generate a new
Hi
Suddenly I'm facing tons of this messages
... bayes: cannot open bayes databases /home/spamd/.spamassassin/bayes_*
R/W: lock failed: File exists
A 'solution' found on the web says disable bayes, reload SA, delete such
files and enable bayes again.
Increased values in
default_process_limit
On Wed, Jan 27, 2021 at 03:01:43PM -0500, Alex wrote:
> Some time ago I configured postfix to be multi-instance and now I'm
> realizing some mail being generated locally by new crontab entries are
> bouncing because apparently the main postfix instance doesn't know
> where to send these emails
On 27-01-2021 20:48, Viktor Dukhovni wrote:
If absolutely every single message is guaranteed to have a "Reply-To:"
that can safely replace "From:", then you could in theory forcibly
remove "From:" from every message, and upon encountering "Reply-To:"
generate a new matching "From:" (via
Viktor Dukhovni:
> On Wed, Jan 27, 2021 at 07:05:37PM +0100, Andy Smith wrote:
>
> > In my case it is safe to assume that all mail from this user (www user)
> > will always have "Reply-To" as they are generated by the program Request
> > Tracker which always includes this header. If it were an
Hi,
Some time ago I configured postfix to be multi-instance and now I'm
realizing some mail being generated locally by new crontab entries are
bouncing because apparently the main postfix instance doesn't know
where to send these emails (at least that's my guess).
Jan 27 14:21:02 xavier
On Wed, Jan 27, 2021 at 07:05:37PM +0100, Andy Smith wrote:
> In my case it is safe to assume that all mail from this user (www user)
> will always have "Reply-To" as they are generated by the program Request
> Tracker which always includes this header. If it were an issue I guess
> before the
On 27-01-2021 18:48, Viktor Dukhovni wrote:
Can you more precise in your description, perhaps with a hypothetical
example specifying precisely the form of the input message envelope
and headers and the desired output values of the same.
to be the same as the existing "Reply-To" address from
On Wed, Jan 27, 2021 at 06:12:35PM +0100, Andy Smith wrote:
> I need to rewrite an address (known/fixed, is the localaddress of the
> user sending the email)
I am having trouble parsing this. Email messages have:
- An envelope-sender, specified via the SMTP "MAIL FROM:" command
prior
combro2k combro2k:
> Hi there,
>
> I've been looking for some days for a solution I need to create for a
> customer.
> What we want to achieve is throttling the delivery of mails in the queue.
> Right now we are using 'default_destination_rate_delay = 1s' which allows
> us to send approx. 3600 to
Hi there!
I wonder if someone would be able to help configure a rewrite? I need
to rewrite an address (known/fixed, is the localaddress of the user
sending the email) to be the same as the existing "Reply-To" address
from the message. Ie in Exim I can use the variable "$reply_address". If
On 1/27/2021 8:02 AM, combro2k combro2k wrote:
Hi there,
I've been looking for some days for a solution I need to create for
a customer.
What we want to achieve is throttling the delivery of mails in the
queue.
Right now we are using 'default_destination_rate_delay = 1s' which
allows us to
On 27/01/2021 13:47, David Bürgin wrote:
Thanks everybody – I’ve decided that for me personally handling this is
too much work, and I’ve disabled this particular milter.
(There is an open issue in the OpenDMARC project that I have upvoted:
Hi there,
I've been looking for some days for a solution I need to create for a
customer.
What we want to achieve is throttling the delivery of mails in the queue.
Right now we are using 'default_destination_rate_delay = 1s' which allows
us to send approx. 3600 to each destination maximum in 1
Thanks everybody – I’ve decided that for me personally handling this is
too much work, and I’ve disabled this particular milter.
(There is an open issue in the OpenDMARC project that I have upvoted:
https://github.com/trusteddomainproject/OpenDMARC/issues/77)
25 matches
Mail list logo
