Postfix 2.3.3 - 504: queue file write error

View: New views
3 Messages — Rating Filter:   Alert me  

Postfix 2.3.3 - 504: queue file write error

by Patrick Vale :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hello,

I run a centos 5.2 Xen VPS running Postfix 2.3.3

It threw the 'queue file write error' when sending a message through webmail (usermin 1.420). The message headers follow.

From: "Aaaaa Aaaaa" <aaaaa@...>
Subject: Aaaaaaa aaaaaaa aaaaaaa
To: aaaaaaaa@...
Cc: aaaaaaa@...
Bcc:
Message-Id: <1257337775.3608@...>
X-Originating-IP: 86.141.247.199
X-Mailer: Usermin 1.420
Date: Wed, 04 Nov 2009 12:29:35 +0000 (GMT)
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="bound1257337777"

It had multiple attachments:

JPEG Image 743.84 kB
JPEG Image 977.07 kB
JPEG Image 1.45 MB
JPEG Image 1.44 MB
JPEG Image 1.47 MB
JPEG Image 1.41 MB

The maillog showed up:

Nov  4 12:29:36 vm2884 postfix/postdrop[3671]: warning: uid=504: Illegal seek
Nov  4 12:29:36 vm2884 postfix/sendmail[3670]: fatal: aaaaaa@...(504): queue file write error

UID 504 is the UID of the user logged in to webmail.

Searching the archives it appears this is usually due to a message being larger than the max_message_size, which is set at 10240000.

Thank you.

Postconf output follows

> postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
home_mailbox = Maildir/
html_directory = no
inet_interfaces = all
mail_owner = postfix
mailbox_command = /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
mydestination = $myhostname, localhost.$mydomain, localhost, vm2884.vps.tagadab.com
newaliases_path = /usr/bin/newaliases.postfix
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/postfix-2.3.3/README_FILES
sample_directory = /usr/share/doc/postfix-2.3.3/samples
sender_bcc_maps = hash:/etc/postfix/bcc
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination check_policy_service unix:/var/spool/postfix/postgrey/socket
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 550
virtual_alias_maps = hash:/etc/postfix/virtual

Re: Postfix 2.3.3 - 504: queue file write error

by Simon Waters :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Friday 06 November 2009 11:47:36 Patrick Vale wrote:
> Illegal seek

Google suggests

http://www.cyberciti.biz/tips/linux-unix-posttfix-mutt-illegal-seek-error.html

Re: Postfix 2.3.3 - 504: queue file write error

by lst_hoe02 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Zitat von Patrick Vale <patrick@...>:

> Hello,
>
> I run a centos 5.2 Xen VPS running Postfix 2.3.3
>
> It threw the 'queue file write error' when sending a message through  
> webmail (usermin 1.420). The message headers follow.
>
> From: "Aaaaa Aaaaa" <aaaaa@...>
> Subject: Aaaaaaa aaaaaaa aaaaaaa
> To: aaaaaaaa@...
> Cc: aaaaaaa@...
> Bcc:
> Message-Id: <1257337775.3608@...>
> X-Originating-IP: 86.141.247.199
> X-Mailer: Usermin 1.420
> Date: Wed, 04 Nov 2009 12:29:35 +0000 (GMT)
> MIME-Version: 1.0
> Content-Type: multipart/mixed; boundary="bound1257337777"
>
> It had multiple attachments:
>
> JPEG Image 743.84 kB
> JPEG Image 977.07 kB
> JPEG Image 1.45 MB
> JPEG Image 1.44 MB
> JPEG Image 1.47 MB
> JPEG Image 1.41 MB
>
> The maillog showed up:
>
> Nov  4 12:29:36 vm2884 postfix/postdrop[3671]: warning: uid=504: Illegal seek
> Nov  4 12:29:36 vm2884 postfix/sendmail[3670]: fatal:  
> aaaaaa@...(504): queue file write error
>
> UID 504 is the UID of the user logged in to webmail.
>
> Searching the archives it appears this is usually due to a message  
> being larger than the max_message_size, which is set at 10240000.

You have found the error by yourself. You have set around 10MB as  
limit and attach data with around 8MB which get MIME encoded. MIME  
encoding lead to increase in size by about 30%-40% so your message  
will be indeed too big.

Regards

Andreas