The "require_home_directory = yes" setting for local mail delivery
takes effect only for users in the UNIX passwd database.

If this setting causes problems for your windoze users, then you
have a weird system setup and need to explain more about what is
going on, before this mystery can be resolved.

        Wietse

Matt Soccio:
> I asked about this problem last week, and Ralph was kind enough to respond
> that it may have been NFS issues. I tried the flag that required home
> directories, but I have a significant number of windows users that only
> pop in and do not have shell accounts, and this created too many problems.
>
> I have a user with a .forward that works for all internal tests, internal
> lists, etc., but when he gets mail from an exteral list (like this one),
> the .forward seems to be skipped and his mail is delivered locally. I was
> willing to dismiss this as an odd NFS snafu, until I saw the logs from the
> mail that was delivered locally yesterday. An external mail list sent
> data to 10 people in our department, 2 of these folks have .forward files,
> the one with a procmail pointer worked, while the one with a forwarding
> address was locally delivered. I don't see ANY logs about nfs servers not
> responding, let alone ones that coincide with this mail. Is it possible
> for majordomo mailings to somehow force local delivery? I have looked at
> the headers of the mail and don't see anything fishy. Is there some way
> that I can test if the .forward file is actually being read? Are there
> any circumstances where it would be ignored?
>
> Below is postconf -n. I'll send the logs and mail headers off list if you
> want to have a gander.
>
> Any help is appreciated.
>
> Matt
>
> alias_database = hash:/etc/mail/aliases
> alias_maps = hash:/etc/mail/aliases
> biff = no
> body_checks = regexp:/etc/postfix/body_checks
> command_directory = /usr/sbin
> config_directory = /etc/postfix
> daemon_directory = /usr/libexec/postfix
> debug_peer_level = 2
> header_checks = regexp:/etc/postfix/header_checks
> ignore_mx_lookup_error = yes
> mail_owner = postfix
> mail_spool_directory = /var/mail
> mailbox_size_limit = 256000000
> mailq_path = /usr/bin/mailq
> manpage_directory = /usr/man
> maps_rbl_domains = relays.ordb.org
> maps_rbl_reject_code = 550
> masquerade_domains = $mydomain
> masquerade_exceptions = root
> message_size_limit = 20480000
> mydestination = $myhostname localhost.$mydomain $mydomain
> /etc/mail/mailhosts
> mydomain = astro.psu.edu
> myhostname = lonestar.astro.psu.edu
> mynetworks_style = subnet
> myorigin = $mydomain
> newaliases_path = /usr/bin/newaliases
> notify_classes = resource, software, delay
> queue_directory = /var/spool/postfix
> queue_minfree = 20480000
> readme_directory = /export/bulk/ripple/postfix-1.1.5/
> relay_domains = $mydomain swift.psu.edu
> sample_directory = /etc/postfix
> sendmail_path = /usr/lib/sendmail
> setgid_group = postdrop
> smtpd_banner = $myhostname ESMTP $mail_name
> smtpd_recipient_limit = 450
> smtpd_recipient_restrictions = reject_non_fqdn_sender,
> reject_unknown_sender_domain, permit_mynetworks,
> reject_unauth_destination, reject_unauth_pipelining,
> reject_invalid_hostname, reject_maps_rbl, permit
>
>
> -
> To unsubscribe, send mail to majordomopostfix.org with content
> (not subject): unsubscribe postfix-users
>
>

-
To unsubscribe, send mail to majordomopostfix.org with content
(not subject): unsubscribe postfix-users

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]