Debian - problem related to procmail

recently I started getting an error like that:

This is the mail system at host xxx.

I'm sorry to have to inform you that your message could notbe
delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You candelete your
own text from the attached returned message.

The mail system

: Command time limit exceeded: "procmail -a "$EXTENSION""

This is happening on Debian linux with Postfix installed into it. I have lost ideas where to look for the problems. All of the mails are located in /home folder. I guess it's local maildir.

asked Mar 4 at 19:14

spayk

First step is to do df and see if any partitions are full (close to 95%, because usually 5% is reserved for root). If that's not the problem: Postfix calls procmail to "deliver" the mail to the user, so find out which user that is, and if there's a .procmailrc for this user, look at which additional tasks it does.

– dirkt
Mar 5 at 7:21

Hello @dirkt I have checked everythnig, the space for hard disk is fine. The bounces seem to happen for few last users. For example user A is sending an email with attachements which is around ~500KB to 100 people (he is also adding some with CC and also BCC). For example the list has 100 emails which 90 people is reciving the emails and 10 randomly emails are bounced (status=bounced). So for now I have figured out few things which I may try, but also asking here and if someone may help me.Thank you.

– spayk
Mar 7 at 9:14

If it only happens for emails with sizeable attachments, one obvious guess is that procmail is configured on your systems to do something with those attachments, and it takes too long. Have you enabled logging for procmail?

– dirkt
Mar 7 at 11:05

Hello @dirkt once again and thank you for the answer. Yes I have been able to login to the procmail via webmin to see and check it. Also I have noticed that procmail config is kind of strange and one line of code is confusing me. This "script": :0fw: spamassassin.lock * < 256000 | /usr/bin/spamc the question is, is my instict of bouncing status right and if I should change the 256000 kb for higher value or lower. What do you think, sir?

– spayk
Mar 8 at 7:18

See man procmailrc and man procmailex for details. Line breaks are significant, but that line probably means "let spamassassin inspect all mails of size less than 256K'. It's possible that spamassassin needs to inspect all mails to deliver them, but I'd have to see the complete script to judge that'. It's also possible there's a problem with lockfiles held, which cause the timeout.

– dirkt
Mar 8 at 8:46

|
show 2 more comments

recently I started getting an error like that:

This is the mail system at host xxx.

I'm sorry to have to inform you that your message could notbe
delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You candelete your
own text from the attached returned message.

The mail system

: Command time limit exceeded: "procmail -a "$EXTENSION""

This is happening on Debian linux with Postfix installed into it. I have lost ideas where to look for the problems. All of the mails are located in /home folder. I guess it's local maildir.

asked Mar 4 at 19:14

spayk

First step is to do df and see if any partitions are full (close to 95%, because usually 5% is reserved for root). If that's not the problem: Postfix calls procmail to "deliver" the mail to the user, so find out which user that is, and if there's a .procmailrc for this user, look at which additional tasks it does.

– dirkt
Mar 5 at 7:21

Hello @dirkt I have checked everythnig, the space for hard disk is fine. The bounces seem to happen for few last users. For example user A is sending an email with attachements which is around ~500KB to 100 people (he is also adding some with CC and also BCC). For example the list has 100 emails which 90 people is reciving the emails and 10 randomly emails are bounced (status=bounced). So for now I have figured out few things which I may try, but also asking here and if someone may help me.Thank you.

– spayk
Mar 7 at 9:14

If it only happens for emails with sizeable attachments, one obvious guess is that procmail is configured on your systems to do something with those attachments, and it takes too long. Have you enabled logging for procmail?

– dirkt
Mar 7 at 11:05

Hello @dirkt once again and thank you for the answer. Yes I have been able to login to the procmail via webmin to see and check it. Also I have noticed that procmail config is kind of strange and one line of code is confusing me. This "script": :0fw: spamassassin.lock * < 256000 | /usr/bin/spamc the question is, is my instict of bouncing status right and if I should change the 256000 kb for higher value or lower. What do you think, sir?

– spayk
Mar 8 at 7:18

See man procmailrc and man procmailex for details. Line breaks are significant, but that line probably means "let spamassassin inspect all mails of size less than 256K'. It's possible that spamassassin needs to inspect all mails to deliver them, but I'd have to see the complete script to judge that'. It's also possible there's a problem with lockfiles held, which cause the timeout.

– dirkt
Mar 8 at 8:46

|
show 2 more comments

recently I started getting an error like that:

This is the mail system at host xxx.

I'm sorry to have to inform you that your message could notbe
delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You candelete your
own text from the attached returned message.

The mail system

: Command time limit exceeded: "procmail -a "$EXTENSION""

This is happening on Debian linux with Postfix installed into it. I have lost ideas where to look for the problems. All of the mails are located in /home folder. I guess it's local maildir.

asked Mar 4 at 19:14

spayk

recently I started getting an error like that:

This is the mail system at host xxx.

I'm sorry to have to inform you that your message could notbe
delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You candelete your
own text from the attached returned message.

The mail system

: Command time limit exceeded: "procmail -a "$EXTENSION""

This is happening on Debian linux with Postfix installed into it. I have lost ideas where to look for the problems. All of the mails are located in /home folder. I guess it's local maildir.

linux debian postfix

asked Mar 4 at 19:14

spayk

asked Mar 4 at 19:14

spayk

asked Mar 4 at 19:14

spayk

asked Mar 4 at 19:14

spayk

asked Mar 4 at 19:14

spayk

