From owner-freebsd-questions Sat Mar 3 9:56:18 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 21F0537B718 for ; Sat, 3 Mar 2001 09:56:15 -0800 (PST) (envelope-from rjmcintire@earthlink.net) Received: from emilyd ([64.161.77.242]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id <0G9M002UKV1RVL@mta6.snfc21.pbi.net> for freebsd-questions@freebsd.org; Sat, 3 Mar 2001 09:53:52 -0800 (PST) Date: Sat, 03 Mar 2001 09:53:52 -0800 From: "Riley J. McIntire" Subject: RE: Forwarding a mail file In-reply-to: <20010302170329.G56205@slappy.plambert.net> To: "Paul M . Lambert" , freebsd-questions@freebsd.org Message-id: MIME-version: 1.0 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Priority: 3 (Normal) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The uuencode solution suggested by another results in a single very > large attachment containing the whole mailspool being sent in one or more > messages. I'm assuming that this isn't your intention. Correct. If I had access to the ISP's mail server I'd cat oldspool >> currentspool I did succeed with uuencode /var/mail/test testfile |mail -s test user@domain.com but as you pointed out, one big attachment that needs uudecode (I guess)--I'm not clear about uuencoding it in the first place. What worked messily was cat /var/mail/test |mail -s test2 user@domain.com which gives one large email with headers and text, but does deliver the mail. If I had to I could use this. I do have elm on the system, and can use formail. elm--Well, I can tag 'em all but can't seem to forward them. formail will do. Thanks, Riley > > If you want the user to receive these messages at their new ISP as if > they were just sent to them, the formail solution mentioned is the > most elegant. You do not need to do a 'make install' of the procmail > port; look in the work directory after just doing a 'make' and you'll find > the appropriate binary. > > If you have any MUAs installed on the system (i.e. mutt, pine, etc.) you > might be able to do a similar thing from within them. I'm not familiar > with anything but mutt, in which I'd do: > > % mutt -R -f /path/to/mailspool > > Once the mailbox comes up, I'd type a capital T (assuming the default > keybindings) which gives a Tag messages matching: prompt. At the prompt > I'd enter just a period (which tags all messasges). > > Then I'd press the semicolon (to make the next command apply to all tagged > messages) followed by a lowercase 'b'. This then shows a Bounce message > to: prompt, at which i'd type the new email address. Then, I'd wait > for quite a while as sendmail is spanked with a zillion new messages all > at once. ;-) > > However, like any task, there are many ways to do it. You'll have to > choose what you're most comfortable with. In my case, I'd use formail > from the procmail port. > > --plambert > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message