Re: [thelounge] thank you for postfix!

2012-02-05 Thread Pete

On 05/02/2012 02:42, Reindl Harald wrote:

Dear Venema

i would like to thank you for postfix, the best MTA in my opinion
i am happy and think you can't hear this often enough for provide
such a great software for free!


[..]

It is also easy for Postfix noobs like myself to get started. I like how 
I can change the way Postfix behaves using understandable parameter 
names. Lots to learn of course ..


[pete@tooms ~]$ postconf -d | grep mail_version
mail_version = 2.8.7


Regards,

Pete.



smime.p7s
Description: S/MIME Cryptographic Signature


Re: [thelounge] thank you for postfix!

2012-02-05 Thread Wietse Venema
Reindl Harald:
> what a wonderful world could this be if any update would run so smooth
> postfix-2.9.0-2.fc15.20120205.rh.x86_64

Thanks for the kind words. Yes, life would be great if all software
installed little pain. Too often, improvements result in a break
of existing functionality.

Wietse


Pflogsumm Version 1.1.5 Released

2012-02-05 Thread Jim Seymour
Pflogsumm version 1.1.5 has been released. This is a Beta release.

From the ChangeLog:

rel-1.1.5   20120205

Fixed RFC 3339 support.  Releases 1.1.3 and 1.1.4 were badly
broken in this respect.  Thanks and a tip o' the hat to Sven
Hoexter (sven-at-timegate-dot-de) for the help.

Short cycle, this time, but I kind of wanted this one to work w/o
patches ;)

With no bug reports, say, w/in a week or so, I'm going to promote
this one to "stable."

Regards,
Jim
-- 
Note: My mail server employs *very* aggressive anti-spam
filtering.  If you reply to this email and your email is
rejected, please accept my apologies and let me know via my
web form at <http://jimsun.LinxNet.com/contact/scform.php>.


Re: message_size_limit causes postfix to stop delivering messages

2012-02-05 Thread Nick Bright

On 2/4/2012 12:20 PM, Ralf Hildebrandt wrote:

* Nick Bright:


Upon restarting postfix with message_size_limit in place it simply
wouldn't deliver any mail. It accepts the mail in to SMTP just fine,
but it never gets delivered.


Logs?



There are no log entries other than normal entries reflecting that the 
messages have been accepted for delivery, though per another posters' 
recommendation; I will enable debug logging and give it another look. I 
also installed postfix-perl-utils and will examine which queue the 
messages are piling up in with pfHandle during my next test.



No mail appears to be lost, and no errors appear in the maillog while
message_size_limit is in effect, but the message doesn't pass to my
anti-spam daemon via content_filter.


It could be that the anti-spam daemon announces a LOWER size limit in
the EHLO greeting:

and thus Postfix won't even try to send



Once postfix is restarted with the message_size_limit parameter removed, 
the mail which was previously accepted and queued by postfix is 
delivered. Ergo, the content filter wouldn't be blocking the file, 
because the content filter configuration doesn't change.


Also, the content filter doesn't announce a SIZE:

$ telnet localhost 10025
Trying ::1...
Connected to localhost.
Escape character is '^]'.
220 mppd
>



When I remove the message_size_limit parameter from main.cf and
reload postfix, all mail that was not delivered does get delivered -
including messages with attachments larger than 10MB.


That makes no sense, since the limit is


I suspect that the test message which is >10MB gets accepted into the 
first queue in the stack, then whatever the problem is causes the 
message to stay there.


Subsequently, when postfix is restarted with the message_size_limit 
parameter removed from main.cf, the problem causing the messages not to 
flow any further through the queues is removed - thus allowing the test 
message >10MB to continue through the mail flow (since the message was 
already waiting in a queue past the point that the 250-SIZE in the SMTP 
conversation would block the message).




$ postconf -d message_size_limit
message_size_limit = 1024

Show postconf -n output and your master.cf


Attached as text.

Thanks for taking the time to reply.

 - Nick Bright
smtpinetn   -   n   -   200 smtpd
-o content_filter=
submission inet n   -   n   -   200 smtpd
-o content_filter=
smtps inet  n   -   n   -   200   smtpd
  -o smtpd_tls_wrappermode=yes
  -o smtpd_sasl_auth_enable=yes
  -o milter_macro_daemon_name=ORIGINATING
  -o content_filter=
