On 12/15/2011 11:14 AM, Michael Weissenbacher wrote:
> All i can tell is that some mails (like 1 out of 2) get corrupted in
> the process and end up being unusable. I cannot disable amavis
> completely as spam hell would break lose. I cannot disable apache-james
> because it contains some cust
schrieb Noel Jones:
>
>
> The previously supplied link suggests using the postcat(1) command.
> http://www.postfix.org/postconf.5.html#dont_remove
> http://www.postfix.org/postcat.1.html
>
>
>
> -- Noel Jones
>
Noel, you have been MOST helpful, thanks again! This substantinates my
choice o
On 12/15/2011 12:00 PM, Michael Weissenbacher wrote:
> schrieb Noel Jones:
>>
>>
>> This sounds like one of the very rare cases where the obscure
>> http://www.postfix.org/postconf.5.html#dont_remove
>> option might be helpful.
>>
>> something like
>> # main.cf
>> dont_remove = 1
>> hash_queue_name
I wrote:
>
> Just one last question: what is the best way to inspect postfix's queue
> files? They look odd in vim :-)
>
OMG i'm sorry, i just found out about postcat [1] myself, silly me.
[1] http://www.postfix.org/postcat.1.html
Thanks for your help!
cheers,
Michael
schrieb Noel Jones:
>
>
> This sounds like one of the very rare cases where the obscure
> http://www.postfix.org/postconf.5.html#dont_remove
> option might be helpful.
>
> something like
> # main.cf
> dont_remove = 1
> hash_queue_names = deferred, defer, saved
>
> If you expect to have more tha
>
> You may enable archive quarantine in your pre-queue amavis,
> e.g.:
>
> $archive_quarantine_method = 'local:archive-%m';
> $archive_quarantine_to = 'archive-quarantine'; # default
>
> to be able to compare a corrupted message to what was seen
> by amavisd. This would not help if a pr
Michael,
> Yeah, unlikely but possible. In fact the mail passes through 2 filters
> before being returned to postfix:
> postfix:25 -> amavis:10024 -> apache-james:10025 -> postfix:10026 ->
> smarthost
>
> All i can tell is that some mails (like 1 out of 2) get corrupted in
> the process and e
schrieb James Day:
> It should be delivered via the local transport, just set "-o content_filter="
> under local in master.cf to override.
>
Clever. Tried it, but somehow it doesn't work. Mail still passes through
all the filters first. Maybe it's because of my odd filter chain:
postfix:25 -> ama
On 12/15/2011 11:14 AM, Michael Weissenbacher wrote:
> Yeah, unlikely but possible. In fact the mail passes through 2 filters
> before being returned to postfix:
> postfix:25 -> amavis:10024 -> apache-james:10025 -> postfix:10026 ->
> smarthost
>
> All i can tell is that some mails (like 1 out of
schrieb Alfonso Alejandro Reyes Jimenez:
> What about tcpdump capture?, then you can reasemble te tcp stream and see
> whats going on.
>
> You can save the capture to a file, then with wireshark you can reasemble the
> tcpstream looking to those emails like in postfix. You can capture traffic
>
: Re: Possibility to store all incoming mail (pre-content_filter)
Original Message
Subject: Re: Possibility to store all incoming mail (pre-content_filter)
From: Mark Goodge
To: postfix-users@postfix.org
Date: Thu Dec 15 2011 18:04:06 GMT+0100 (CET)
> On 15/12/2011 16
Original Message
Subject: Re: Possibility to store all incoming mail (pre-content_filter)
From: Mark Goodge
To: postfix-users@postfix.org
Date: Thu Dec 15 2011 18:04:06 GMT+0100 (CET)
> On 15/12/2011 16:58, Michael Weissenbacher wrote:
>> schrieb Mark Goodge:
>>
On 15/12/2011 16:58, Michael Weissenbacher wrote:
schrieb Mark Goodge:
On 15/12/2011 16:24, Michael Weissenbacher wrote:
Hi!
You can do this with recpients_bcc_maps
Well, as far as i know this just adds a "bcc" address to the message and
as a result the mail would still pass through amavis
postfix-us...@postfix.org [mailto:owner-postfix-us...@postfix.org]
On Behalf Of Michael Weissenbacher
Sent: 15 December 2011 16:58
To: postfix-users@postfix.org
Subject: Re: Possibility to store all incoming mail (pre-content_filter)
schrieb Mark Goodge:
> On 15/12/2011 16:24, Michael Weissenbacher
schrieb Mark Goodge:
> On 15/12/2011 16:24, Michael Weissenbacher wrote:
>> Hi!
>>>
>>> You can do this with recpients_bcc_maps
>>>
>> Well, as far as i know this just adds a "bcc" address to the message and
>> as a result the mail would still pass through amavis and through the
>> smarthost before
On 15/12/2011 16:24, Michael Weissenbacher wrote:
Hi!
You can do this with recpients_bcc_maps
Well, as far as i know this just adds a "bcc" address to the message and
as a result the mail would still pass through amavis and through the
smarthost before leaving the system, thus it would get al
Hi!
>
> You can do this with recpients_bcc_maps
>
Well, as far as i know this just adds a "bcc" address to the message and
as a result the mail would still pass through amavis and through the
smarthost before leaving the system, thus it would get altered (and
destroyed if i hit the bug).
On Thu, Dec 15, 2011 at 04:30:34PM CET, Michael Weissenbacher
said:
> Hi Postfix Gurus!
> Is there a possibility to store all incoming mail in a central folder at
> postfix level. I am trying to find a nasty bug in one of our backend
> systems which corrupts mail data before they a
Hi Postfix Gurus!
Is there a possibility to store all incoming mail in a central folder at
postfix level. I am trying to find a nasty bug in one of our backend
systems which corrupts mail data before they arrive in the users's
inbox. Therefore i would like to store all imcoming mail unal
19 matches
Mail list logo