First step is to do df and see if any partitions are full (close to 95%, because usually 5% is reserved for root). If that's not the problem: Postfix calls procmail to "deliver" the mail to the user, so find out which user that is, and if there's a .procmailrc for this user, look at which additional tasks it does.

– dirkt
Mar 5 at 7:21

Hello @dirkt I have checked everythnig, the space for hard disk is fine. The bounces seem to happen for few last users. For example user A is sending an email with attachements which is around ~500KB to 100 people (he is also adding some with CC and also BCC). For example the list has 100 emails which 90 people is reciving the emails and 10 randomly emails are bounced (status=bounced). So for now I have figured out few things which I may try, but also asking here and if someone may help me.Thank you.

– spayk
Mar 7 at 9:14

If it only happens for emails with sizeable attachments, one obvious guess is that procmail is configured on your systems to do something with those attachments, and it takes too long. Have you enabled logging for procmail?

– dirkt
Mar 7 at 11:05

Hello @dirkt once again and thank you for the answer. Yes I have been able to login to the procmail via webmin to see and check it. Also I have noticed that procmail config is kind of strange and one line of code is confusing me. This "script": :0fw: spamassassin.lock * < 256000 | /usr/bin/spamc the question is, is my instict of bouncing status right and if I should change the 256000 kb for higher value or lower. What do you think, sir?

– spayk
Mar 8 at 7:18

See man procmailrc and man procmailex for details. Line breaks are significant, but that line probably means "let spamassassin inspect all mails of size less than 256K'. It's possible that spamassassin needs to inspect all mails to deliver them, but I'd have to see the complete script to judge that'. It's also possible there's a problem with lockfiles held, which cause the timeout.

– dirkt
Mar 8 at 8:46

|
show 2 more comments

First step is to do df and see if any partitions are full (close to 95%, because usually 5% is reserved for root). If that's not the problem: Postfix calls procmail to "deliver" the mail to the user, so find out which user that is, and if there's a .procmailrc for this user, look at which additional tasks it does.

– dirkt
Mar 5 at 7:21

Hello @dirkt I have checked everythnig, the space for hard disk is fine. The bounces seem to happen for few last users. For example user A is sending an email with attachements which is around ~500KB to 100 people (he is also adding some with CC and also BCC). For example the list has 100 emails which 90 people is reciving the emails and 10 randomly emails are bounced (status=bounced). So for now I have figured out few things which I may try, but also asking here and if someone may help me.Thank you.

– spayk
Mar 7 at 9:14

If it only happens for emails with sizeable attachments, one obvious guess is that procmail is configured on your systems to do something with those attachments, and it takes too long. Have you enabled logging for procmail?

– dirkt
Mar 7 at 11:05

Hello @dirkt once again and thank you for the answer. Yes I have been able to login to the procmail via webmin to see and check it. Also I have noticed that procmail config is kind of strange and one line of code is confusing me. This "script": :0fw: spamassassin.lock * < 256000 | /usr/bin/spamc the question is, is my instict of bouncing status right and if I should change the 256000 kb for higher value or lower. What do you think, sir?

– spayk
Mar 8 at 7:18

See man procmailrc and man procmailex for details. Line breaks are significant, but that line probably means "let spamassassin inspect all mails of size less than 256K'. It's possible that spamassassin needs to inspect all mails to deliver them, but I'd have to see the complete script to judge that'. It's also possible there's a problem with lockfiles held, which cause the timeout.

– dirkt
Mar 8 at 8:46

First step is to do df and see if any partitions are full (close to 95%, because usually 5% is reserved for root). If that's not the problem: Postfix calls procmail to "deliver" the mail to the user, so find out which user that is, and if there's a .procmailrc for this user, look at which additional tasks it does.

– dirkt
Mar 5 at 7:21

Hello @dirkt I have checked everythnig, the space for hard disk is fine. The bounces seem to happen for few last users. For example user A is sending an email with attachements which is around ~500KB to 100 people (he is also adding some with CC and also BCC). For example the list has 100 emails which 90 people is reciving the emails and 10 randomly emails are bounced (status=bounced). So for now I have figured out few things which I may try, but also asking here and if someone may help me.Thank you.

– spayk
Mar 7 at 9:14

If it only happens for emails with sizeable attachments, one obvious guess is that procmail is configured on your systems to do something with those attachments, and it takes too long. Have you enabled logging for procmail?

– dirkt
Mar 7 at 11:05

Hello @dirkt once again and thank you for the answer. Yes I have been able to login to the procmail via webmin to see and check it. Also I have noticed that procmail config is kind of strange and one line of code is confusing me. This "script": :0fw: spamassassin.lock * < 256000 | /usr/bin/spamc the question is, is my instict of bouncing status right and if I should change the 256000 kb for higher value or lower. What do you think, sir?

– spayk
Mar 8 at 7:18

See man procmailrc and man procmailex for details. Line breaks are significant, but that line probably means "let spamassassin inspect all mails of size less than 256K'. It's possible that spamassassin needs to inspect all mails to deliver them, but I'd have to see the complete script to judge that'. It's also possible there's a problem with lockfiles held, which cause the timeout.

– dirkt
Mar 8 at 8:46

|
show 2 more comments

0

active

oldest

votes

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f504334%2fdebian-problem-related-to-procmail%23new-answer', 'question_page');

);

Post as a guest

Name

Required, but never shown

0

active

oldest

votes

0

active

oldest

votes

draft saved

draft discarded

Thanks for contributing an answer to Unix & Linux Stack Exchange!

Please be sure to answer the question. Provide details and share your research!

But avoid …

Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.

draft saved

draft discarded

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

搜尋此網誌

mjhjmtu