pickupfifo  n   -   n   60  1   pickup
cleanup   unix  n   -   n   -   0   cleanup
qmgr  fifo  n   -   n   300 1   qmgr
tlsmgrunix  -   -   n   1000?   1   tlsmgr
rewrite   unix  -   -   n   -   -   trivial-rewrite
bounceunix  -   -   n   -   0   bounce
defer unix  -   -   n   -   0   bounce
trace unix  -   -   n   -   0   bounce
verifyunix  -   -   n   -   1   verify
flush unix  n   -   n   1000?   0   flush
proxymap  unix  -   -   n   -   -   proxymap
proxywrite unix -   -   n   -   1   proxymap
smtp  unix  -   -   n   -   -   smtp
relay unix  -   -   n   -   -   smtp
-o smtp_fallback_relay=
showq unix  n   -   n   -   -   showq
error unix  -   -   n   -   -   error
retry unix  -   -   n   -   -   error
discard   unix  -   -   n   -   -   discard
local unix  -   n   n   -   -   local
virtual   unix  -   n   n   -   -   virtual
lmtp  unix  -   -   n   -   -   lmtp
anvil unix  -   -   n   -   1   anvil
scacheunix  -   -   n   -   1   scache
localhost:10026 inetn   -   n   -   50  smtpd
-o content_filter=
-o local_recipient_maps=
-o relay_recipient_maps=
-o myhostname=localhost.domain.tld
-o smtpd_helo_restrictions=
-o smtpd_client_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o mynetworks=127.0.0.0/8
-o smtpd_data_restrictions=
-o smtpd_end_of_data_restrictions=
-o smtpd_authorized_xforward_hosts=127.0.0.0/8

mppscan unix-   -   n   -   50  lmtp
-o lmtp_send_xforward_command=yes
-o lmtp_cache_connection=noalias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfi

Re: message_size_limit causes postfix to stop delivering messages

2012-02-05 Thread Wietse Venema
Nick Bright:
> On 2/4/2012 12:20 PM, Ralf Hildebrandt wrote:
> > * Nick Bright:
> >
> >> Upon restarting postfix with message_size_limit in place it simply
> >> wouldn't deliver any mail. It accepts the mail in to SMTP just fine,
> >> but it never gets delivered.
> >
> > Logs?
> >
> 
> There are no log entries other than normal entries reflecting that the 
> messages have been accepted for delivery, though per another posters' 
> recommendation; I will enable debug logging and give it another look. I 
> also installed postfix-perl-utils and will examine which queue the 
> messages are piling up in with pfHandle during my next test.

Postfix logs all attempts to deliver mail, whether
or not successful.

Please do not turn on debug logging, it will just make
the problem harder to diagnose.

You probably have a bug in the VDA patch that breaks
when the message size limit exceeds the mailbox size
limit. Their code does not handle that correctly.

Wietse


Re: message_size_limit causes postfix to stop delivering messages

2012-02-05 Thread Tomas Macek

On Sun, 5 Feb 2012, Wietse Venema wrote:


Nick Bright:

On 2/4/2012 12:20 PM, Ralf Hildebrandt wrote:

* Nick Bright:


Upon restarting postfix with message_size_limit in place it simply
wouldn't deliver any mail. It accepts the mail in to SMTP just fine,
but it never gets delivered.


Logs?



There are no log entries other than normal entries reflecting that the
messages have been accepted for delivery, though per another posters'
recommendation; I will enable debug logging and give it another look. I
also installed postfix-perl-utils and will examine which queue the
messages are piling up in with pfHandle during my next test.


Postfix logs all attempts to deliver mail, whether
or not successful.

Please do not turn on debug logging, it will just make
the problem harder to diagnose.

You probably have a bug in the VDA patch that breaks
when the message size limit exceeds the mailbox size
limit. Their code does not handle that correctly.

Wietse



What should be a proper behaviour in this case?
If the patched virtual 
agent gets from the queue the message, that exceeds the mailbox size 
limit, it can only bounce or drop the message. It does something else? Or 
what's bad?


Tomas