Sponsored Content
Operating Systems OS X (Apple) fetchmail and postfix mail setup on Snow Leopard - request for guidance Post 302584931 by butterbaerchen on Monday 26th of December 2011 09:15:23 PM
Old 12-26-2011
that is exactly what I want to happen. I read that link just yesterday, thank you for posting it. Now, I have a file: /var/root/.forward
and it says: /dev/null (I have not found a root mailbox so far ... where do I create it and with which permissions etc?)
Smilie
and when I send mail to root from the commandline it gets rewritten to:
root @ mydomain.org and postfix sends it off... and it bounces.
and if I put roadie (my username) into that /var/root/.forward file instead of /dev/null - it gets rewritten to roadie @ mydomain.org - and, since that mail account actually exists on the server, - I do get the mail - but from fetchmail - not what I want - the mail should not leave the machine. Smilie

in the article it says to put username@localhost into roots .forward file. good, makes sense but still gets rewritten and sent out. I am reading on how mailqueue and local delivery actually works - but I am slow. Have not found a thread so far that tells how someone set it up in words I understand. What am I missing? ... is it the local_recipient_map in postfix and the postmap command? I get confused with virtual, forward, aliases and all of that.
to me it looks as if roadie and roadie @ domain.org are 2 different identities to postfix - where do I glue them together so that they share the /var/mail/roadie inbox file and local mail arrives direct and not via the mailserver of my hosting company? thank you for giving your time. I am learning heaps btw - great undertaking.

Last edited by butterbaerchen; 12-26-2011 at 10:19 PM.. Reason: flatten email address
 

4 More Discussions You Might Find Interesting

1. OS X (Apple)

MacPorts on Snow Leopard

Hello everyone. I was previously using MacPorts 1.8 on Mac OS 10.5.8 without any problems and everything was working well. I recently upgraded to Xcode 3.2 and Mac OS 10.6, since then my MacPorts installation has not been working at all. I deleted it and then reinstalled the .dmg from the... (1 Reply)
Discussion started by: HoldenCaulfield
1 Replies

2. OS X (Apple)

Alpine 2 on Snow Leopard

I've just installed Alpine on Snow Leopard but can't seem to get a default spell checker configured for it. What happened to spell? I can't find it at all on 10.6, must have been some changes. Does anyone know about the default unix spell checker on SL? Thanks! (0 Replies)
Discussion started by: platz
0 Replies

3. OS X (Apple)

Installing Oracle 10g on Snow Leopard using this tutorial

This tutorial. Which is a lovely tutorial, really, and was working up until this instruction: Now download db.zip installation archive and place it somewhere and unzip it: mkdir Install cd Install # download db.zip to this directory unzip db.zip cd db/Disk1 I didn't know how to... (1 Reply)
Discussion started by: khayraB
1 Replies

4. OS X (Apple)

Problem with mail attachment in Snow Leopard

Hi, We have few scripts that are run through jobs . It sends us daily reports (using mailx). This was working fine in Leopard. But in Snow Leopard there is problem with the attachments.Neither the attachment name is being displayed correctly(all it displays is "Mail Attachment") nor the format... (1 Reply)
Discussion started by: adash
1 Replies
forward(4)						     Kernel Interfaces Manual							forward(4)

NAME
forward - forward mail SYNOPSIS
/var/adm/forward/username $HOME/.forward DESCRIPTION
The .forward file allows a user to forward messages to another host, or to invoke programs (such as vacation(1)) to process their mail. It is formatted as a series of comma-separated addresses in the form: addr_1, addr_2, ... Alternatively, each address can be on a separate line. The newer sendmail.v8 program also allows the use of comments (lines that begin with a ``#'') and blank lines. As with the aliases(4) file, mail messages can be forwarded to another host or given to programs for further processing. The following is an example of the vacation program. Assuming that the user's name is myra, create a .forward file and add the following line: myra, "|/usr/bin/vacation myra" The previous example forwards mail to myra (the backslash prevents an accidental aliasing loop), and also sends a copy of the message to the vacation program. For security reasons, the file must be owned by the user or by root and it should be writable only by the file owner. In addition, the file must be readable by the owner (myra) or root. On traditional systems, only the $HOME/.forward file is checked. The sendmail.v8 program allows the use of the system-wide forwarding directory /var/adm/forward. By default, this directory is checked for a forward file prior to examining the users $HOME directory. FILES
System-wide forwarding file. The per-user forwarding file. RESTRICTIONS
The sendmail command can hang trying to read the user's $HOME/.forward file. If the user's home directory is NFS-mounted and temporarily unavailable, sendmail will stall until the directory becomes available again. The use of non-NFS mounted directories for the forwarding of files is recommended. The use of /var/adm/forward is supported only by sendmail.v8. The actual path for /var/adm/forward is configurable in the sendmail.cf file. Incorrect file permissions/ownership are quietly ignored. It is easy to create an accidental loop, for example, on host_a myra@host_b and on host_b myra@host_a RELATED INFORMATION
Commands: aliases(4), sendmail.cf(4), sendmail(8) delim off forward(4)
All times are GMT -4. The time now is 08:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy