No messages delivered to INBOX

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

No messages delivered to INBOX

Rich Shepard
   Running postfix-3.2.4 on Slackware-14.2. My server and workstation are on
the same host. Yesterday, about mid-day, messages to me stopped being
delivered to my INBOX. /var/spool/mail shows:

-rw-rw---- 1 rshepard mail 207100 Jan 15 12:30 /var/spool/mail/rshepard

   Messages from mail lists are directed by procmail's recipes.rc to the
proper file in ~/mail/. I've temporarily directed all incoming messages
directed to me at my business domain (same as used to send this message) to
the file for messages sent to my personal domain.

   Yesterday morning I added a couple of domains to rhsbl_sender_exceptions
and postgrey_whitelist_clients and processed the changed files with postmap.
These are the only changes I've made in /etc/postfix/.

   Stopping and restarting postfix does not fix this issue, and I noticed the
problem only this morning when I logged in and found no log reports or spam
that the filters missed.

   In the 20+ years I've run postfix this has not before happened and I've no
idea how to identify the source of the issue. Please advise me on how I can
find the problem.

TIA,

Rich

Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Noel Jones-2
On 1/16/2018 9:50 AM, Rich Shepard wrote:

>   Running postfix-3.2.4 on Slackware-14.2. My server and workstation
> are on
> the same host. Yesterday, about mid-day, messages to me stopped being
> delivered to my INBOX. /var/spool/mail shows:
>
> -rw-rw---- 1 rshepard mail 207100 Jan 15 12:30 /var/spool/mail/rshepard
>
>   Messages from mail lists are directed by procmail's recipes.rc to the
> proper file in ~/mail/. I've temporarily directed all incoming messages
> directed to me at my business domain (same as used to send this
> message) to
> the file for messages sent to my personal domain.
>
>   Yesterday morning I added a couple of domains to
> rhsbl_sender_exceptions
> and postgrey_whitelist_clients and processed the changed files with
> postmap.
> These are the only changes I've made in /etc/postfix/.
>
>   Stopping and restarting postfix does not fix this issue, and I
> noticed the
> problem only this morning when I logged in and found no log reports
> or spam
> that the filters missed.
>
>   In the 20+ years I've run postfix this has not before happened and
> I've no
> idea how to identify the source of the issue. Please advise me on
> how I can
> find the problem.
>
> TIA,
>
> Rich
>


Pick one message and follow it through the logs.  If postfix fails
or misdirects the message, postfix will log what happened.  If the
message makes it through postfix and is handed off to procmail, then
that's where the problem is.




  -- Noel Jones
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Rich Shepard
On Tue, 16 Jan 2018, Noel Jones wrote:

> Pick one message and follow it through the logs. If postfix fails or
> misdirects the message, postfix will log what happened. If the message
> makes it through postfix and is handed off to procmail, then that's where
> the problem is.

Noel,

   Aw, I should have looked at the log, but looked everywhere but there. My
apologies.

   I sent a test message from my personal account. This is what maillog
shows:

Jan 16 05:54:55 salmo postfix/smtpd[23648]: connect from salmo.appl-ecosys.com[192.168.55.1]
Jan 16 05:54:55 salmo postfix/smtpd[23648]: warning: connect to Milter service inet:127.0.0.1:8891: Connection refused
Jan 16 05:54:55 salmo postfix/smtpd[23648]: 0689799232: client=salmo.appl-ecosys.com[192.168.55.1]
Jan 16 05:54:55 salmo postfix/cleanup[23650]: 0689799232: message-id=<[hidden email]>
Jan 16 05:54:55 salmo postfix/qmgr[14668]: 0689799232: from=<[hidden email]>, size=661, nrcpt=1 (queue active)
Jan 16 05:54:55 salmo postfix/smtpd[23648]: disconnect from salmo.appl-ecosys.com[192.168.55.1] ehlo=1 mail=1 rcpt=1 data=1 quit=1 commands=5
Jan 16 05:54:57 salmo postfix/local[23651]: 0689799232: to=<[hidden email]>, orig_to=<[hidden email]>, relay=local, delay=2.4, delays=0.14/0.02/0/2.2, dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail)
Jan 16 05:54:57 salmo postfix/qmgr[14668]: 0689799232: removed

   So it looks like it was passed to procmail but not delivered to my inbox.
Now I need to figure out why since the only changes to the recipes were the
addition of two rules for two mail lists.

Thanks,

Rich
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Noel Jones-2
On 1/16/2018 10:32 AM, Rich Shepard wrote:

