Zsombor B:
> Hi,
>
>
> > Please provide evidence.
>
> This is the point. :)
>
> External client sent us a mail we accepted with queue id "A".
> I have asked them to look for this "A" in their logs.
> I was told they can't find it in thei
Hi,
Please provide evidence.
This is the point. :)
External client sent us a mail we accepted with queue id "A".
I have asked them to look for this "A" in their logs.
I was told they can't find it in their logs.
Zsombor
Idézet (Wietse Venema ):
Zsombor B:
On 09 Feb 2021, at 05:45, Wietse Venema wrote:
> Zsombor B:
>> It turned out during an investigation that our postfix servers don't
>> provide a queue id for the external clients when accepting a new email.
>
> Please provide evidence.
>
> Postfix SMTP client loggin
Zsombor B:
> It turned out during an investigation that our postfix servers don't
> provide a queue id for the external clients when accepting a new email.
Please provide evidence.
Postfix SMTP client logging:
... status=sent (250 2.0.0 Ok: queued as AA92365E6F)
Wietse
Hi,
It turned out during an investigation that our postfix servers don't
provide a queue id for the external clients when accepting a new email.
However the very same servers do provide queue id for internal mail servers.
Is there a specific configuration option to provide the queue id
Wietse Venema wrote:
Below are the SMTP commands/responses, and the test-milter output
showing that the second "DATA" event is reported with the correct
queue ID.
OK, thanks! I'll take it up further with the milter authors.
-kgd
Below are the SMTP commands/responses, and the test-milter output
showing that the second "DATA" event is reported with the correct
queue ID.
Wietse
$ telnet 127.0.0.1 smtp
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.
220-wzv.porcupine.org ESMTP P
-a "$EXTENSION")
> Mar 29 16:36:36 jessie64 postfix/qmgr[17527]: 55ADB428A4: removed
> Mar 29 16:36:38 jessie64 postfix/smtpd[17537]: disconnect from
> localhost[127.0.0.1] helo=1 mail=2 rcpt=2 data=2 quit=1 commands=8
I can't reproduce this. The Milter sends the queue ID
Wietse Venema wrote:
Kris Deugau:
I came across a bit of an information-passing glitch on a system that
uses a milter (MIMEDefang) to glue together complex filter policies.
MIMEDefang is configured to log sender, first recipient, Message-ID (if
any), and the queue ID, along with some filter
Kris Deugau:
> I came across a bit of an information-passing glitch on a system that
> uses a milter (MIMEDefang) to glue together complex filter policies.
>
> MIMEDefang is configured to log sender, first recipient, Message-ID (if
> any), and the queue ID, along with some fil
I came across a bit of an information-passing glitch on a system that
uses a milter (MIMEDefang) to glue together complex filter policies.
MIMEDefang is configured to log sender, first recipient, Message-ID (if
any), and the queue ID, along with some filter result data, for each
message
hyndavirap...@bel.co.in:
I have enabled enable_long_queue_id = yes
That is a non-existent parameter.
Now my doubt is how long, queueids will be unique, for 150 mails/min mail
flow?
http://www.postfix.org/postconf.5.html#enable_long_queue_ids
enable_long_queue_ids (default: no)
Enable
Am 2015-01-22 10:26, schrieb hyndavirap...@bel.co.in:
I have enabled enable_long_queue_id = yes
Now my doubt is how long, queueids will be unique, for 150 mails/min
mail
flow?
The id is build from the time and the file-id within the filesystem.
So each queue_id should be locally unique.
The
Hi,
I have a query regarding queue ids.
In my mail system, 150 mails/min flow is there and I need to keep track of
mails and DSN for atleast 24 hours. To achieve this functionality, I have
modified code as follows.
1. I am logging all mails Queue ids in a text file.(Queueid represents
Rolf E. Sonneveld:
Apr 23 20:26:38 helium postfix-cust1/smtpd[9220]: 3ZwCmG272nz1L8Zd:
client=D57E1702.static.ziggozakelijk.nl[213.126.23.2]
The above logging gives you the link between client and queue ID.
client = D57E1702.static.ziggozakelijk.nl[213.126.23.2]
queue ID
On 04/23/2013 10:14 PM, Wietse Venema wrote:
Rolf E. Sonneveld:
Apr 23 20:26:38 helium postfix-cust1/smtpd[9220]: 3ZwCmG272nz1L8Zd:
client=D57E1702.static.ziggozakelijk.nl[213.126.23.2]
The above logging gives you the link between client and queue ID.
client = D57E1702
the source for my question - is that this always
means a string compare in the database search which is aweful for
performance.
Not if you index the queue-ID properly.
If the database is central to your bounce handling process, you need
this anyway.
--
J.
-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Sonntag, 7. Oktober 2012 13:59
To: Postfix users
Subject: Re: AW: AW: How to change queue id?
Steffen Schebesta:
Hello Witse, I really don't want to get on your nerves but as far as I
understand using the standardized bounce messages from
Message-
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Sonntag, 7. Oktober 2012 13:59
To: Postfix users
Subject: Re: AW: AW: How to change queue id?
Steffen Schebesta:
Hello Witse, I really don't want to get on your
-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Sonntag, 7. Oktober 2012 13:59
To: Postfix users
Subject: Re: AW: AW: How to change queue id?
Steffen Schebesta:
Hello Witse, I really don't want to get on your nerves but as far as I
understand using the standardized bounce messages from
Steffen Schebesta:
Hello Wietse,
ok, here is my problem in detail:
I pass mails to Postfix through smtpd. Postfix sends them out and returns
the queue_id.
...
I parse the mail.log for bounces every hour. When I find a bounce in the log
You are re-inventing an old wheel: it's called list
an application that generates email. You have an MTA that
tries to deliver that email. Now what is the problem? Removing
obsolete addresses from the list? Stop talking about solutions
like changing the queue ID or changing the Postfix logging.
Wietse
-postfix-us...@postfix.org] Im Auftrag von Wietse Venema
Gesendet: Donnerstag, 4. Oktober 2012 14:26
An: Postfix users
Betreff: Re: AW: How to change queue id?
Steffen Schebesta:
If that doesn't work though then maybe I could work around this
problem. I thought about adding the message-id
Am 06.10.2012 18:20, schrieb Steffen Schebesta:
Using Wietse's first approach (adding a custom id to the MAIL FROM address
as an extension) I have tried to output the sender's address in the same
line of the mail.log as the bounce message.
I believe I would need to change the
Steffen Schebesta:
Using Wietse's first approach (adding a custom id to the MAIL FROM address
as an extension) I have tried to output the sender's address in the same
line of the mail.log as the bounce message.
To this end, YOU specify the sender address AT MAIL SUBMISSION TIME,
instead of
in the log together with the recipient address.
This is unnecessary. And I repeat that tinkering with Postfix source
code is not supported.
Postfix returns a standardized bounce message with the old queue
id AND the bounced recipient AND the sender-address-with-your-identier
and the Message-ID
. Oktober 2012 18:47
An: Postfix users
Betreff: Re: How to change queue id?
Steffen Schebesta:
Hello everybody,
I deliver mails to my Postfix through smtpd. Postfix then takes it and
sends it out to the recipient.
Now I'm trying to change the queue_id for each email in Postfix 2.9
source
Steffen Schebesta:
If that doesn't work though then maybe I could work around this problem. I
thought about adding the message-id to the bounce message but that probably
Postfix has lots of options to identify a returned message.
1) You can encode the unique identifier in the envelope sender
-
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Wietse Venema
Sent: Donnerstag, 4. Oktober 2012 14:26
To: Postfix users
Subject: Re: AW: How to change queue id?
Steffen Schebesta:
If that doesn't work though then maybe I could work around this
problem
Hello everybody,
I deliver mails to my Postfix through smtpd. Postfix then takes it and sends
it out to the recipient.
Now I'm trying to change the queue_id for each email in Postfix 2.9 source
code so that it is equal to the Message-ID (it is unique, don't worry) that
I set in the email
Am 03.10.2012 16:53, schrieb Steffen Schebesta:
I deliver mails to my Postfix through smtpd. Postfix then takes it and sends
it out to the recipient.
Now I'm trying to change the |queue_id| for each email in Postfix 2.9 source
code so that it is equal to
the |Message-ID| (it is unique,
On Wed, Oct 03, 2012 at 04:53:22PM +0200, Steffen Schebesta wrote:
I deliver mails to my Postfix through smtpd. Postfix then takes it and sends
it out to the recipient.
One or more recipients. And it may receive one or more copies of
the original message if it was sent to many recipients.
On 10/3/2012 9:53 AM, Steffen Schebesta wrote:
Now I'm trying to change the |queue_id| for each email in Postfix
2.9 source code so that it is equal to the |Message-ID| (it is
unique, don't worry) that I set in the email header when passing the
email to Postfix through smtpd.
Why?
At any
a Message-ID. This field is not
required by current RFC documents.
- Chicken-and-egg problem: Postfix chooses the queue file name (and
creates the file) before it receives the message content.
I suggest that you set enable_long_queue_ids = yes. Long queue ID
strings don't repeat as long as your clock
Gesendet: Mittwoch, 3. Oktober 2012 18:47
An: Postfix users
Betreff: Re: How to change queue id?
Steffen Schebesta:
Hello everybody,
I deliver mails to my Postfix through smtpd. Postfix then takes it and
sends it out to the recipient.
Now I'm trying to change the queue_id for each email
are based on Queue ID in the logs... finding a Queue Id,
parse the log file to grep this Queue Id and get from, to, ip adresses
Every thing goes right execpt that it happens “Queue ID collision” :
for exemple in my logs :
smtp_vm1:~$ cat /var/log/mail.log|grep 79E8223CA90D
May 11 09:32:55
Am 07.06.2012 14:26, schrieb Nico Angenon:
I use Postfix 2.5.5
Every thing goes right execpt that it happens “Queue ID collision”
Is there any way to prevent this?
not with you terrible outdated version
recent is 2.9.3
enable_long_queue_ids = yes
http://www.postfix.org/postconf.5.html
from and
to addresses... My search are based on Queue ID in the logs... finding a
Queue Id, parse the log file to grep this Queue Id and get from, to, ip
adresses
Every thing goes right execpt that it happens “Queue ID collision” :
for exemple in my logs :
smtp_vm1:~$ cat /var/log
Nico Angenon:
Every thing goes right execpt that it happens ?Queue ID collision? :
for exemple in my logs :
The Queue ID is not reused before a message is removed from the queue.
Therefore there are no collisions.
If you need unique queue IDs, use Postfix 2.8 long queue IDs
Wietse
Hello,
I've upgraded to postfix 2.9.1,
put enable_long_queue_ids = yes
in my /etc/postfix/main.cf file, and restarted postfix...
Queue Id seems to be longger and uses all letters in the log file...
Wait see...
Thanks for all.
Nico
-Message d'origine-
From: Wietse Venema
Sent
Hello Postfix Users :)
I am using Postfix with amavisd.
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
by my.postfix-server.org (Postfix) with ESMTPSno Queue ID
Where is the Postfix queue ID?
my master.cf:
smtpd pass - - n
* Chris xchris...@googlemail.com:
Hello Postfix Users :)
I am using Postfix with amavisd.
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
by my.postfix-server.org (Postfix) with ESMTPSno Queue ID
Where is the Postfix queue ID?
It's logged
no Queue ID
Where is the Postfix queue ID?
It's logged by the second smtpd, since the first smtpd using
smtpd_proxy_filter doesn't issue an queueid
Can this be changed?
--
Chris
])
by my.postfix-server.org (Postfix) with ESMTPS no Queue ID
Where is the Postfix queue ID?
It's logged by the second smtpd, since the first smtpd using
smtpd_proxy_filter doesn't issue an queueid
Can this be changed?
Not without getting rid of smtpd_proxy_filter
--
Ralf Hildebrandt
-f174.google.com
[209.85.212.174])
by my.postfix-server.org (Postfix) with ESMTPS no Queue ID
Where is the Postfix queue ID?
It's logged by the second smtpd, since the first smtpd using
smtpd_proxy_filter doesn't issue an queueid
Can this be changed?
Not without getting rid
.
Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com
[209.85.212.174])
by my.postfix-server.org (Postfix) with ESMTPS no Queue ID
Where is the Postfix queue ID?
It's logged by the second smtpd, since the first smtpd using
smtpd_proxy_filter doesn't issue
mail-wi0-f174.google.com
(mail-wi0-f174.google.com [209.85.212.174])
by my.postfix-server.org (Postfix) with ESMTPS no Queue ID
Where is the Postfix queue ID?
It's logged by the second smtpd, since the first smtpd
using smtpd_proxy_filter doesn't issue an queueid
with amavisd.
Received: from mail-wi0-f174.google.com
(mail-wi0-f174.google.com [209.85.212.174])
by my.postfix-server.org (Postfix) with ESMTPS no Queue ID
Where is the Postfix queue ID?
It's logged by the second smtpd, since the first smtpd
using
-Original Message-
From: owner-postfix-us...@postfix.org [mailto:owner-postfix-
us...@postfix.org] On Behalf Of Chris
Sent: 02 March 2012 16:55
To: postfix-users@postfix.org
Subject: Re: Queue ID with amavisd
2012/3/2 /dev/rob0 r...@gmx.co.uk:
On Fri, Mar 02, 2012 at 05:32:18PM
root@pinkie:/var/log# postqueue -p
-Queue ID- --Size-- Arrival Time -Sender/Recipient---
808AD1858E* 459339 Wed Nov 23 17:20:37 i...@dpsdirect.us
@brookeagent.com
2BDBF18581* 459337 Wed Nov 23 17:50:25 i...@dpsdirect.us
On Thu, 24 Nov 2011 02:03:17 +, peng...@sepserver.net wrote:
root@pinkie:/var/log# postqueue -p
-Queue ID- --Size-- Arrival Time -Sender/Recipient---
808AD1858E* 459339 Wed Nov 23 17:20:37 i...@dpsdirect.us
@brookeagent.com
On Sun, Mar 20, 2011 at 03:57:45PM -0400, Wietse Venema wrote:
Below is the manpage entry for long queue ID support. Let me know
if there's anything missing.
With the first few characters of the new long queue-id encoding the
epoch-seconds time and not the micro-seconds time, it seems to me
Wietse Venema:
Victor Duchovni:
On Sun, Mar 20, 2011 at 03:57:45PM -0400, Wietse Venema wrote:
Below is the manpage entry for long queue ID support. Let me know
if there's anything missing.
With the first few characters of the new long queue-id encoding the
epoch-seconds time
Victor Duchovni:
On Sun, Mar 20, 2011 at 03:57:45PM -0400, Wietse Venema wrote:
Below is the manpage entry for long queue ID support. Let me know
if there's anything missing.
With the first few characters of the new long queue-id encoding the
epoch-seconds time and not the micro
On Mon, Mar 21, 2011 at 07:15:44AM -0400, Wietse Venema wrote:
So my proposed update for the long queue id is:
- 4 octets of base 32 encoded tv_usec
- 6+ octets of base 51 encoded tv_sec epoch time
- one non base 51 octet separator
- inode number in base 52.
Better
fairness if incoming is hashed, but perhaps hashing of
incoming should be discouraged. If so, perhaps we don't need to optimize
for locally constant sub-directories.
Also, with a little-endian base 52 queue-id, and hash depth of 2,
we have 2704 directories to search, while big-endian 32 x 32
Victor Duchovni:
Also, with a little-endian base 52 queue-id, and hash depth of 2,
we have 2704 directories to search, while big-endian 32 x 32 takes us
to 977 directories as compared to 245 directories for big-endian base 16.
Base 52 requires fewer levels of hashing than smaller
Wietse Venema:
I could just forget about lexicographical hashing and simply hash
the hexadecimal representation of the microseconds (extracted from
the queue file name and converted from base 52). With this there
would be no change in file distribution compared to Postfix 2.8.
Below is the manpage entry for long queue ID support. Let me know
if there's anything missing.
This code is part of this weekend's snapshot (*). Several iterations
have been running on my systems through the past week.
Wietse
(*) As of Postfix 2.9, snapshot releases happen on weekends
Today I was testing an option for long Postfix queue IDs (queue
file names) that won't be reused for about 30+ years. The idea is
to prepend the 30 least significant bits of the time in seconds to
the queue ID.
For the long queue IDs I chose an encoding that packs more bits in
a queue ID
The idea is to prepend the 30 least significant bits of the time
in seconds to the queue ID.
Btw, 6 more hours to the next 'pretty' decimal unix timestamp: 13
Mark
On 3/12/2011 7:31 PM, Wietse Venema wrote:
[snip]
The problem is that the larger alphabet and longer queue IDs increase
the possibility that existing words will appear inside queue IDs
(consider that the letters C, F, K and U are in the base 32 alphabet
and that a queue ID can be 12 characters
Hello everybody,
I use pipe to start my own script when an email to a certain address
is received. The script will do it's own logging and I want to be able
to correlate that logging with the Postifx logs. The queue id that is
used in the Postifix logs seems ideal for that. I think it's called
logs. The queue id that is
used in the Postifix logs seems ideal for that. I think it's called
queue id in Postfix terminology, but to be clear, I'm referring to
21D5D497FE in the example below:
Nov 11 12:29:39 WCEA006 postfix/smtpd[28104]: 21D5D497FE: client=
That is the Queue-ID, true.
However
Catalin Iacob:
Hello everybody,
I use pipe to start my own script when an email to a certain address
is received. The script will do it's own logging and I want to be able
to correlate that logging with the Postifx logs. The queue id that is
used in the Postifix logs seems ideal for that. I
15.11.2010 14:59, Wietse Venema wrote:
Catalin Iacob:
Hello everybody,
I use pipe to start my own script when an email to a certain address
is received. The script will do it's own logging and I want to be able
to correlate that logging with the Postifx logs. The queue id that is
used
Hi,
I'm trying to write a pipe content filter for postfix.
I have a question, Is There a way to put the queue id of email, to this
content filter?
It would be really useful to write a log file and trace the email flow.
Thanks
On 12/15/2009 5:21 AM, Giovanni Mancuso wrote:
Hi,
I'm trying to write a pipe content filter for postfix.
I have a question, Is There a way to put the queue id of email, to this
content filter?
No.
It would be really useful to write a log file and trace the email flow.
If you write your
Giovanni Mancuso:
Hi,
I'm trying to write a pipe content filter for postfix.
I have a question, Is There a way to put the queue id of email, to this
content filter?
It would be really useful to write a log file and trace the email flow.
The queue ID is in the first RECEIVED: message
Hi
Checking the logs i've noticed that i have the same Queue
Id for two connections... this could be?
I Ask because i was looking for some specific entry and i found more
than one entry
Here is the log
Feb 2 11:33:13 newcosmos postfix/smtpd[11863]: 54EF440BF:
client=localhost
Michael,
From http://www.postfix.org/faq.html:
Postfix names a queue file after its inode number and after the
microsecond part of the time of day. Thus, if a queue file has a name
based on someone elses inode number there is a small chance that the
file name will collide with another queue
On Tue, 2009-02-03 at 17:09 +0100, Martin Schmitt (Schmitt
Systemberatung) wrote:
Michael,
From http://www.postfix.org/faq.html:
Postfix names a queue file after its inode number and after the
microsecond part of the time of day. Thus, if a queue file has a name
based on someone elses
Michael Fernández M wrote:
Hi
Checking the logs i've noticed that i have the same Queue
Id for two connections... this could be?
I Ask because i was looking for some specific entry and i found more
than one entry
Here is the log
The QueueID is not, and is not intended
Hi Victor,
Perfect, thanks a lot! This is the information I was looking for.
Durk
On Thu, Nov 13, 2008 at 10:36:10PM +0100, Durk Strooisma wrote:
I was examining my Postfix logs and saw two sequential sessions using
the same queue ID. I was a bit surprised as I had the assumption
I was examining my Postfix logs and saw two sequential sessions using
the same queue ID. I was a bit surprised as I had the assumption that
queue IDs were generated randomly, which means they should be
practically unique.
Postfix behaves as documented. Please point out where
Durk Strooisma:
I was examining my Postfix logs and saw two sequential sessions using
the same queue ID. I was a bit surprised as I had the assumption that
queue IDs were generated randomly, which means they should be
practically unique.
Postfix behaves as documented. Please point out
@postfix.org
Sent: Friday, November 14, 2008 12:40 PM
Subject: Re: Queue ID gets reused? Not unique?
Durk Strooisma:
I was examining my Postfix logs and saw two sequential sessions
using
the same queue ID. I was a bit surprised as I had the
assumption that
queue IDs were generated randomly
of an email its authoritative tracking.
Just curious. Thanks,
Olivier
- Original Message -
From: Wietse Venema [EMAIL PROTECTED]
To: Postfix users postfix-users@postfix.org
Sent: Friday, November 14, 2008 12:40 PM
Subject: Re: Queue ID gets reused? Not unique?
Durk
Hi all,
I was examining my Postfix logs and saw two sequential sessions using the
same queue ID. I was a bit surprised as I had the assumption that queue IDs
were generated randomly, which means they should be practically unique.
Okay, so this could be a wrong assumption... My question is, how
On Thu, Nov 13, 2008 at 10:36:10PM +0100, Durk Strooisma wrote:
I was examining my Postfix logs and saw two sequential sessions using the
same queue ID. I was a bit surprised as I had the assumption that queue IDs
were generated randomly, which means they should be practically unique
Durk Strooisma:
Hi all,
I was examining my Postfix logs and saw two sequential sessions using the
same queue ID. I was a bit surprised as I had the assumption that queue IDs
were generated randomly, which means they should be practically unique.
Postfix behaves as documented. Please point
81 matches
Mail list logo
