Re: Postfix Access Problem Procmail
On Wed, Apr 02, 2008 at 06:13:20PM -0400, Thomas H. George wrote:
Chis,
I have attached the output of postconf -n and the contents of muttrc
and master.cf. I really appreciate the help and did not mean to be
unresponsive. I just felt obligated to keep trying to work things out
myself.
Fine. Did you do a dpkg-reconfigure postfix?
What settings did you choose?
What errors are you seeing in the logs?
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
delay_warning_time = 1h
inet_interfaces = all
mailbox_command = procmail -a $EXTENSION
So you are using procmail?
mailbox_size_limit = 0
mydestination = tomgeorge.info, Phoenix.Zoo, localhost.Zoo, localhost
myhostname = Phoenix.Zoo
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost =
Why is relayhost empty? Can you explain tomgeorge.info and
Phoenix.Zoo?
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_client_restrictions = check_client_access hash:/etc/postfix/access
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtpd_use_tls = yes
This is a bare .muttrc. If you are using procmail, you will need to tell
mutt where the mail is delivered: look at the mutt documentation, either
press F1 from within mutt, or start here:
/usr/share/doc/mutt/html/gettingstarted.html
Particularly, the set folder and mailboxes commands.
set use_from=yes
set [EMAIL PROTECTED]
#my_hdr From: Thomas H. George [EMAIL PROTECTED]
hdr_order date from subject to cc
lists debian-user@lists.debian.org
I don't know anything about TLS, but in your main.cf you have
smtpd_use_tls = yes but in your master.cf the options for tls are
commented out, is that ok?
# Postfix master process configuration file. For details on the format
# of the file, see the master(5) manual page (command: man 5 master).
#
# Do not forget to execute postfix reload after editing this file.
#
# ==
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==
smtp inet n - - - - smtpd
#submission inet n - - - - smtpd
# -o smtpd_tls_security_level=encrypt
# -o smtpd_sasl_auth_enable=yes
# -o smtpd_client_restrictions=permit_sasl_authenticated,reject
# -o milter_macro_daemon_name=ORIGINATING
#smtps inet n - - - - smtpd
# -o smtpd_tls_wrappermode=yes
# -o smtpd_sasl_auth_enable=yes
# -o smtpd_client_restrictions=permit_sasl_authenticated,reject
# -o milter_macro_daemon_name=ORIGINATING
#628 inet n - - - - qmqpd
pickupfifo n - - 60 1 pickup
cleanup unix n - - - 0 cleanup
qmgr fifo n - n 300 1 qmgr
#qmgr fifo n - - 300 1 oqmgr
tlsmgrunix - - - 1000? 1 tlsmgr
rewrite unix - - - - - trivial-rewrite
bounceunix - - - - 0 bounce
defer unix - - - - 0 bounce
trace unix - - - - 0 bounce
verifyunix - - - - 1 verify
flush unix n - - 1000? 0 flush
proxymap unix - - n - - proxymap
proxywrite unix - - n - 1 proxymap
smtp unix - - - - - smtp
# When relaying mail as backup MX, disable fallback_relay to avoid MX loops
relay unix - - - - - smtp
-o smtp_fallback_relay=
# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix n - - - - showq
error unix - - - - - error
retry unix - - - - - error
discard unix - - - - - discard
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - - - - lmtp
anvil unix - - - - 1 anvil
scacheunix - - - - 1 scache
#
#
# Interfaces to non-Postfix software. Be sure to examine
Re: Postfix Access Problem Procmail
Ok, its probably a procmail problem. procmail is installed but there is no procmailrc (and I don't believe there was one on the other computer either ). I have never created a procmailrc. I have started reading the man page and the examples. A lot of neat stuff mostly dealing with incoming mail and mostly dealing with more complex setups. I'll try a basic procmailrc and see what happens. Incidently right now I have a tangle. Postings to the users' list are retrieved by fetchmail and I read them with mutt but I can't post replies from mutt. I still must post from iceape and am unable to link my postings to others' replies, only to my original posting. Tom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Postfix Access Problem Procmail
On Wed April 2 2008 06:50:32 Thomas H. George wrote: Ok, its probably a procmail problem. procmail is installed but there is no procmailrc (and I don't believe there was one on the other computer either ). I have never created a procmailrc. I have started reading the man page and the examples. A lot of neat stuff mostly dealing with incoming mail and mostly dealing with more complex setups. I'll try a basic procmailrc and see what happens. Incidently right now I have a tangle. Postings to the users' list are retrieved by fetchmail and I read them with mutt but I can't post replies from mutt. I still must post from iceape and am unable to link my postings to others' replies, only to my original posting. Tom, It's time to take a step back and decide what you want your mail system to do and then design an implementation that will do it. I don't think chasing wierd behavior will get you from here to there. I suspect you copied and pasted some complex Postfix configuration when something simpler would have served you better. But just in case I'm wrong, why not tell Postfix not to use Procmail? --Mike Bird -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Postfix Access Problem Procmail
On Wed, Apr 02, 2008 at 09:50:32AM -0400, Thomas H. George wrote: Ok, its probably a procmail problem. procmail is installed but there is no procmailrc (and I don't believe there was one on the other computer either ). Waste of time installing procmail without one. :-) I have never created a procmailrc. I have started reading the man page and the examples. A lot of neat stuff mostly dealing with incoming mail and mostly dealing with more complex setups. I'll try a basic procmailrc and see what happens. Incidently right now I have a tangle. Postings to the users' list are retrieved by fetchmail and I read them with mutt but I can't post replies from mutt. I still must post from iceape and am unable to link my postings to others' replies, only to my original posting. iceape and mutt store mail in different locations, so unless you set up imap mixing mutt and iceape will only add to the problems. Can you *please* post the contents of your .muttrc? Also as root, can you *please* post the output of: postconf -n Without that information its like the blind man looking for the black cat in a dark room which isn't there. -- Rowan Atkinson So please, please, please, help us so that we can help you. -- Chris. == -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Postfix Access Problem Procmail
Chis,
I have attached the output of postconf -n and the contents of muttrc
and master.cf. I really appreciate the help and did not mean to be
unresponsive. I just felt obligated to keep trying to work things out
myself.
Tom
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
delay_warning_time = 1h
inet_interfaces = all
mailbox_command = procmail -a $EXTENSION
mailbox_size_limit = 0
mydestination = tomgeorge.info, Phoenix.Zoo, localhost.Zoo, localhost
myhostname = Phoenix.Zoo
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
myorigin = /etc/mailname
readme_directory = no
recipient_delimiter = +
relayhost =
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
smtpd_client_restrictions = check_client_access hash:/etc/postfix/access
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtpd_use_tls = yes
set use_from=yes
set [EMAIL PROTECTED]
#my_hdr From: Thomas H. George [EMAIL PROTECTED]
hdr_order date from subject to cc
lists debian-user@lists.debian.org
#
# Postfix master process configuration file. For details on the format
# of the file, see the master(5) manual page (command: man 5 master).
#
# Do not forget to execute postfix reload after editing this file.
#
# ==
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==
smtp inet n - - - - smtpd
#submission inet n - - - - smtpd
# -o smtpd_tls_security_level=encrypt
# -o smtpd_sasl_auth_enable=yes
# -o smtpd_client_restrictions=permit_sasl_authenticated,reject
# -o milter_macro_daemon_name=ORIGINATING
#smtps inet n - - - - smtpd
# -o smtpd_tls_wrappermode=yes
# -o smtpd_sasl_auth_enable=yes
# -o smtpd_client_restrictions=permit_sasl_authenticated,reject
# -o milter_macro_daemon_name=ORIGINATING
#628 inet n - - - - qmqpd
pickupfifo n - - 60 1 pickup
cleanup unix n - - - 0 cleanup
qmgr fifo n - n 300 1 qmgr
#qmgr fifo n - - 300 1 oqmgr
tlsmgrunix - - - 1000? 1 tlsmgr
rewrite unix - - - - - trivial-rewrite
bounceunix - - - - 0 bounce
defer unix - - - - 0 bounce
trace unix - - - - 0 bounce
verifyunix - - - - 1 verify
flush unix n - - 1000? 0 flush
proxymap unix - - n - - proxymap
proxywrite unix - - n - 1 proxymap
smtp unix - - - - - smtp
# When relaying mail as backup MX, disable fallback_relay to avoid MX loops
relay unix - - - - - smtp
-o smtp_fallback_relay=
# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix n - - - - showq
error unix - - - - - error
retry unix - - - - - error
discard unix - - - - - discard
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - - - - lmtp
anvil unix - - - - 1 anvil
scacheunix - - - - 1 scache
#
#
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# Many of the following services use the Postfix pipe(8) delivery
# agent. See the pipe(8) man page for information about ${recipient}
# and other message envelope options.
#
#
# maildrop. See the Postfix MAILDROP_README file for details.
# Also specify in main.cf: maildrop_destination_recipient_limit=1
#
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/bin/maildrop -d ${recipient}
#
# See the Postfix UUCP_README file for configuration details.
#
uucp unix - n n - - pipe
flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
#
# Other