> Jan 16 05:54:55 salmo postfix/smtpd[23648]: warning: connect to
> Milter service inet:127.0.0.1:8891: Connection refused

This probably isn't related to your delivery problems, but whatever
miler you've configured at :8891 isn't running.  Most likely the
service is down.

...

> Jan 16 05:54:57 salmo postfix/local[23651]: 0689799232:
> to=<[hidden email]>, orig_to=<[hidden email]>,
> relay=local, delay=2.4, delays=0.14/0.02/0/2.2, dsn=2.0.0,
> status=sent (delivered to command: /usr/bin/procmail)
> Jan 16 05:54:57 salmo postfix/qmgr[14668]: 0689799232: removed
>
>   So it looks like it was passed to procmail but not delivered to my
> inbox.
> Now I need to figure out why since the only changes to the recipes
> were the
> addition of two rules for two mail lists.
>

Yes. Sorry, I've never used procmail, so can't really help with
that.  Does procmail provide logging?

If you post your procmail recipe here, someone else may be able to help.




  -- Noel Jones
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Rich Shepard
On Tue, 16 Jan 2018, Noel Jones wrote:

> This probably isn't related to your delivery problems, but whatever miler
> you've configured at :8891 isn't running. Most likely the service is down.

Noel,

   That was added by me last November as I added SPF and openDKIM to postfix.
The latter starts and appears to work but verifier.port25.com does not see
it. Anyway, I had to reboot this host last week and forgot that opendkim
does not start upon boot up even though it should. I just started it.

> Yes. Sorry, I've never used procmail, so can't really help with that. Does
> procmail provide logging? If you post your procmail recipe here, someone
> else may be able to help.

    Here is the log entries from a test message sent recently to
[hidden email]:

procmail: Unlocking "personal.lock"
>From [hidden email]  Tue Jan 16 08:50:05 2018
   Subject: test
    Folder: personal   1039
procmail: [27159] Tue Jan 16 08:50:08 2018
procmail: Assigning "LOGABSTRACT=all"
procmail: Assigning "MAILDIR=/home/rshepard/mail"
procmail: Assigning "PMDIR=/home/rshepard/procmail"
procmail: Assigning "DEFAULT=/var/spool/mail/rshepard"
procmail: Assigning "ORGMAIL=/var/spool/mail/rshepard"
procmail: Assigning "COMSAT=no"
procmail: Assigning "COMSAT=no"
procmail: Assigning "LOGFILE=/home/rshepard/procmail/log"
procmail: Opening "/home/rshepard/procmail/log"
procmail: Assigning "INCLUDERC=/home/rshepard/procmail/recipes.rc"
procmail: Match on "< 256000"
procmail: Locking "spamassassin.lock"
procmail: Executing "spamassassin"
procmail: [27159] Tue Jan 16 08:50:10 2018
procmail: Unlocking "spamassassin.lock"
procmail: No match on "^X-Spam-Status: Yes"
procmail: No match on "^Subject: *****SPAM*****"
procmail: No match on "(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?).*[hidden email]"
procmail: No match on "(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?).*@appl-ecosys.com"
procmail: No match on "(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?).*@appl-ecosys.com"

    Procmail then looks at each recipe for the mail lists and finds no
matches.

    Nothing's changed here from before mail stopped being sent to the default
file. Now I need to find why it sees the default but is not passing mail
there.

Rich
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Matus UHLAR - fantomas
On 16.01.18 13:21, Rich Shepard wrote:

>   Here is the log entries from a test message sent recently to
>[hidden email]:
>
>procmail: Unlocking "personal.lock"
>>From [hidden email]  Tue Jan 16 08:50:05 2018
>  Subject: test
>   Folder: personal   1039
>procmail: [27159] Tue Jan 16 08:50:08 2018
>procmail: Assigning "LOGABSTRACT=all"
>procmail: Assigning "MAILDIR=/home/rshepard/mail"
>procmail: Assigning "PMDIR=/home/rshepard/procmail"
>procmail: Assigning "DEFAULT=/var/spool/mail/rshepard"
>procmail: Assigning "ORGMAIL=/var/spool/mail/rshepard"
>procmail: Assigning "COMSAT=no"
>procmail: Assigning "COMSAT=no"
>procmail: Assigning "LOGFILE=/home/rshepard/procmail/log"
>procmail: Opening "/home/rshepard/procmail/log"
>procmail: Assigning "INCLUDERC=/home/rshepard/procmail/recipes.rc"
>procmail: Match on "< 256000"
>procmail: Locking "spamassassin.lock"
>procmail: Executing "spamassassin"
>procmail: [27159] Tue Jan 16 08:50:10 2018
>procmail: Unlocking "spamassassin.lock"
>procmail: No match on "^X-Spam-Status: Yes"
>procmail: No match on "^Subject: *****SPAM*****"
>procmail: No match on "(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?).*[hidden email]"
>procmail: No match on "(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?).*@appl-ecosys.com"
>procmail: No match on "(^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope|Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?).*@appl-ecosys.com"
>
>   Procmail then looks at each recipe for the mail lists and finds no
>matches.

>   Nothing's changed here from before mail stopped being sent to the default
>file. Now I need to find why it sees the default but is not passing mail
>there.

what's in the /home/rshepard/procmail/log ?


--
Matus UHLAR - fantomas, [hidden email] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The 3 biggets disasters: Hiroshima 45, Tschernobyl 86, Windows 95
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Rich Shepard
On Wed, 17 Jan 2018, Matus UHLAR - fantomas wrote:

> what's in the /home/rshepard/procmail/log ?

Matus,

   That is what I sent in the message: the log content for that specific
test message not delivered to my inbox. I deleted the lines showing procmail
testing for matches to mail list addresses.

   If I mis-understand your question let me know what additional information
I can provide and I will send it.

Thanks,

Rich
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Matus UHLAR - fantomas
>On Wed, 17 Jan 2018, Matus UHLAR - fantomas wrote:
>>what's in the /home/rshepard/procmail/log ?


On 17.01.18 05:41, Rich Shepard wrote:
>  That is what I sent in the message: the log content for that specific
>test message not delivered to my inbox. I deleted the lines showing procmail
>testing for matches to mail list addresses.
>
>  If I mis-understand your question let me know what additional information
>I can provide and I will send it.

on some systems I maintain there was "VERBOSE=yes" and procmail logged path
to the created file within maildir.
try setting VERBOSE=yes at the begin of your procmail rc file.

--
Matus UHLAR - fantomas, [hidden email] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux IS user friendly, it's just selective who its friends are...
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX

Rich Shepard
On Wed, 17 Jan 2018, Matus UHLAR - fantomas wrote:

> on some systems I maintain there was "VERBOSE=yes" and procmail logged
> path to the created file within maildir. try setting VERBOSE=yes at the
> begin of your procmail rc file.

Matus,

   Thanks for clarifying. Here is ~/.procmailrc:

LOGFILE=/home/rshepard/procmail/log
# set to yes when debugging
VERBOSE=yes

# Remove ## when debugging; set to no if you want minimal logging; to all
# for max.
LOGABSTRACT=all

MAILDIR=$HOME/mail

# Directory for storing procmail-related files
PMDIR=$HOME/procmail

#diagnostic:
DEFAULT=/var/spool/mail/rshepard
ORGMAIL=/var/spool/mail/rshepard

# Turn off notification of mail received
COMSAT=no

# Put ## before LOGFILE if no logging is wanted (not recommended)
LOGFILE=$PMDIR/log
## INCLUDERC=$PMDIR/testing.rc
## INCLUDERC=$PMDIR/lists.rc
INCLUDERC=$PMDIR/recipes.rc

# Catch SPAM
#:0
#* ^X-Spam-Flag: YES
#* ^X-Spam-Level: \*\*\*\*\*\*
#/dev/null
#EOF
Reply | Threaded
Open this post in threaded view
|

Re: No messages delivered to INBOX [RESOLVED]

Rich Shepard
In reply to this post by Rich Shepard
On Tue, 16 Jan 2018, Rich Shepard wrote:

> Running postfix-3.2.4 on Slackware-14.2. My server and workstation are on
> the same host. Yesterday, about mid-day, messages to me stopped being
> delivered to my INBOX. /var/spool/mail shows:

   Earlier today I added another recipe to ~/procmail/recipes.rc:

:0:
* ^TO_.*@appl-ecosys.com
$DEFAULT

which duplicates procmail's default behavior. I made no difference when I
sent a test message from my personal domain. However, ...

   I just upgraded the kernel to 4.4.111 and rebooted the system. With the
new recipe test messages from my personal domain are now put into
/var/spool/mail/rshepard which is alpine's INBOX. Messages sent with that
new recipe commented out are not delivered anywhere. Strange, but I can live
with the new recipe because it works.

Thanks to all,

Rich