Re: [Mimedefang] $QueueId not allways defined

[Dianne Skoll]

On Mon, 26 Sep 2016 05:59:59 +
Thomas Kristensen  wrote:

> How do i apply the patch? I need to apply it to the source and then
> compile a my self, right?

Yes.  I will probably release 2.79 soon, with the patch.

Regards,

Dianne.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] $QueueId not allways defined

[Thomas Kristensen]

How do i apply the patch? I need to apply it to the source and then compile a 
my self, right?



Med venlig hilsen
Thomas Kristensen

Storhaven 12 - 7100 Vejle
Tlf: 75 72 54 99 - Fax: 75 72 65 33
E-mail: t...@multimed.dk


-Oprindelig meddelelse-
Fra: MIMEDefang [mailto:mimedefang-boun...@lists.roaringpenguin.com] På vegne 
af Dianne Skoll
Sendt: 25. september 2016 20:51
Til: mimedefang@lists.roaringpenguin.com
Emne: Re: [Mimedefang] $QueueId not allways defined

On Sat, 24 Sep 2016 17:20:16 +
Thomas Kristensen <t...@multimed.dk> wrote:

> But it still doesnt work. I still got the NOQUEUE in filter_begin.

Right, you need to apply the patch.

Regards,

Dianne.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above message, 
it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang 
mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


Denne e-mail kan indeholde fortrolig information. Hvis du ikke er den rette 
modtager af denne e-mail eller hvis du modtager den ved en fejltagelse, beder 
vi dig venligst informere afsender om fejlen ved at bruge svarfunktionen. 
Samtidig bedes du slette e-mailen med det samme uden at videresende eller 
kopiere den.

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] $QueueId not allways defined

[Dianne Skoll]

On Sat, 24 Sep 2016 17:20:16 +
Thomas Kristensen  wrote:

> But it still doesnt work. I still got the NOQUEUE in filter_begin.

Right, you need to apply the patch.

Regards,

Dianne.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] $QueueId not allways defined

[Thomas Kristensen]

Thanks for that. I have updated my postfix configuration with the setting.

I use only filter_begin, so i should be good with the mimedefang version i got, 
however i cant seem to find a version number on mimedefang.

But it still doesnt work. I still got the NOQUEUE in filter_begin.

Med venlig hilsen
Thomas Kristensen

Storhaven 12 - 7100 Vejle
Tlf: 75 72 54 99 - Fax: 75 72 65 33
E-mail: t...@multimed.dk

-Oprindelig meddelelse-
Fra: MIMEDefang [mailto:mimedefang-boun...@lists.roaringpenguin.com] På vegne 
af Dianne Skoll
Sendt: 24. september 2016 16:42
Til: mimedefang@lists.roaringpenguin.com
Emne: Re: [Mimedefang] $QueueId not allways defined

On Fri, 23 Sep 2016 22:49:39 -0400
"Bill Cole" <mdlist-20140...@billmail.scconsult.com> wrote:

> So if you're not running MD 2.78 plus the patch available at
> http://lists.roaringpenguin.com/pipermail/mimedefang/2015-April/037618
> .html

Ooh... I really should release 2.79.  I have a few patches in the queue.
Maybe next week...

Regards,

Dianne.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above message, 
it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang 
mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


Denne e-mail kan indeholde fortrolig information. Hvis du ikke er den rette 
modtager af denne e-mail eller hvis du modtager den ved en fejltagelse, beder 
vi dig venligst informere afsender om fejlen ved at bruge svarfunktionen. 
Samtidig bedes du slette e-mailen med det samme uden at videresende eller 
kopiere den.

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] $QueueId not allways defined

[Dianne Skoll]

On Fri, 23 Sep 2016 22:49:39 -0400
"Bill Cole"  wrote:

> So if you're not running MD 2.78 plus the patch available at 
> http://lists.roaringpenguin.com/pipermail/mimedefang/2015-April/037618.html

Ooh... I really should release 2.79.  I have a few patches in the queue.
Maybe next week...

Regards,

Dianne.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] $QueueId not allways defined

[Dianne Skoll]

On Fri, 23 Sep 2016 21:51:19 +
Thomas Kristensen  wrote:

> I just installed postfix and mimedefang, and i works pretty nice.
> But in some cases that $QueueId is not defined, only as NOQUEUE.

Sendmail picks a Queue ID as soon as the MAIL From: SMTP command is
received.

However, Postfix does not... it delays picking a Queue ID until the first
RCPT To: command is received.  So in filter_sender and earlier, no
Queue ID will be available for Postfix users.

Regards,

Dianne.
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Re: [Mimedefang] $QueueId not allways defined

[Bill Cole]

On 23 Sep 2016, at 17:58, Thomas Kristensen wrote:


Hallo

I just installed postfix and mimedefang, and i works pretty nice.
But in some cases that $QueueId is not defined, only as NOQUEUE.

I cant see why this is only happing to some of the mails and not all.
I tend to be some a certin host, but on sometimes the variable is 
fine, even from the host.


How can i debug this even futher to see why the variables is not 
allways defined?


This can be dependent on software versions, since there can be a 
combination of a Postfix quirk and a  MIMEDefang adaptation to that 
quirk which was overdone prior to a fix published in April 2015 which is 
not in the latest release version.


The Postfix quirk is that for performance reasons relevant only to 
rather high-volume systems, by default it delays the assignment of a 
QueueID and creation of a file in its incoming queue directory until it 
has accepted one recipient for a message. This behavior can be changed 
with this Postfix setting:


smtpd_delay_open_until_valid_rcpt = no

That causes Postfix smtpd to create a QueueID as soon as it takes 
control of the SMTP session (either answering it directly or being 
passed the connection from postscreen) so in principle it should be 
available at all stages in the milter protocol. However, until very 
recent versions of MIMEDefang, it assumed the default behavior of 
delaying the creation of the queue file and hence the QueueID, and 
didn't ask for the QueueID at any milter stage before filter_begin. So 
if you're not running MD 2.78 plus the patch available at 
http://lists.roaringpenguin.com/pipermail/mimedefang/2015-April/037618.html 
you will get NOQUEUE as the QueueID at all stages before filter_begin, 
even if Postfix is logging about the message with a QueueID before MD 
logs without one.


And tangentially related...

I also advise this Postfix setting:

enable_long_queue_ids = yes

That makes Postfix use 17-character IDs that encode a timestamp (and 
other information), are created in lexicographic order, and will never 
repeat on one host unless the clock gets set backwards.


___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang