Sending and Reading Email

Total Page:16

File Type:pdf, Size:1020Kb

Sending and Reading Email Sending and Reading Email Get familiar with mailx, alpine, mutt, and mail. Creating a Signature file Automatically forwarding incoming messages Announcing an absence with vocation Configuring and managing email with procmail Using the Email An email message is identified by a sender and a receipt, both of which appear as headers in the message. mailx is a mail user agent for moving mails between users on the same host. Depending upon whether both sender and receipt are on the same host, an email address can take the following forms: 1. henry – user henry is on the same host 2. henry@saturn – henry is on a different host 3. [email protected] –henryis on the internet Internet Email Handling (1/3) Internet mail handling requires the works of at least three agencies: 1. Mail user agent –for reading the mailbox and sending mail, like mailx and pine. 2. Mail transport agent –for transporting mail between machines 3. Mail delivery agent –for delivering mail to the recipients’ mailboxes. MUA reads incoming mail from the mailbox and hands over outgoing mail to the MTA. MTA sends and receives mail. At the sending end, it identifies the recipient’s address and delivers the message directly to the MTA at the other end. At the receiving end, the MTA passes on mail to MDA. Internet Email Handling (2/3) MTA’s sending and receiving functions are handled universally by the simple mail transfer protocol (SMTP). The MTA doesn’t deliver mail. MDA does the delivery, like procmail. If the user’s host connects to the mail server intermittently, the user typically uses his ISP’s facilities to handle his mail. The ISP stores the user’s mail on the server, and the user fetches the mail using a separate program, such as POP3 (Post Office Protocol) and IMAP (Internet Message Access Protocol). Internet Email Handling (3/3) mailx and pine can only view mail that has been delivered to the host on which the clients are running. They can’t receive mail from a POP/IMAP server. To receive mail from POP/IMAP server, you need to specify the following parameters as part of your client’s setup: 1. The outgoing SMTP server 2. The incoming server that may use POP3 or IMAP. 3. Your user‐id on these servers. ~/.signature and ~/.forward Most mailers make use of the signature facility to append some static text to every outgoing message. The signature message is often saved in $HOME/.signature. When you travel, you can use the automatic forwarding facility to redirect all your incoming messages to another address. The forwarding address is simply put in $HOME/.forward, so that MTA forwards the mail. The forwarding function is a feature of sendmail, the program that uses SMTP and delivers most of our mail on the Internet. Multipurpose Internet Mal Extensions (MIME) The original SMTP protocol has two limitations that disallowed the mailing of binary attachment. 1. Only 7‐bit ASCII characters could form a mail message. 2. The line length could not exceed 1000 characters. MIME extends the definition of mail to include binary files and multiple data formats in a single message. MIME also imposes no restriction on line length. MIME requires two additional headers to be sent with the message (in addition to the commonly appeared fields: Subject, Date, From, To, and/or Cc): 1. Content‐Type: application/pdf; name=“inter,pdf” 2. Content‐Transfer‐Encoding: base64 Mailx (1/2) mailx is the mail utility, a command‐line tool, that POSIX requires all Unix systems to support. Received mail is deposited in a mailbox. Once a message has been viewed, it moves from the mailbox to mbox. mailx works in both sending and receiving mode. To send a mail, “mailx email_address” and end with a . or [ctrl‐d]. You may also use it non‐ interactively, as in “mailx ‐s “new system” sjkao < message.txt”. Mailx (2/2) Incoming mail is appended to the mailbox, a text file named after the user‐id of the recipient. The mailbox is located in /var/spool/mail (/var/mail in Unix), sjkao’s mail is appended to /var/spool/mail/sjkao. When you enter the mailx, upon ?, you may use + to print next massage, ‐ to print previous message, d N to delete message N, s filename to save the current message, r N to reply to sender the message N, q to quit mailx, and ! cmd to run Linux command cmd. Use w filename to save the message in separate file, such as “w 1 2 memo”. Internal Commands Used by Mailx Command Action +Prints the next message ‐ Prints the previous message N Prints message numbered N hPrints headers of all messages dN Deletes message N (the current message if N is not appeared) u N Un‐deletes message N s flname Saves current message with headers in flname (or mbox) w flname Saves current message without headers in flname (or mbox) m user Forwards mail to user r N Replies to sender of message N q Quits mailx ! cmd Runs the Linux command cmd Reading Email with alpine 1. Type alpine to start the program, there will be greeting message. Enter [return] to main screen. 2. Press L to view the folder list, which includes an inbox and other folders you set up. 3. Use the arrow keys to navigate the folder list. 4. Press V to view the selected folder. 5. Use ↑ and ↓ keys to move up and down in the message list. 6. Press [Enter] to read the selected message. 7. Press q to quit. Tips of Using alpine alpine is case‐insensitive. alpine –i starts in your inbox. As you are pursing your email, you can use [tab] to jump to the next unread message. delete messages by pressing [delete], either when the message is highlighted in the list or when the message is open onscreen. reply a message by pressing [r] with a message selected or while reading a message. Sending Email with alpine 1. Type alpine 2. Press [c] to compose a new massage 3. [tab] to move through the message header fields. 4. Compose your message. 5. When you are ready to send, press [ctrl+x] and confirm sending status (yes or no). To avoid typing a lengthy email address, you may set up an alias by editing the address book (press [A]). If you want to send email to multiple addresses, just separate them with commas or spaces. Customizing alpine 1. Type alpine 2. Press [M] to visit the main menu. 3. Press [S] to summon the setup menu. 4. Press [C] to access the configuration setup menu. 5. Scroll through the configuration list using the ↑ and ↓ keys. 6. Press [Enter] to select the option you want to change. 7. Make your selection or fill in the necessary information. 8. [Enter] to exit the configuration menu and return to main menu. You will be prompted to save your changes. Commonly Used Configuration Options Option Description initial-keystroke- Specifies key commands for alpine to use list when starting, just as if you'd typed them in directly. quit-without-confirm Allows you to exit alpine without the "are you sure?" message. signature-at-bottom Puts your automatic signature at the end of the message you're replying to, rather than above it. saved-msg-name-rule Sets alpine to automatically file your saved messages in a specific folder, based on the characteristics (sender, etc.) of the message. fcc-name-rule Sets your file copy of outgoing messages to be saved in a particular folder. We like the by- recipient option, which files messages according to whom we sent them to. use-only-domain-name Sets alpine to send all outgoing messages with just the domain name and not the machine name on the From: line. For example, our messages come from @raycomm.com , not from @frazz.raycomm.com . Reading Email with mutt 1. Type mutt at the shell prompt to start the program. The system might ask you if you want it to create folders for you. 2. Use ↑ and ↓ keys to move up and down in your mailing list. 3. Press [Enter] to open a message to read. 4. Press l to return to the list or press [Spacebar] to scroll down through the current message. 5. Press [q] to quit. [D] for delete, [?] for help, [R] for reply, and a specific number for the message. Configuration file in ~/.muttrc Sending Email with mutt 1. Type mutt 2. Press [M] to start a new massage 3. [tab] to move through the message header fields. 4. Press [Enter] after you entering the information that mutt asks for, such as to: and subject:. 5. When you finished, press [Esc] 6. :wq to save work and exit the editor (vi). 7. Press [Y] to send the message. Creating a Signature File 1. Nano ~/.signature 2. Key in whatever text for your signature 3. Save and exit the file Both alpine and mutt automatically include a .signature file in outgoing mail. Automatically Forwarding Incoming Messages 1. vi ~/.forward 2. Key in the address as the first line of the file to which you want your email to be forwarded. 3. Save and close the file You can keep the incoming mails as well as forward them to unsuspecting recipients. Typing “\yourid, [email protected]” Announcing an Absence with Vocation 1. vi ~/.vocation.msg 2. Key in the message. E.g. Subject: **** (&msg) 3. Save and close the file. 4. “vocation –I” at the shell prompt to start vocation. 5. “cat ~/.forward”. The .forward file should specify what should happen to your mail upon receipt.
Recommended publications
  • Oldschool E-Mail Setup Eine Freakshow
    Oldschool E-mail Setup Eine Freakshow [email protected] Chemnitzer Linuxtage, 2016 (Screenshot GMX vor >15 Jahren: Waybackmachine zu www.gmx.net) (Screenshot GMX heute) (Screenshot Gmail heute) Lösungen? ● Claws ● Mutt ● Eudora ● Netscape Navigator ● Evolution ● Opera M2 ● GMX ● Outlook ● Gnus ● SquirrelMail ● Hotmail ● The Bat! ● Hushmail ● Thunderbird ● KMail ● … Flußgrafik Email Netz MTA MRA MDA MUA MSA MTA Netz Hipster! ● KISS ● YAGNI ● DRY ● NIH ● Divide And Conquer ● Everything is a file ● No vendor lock-in ● Mißtraue Autoritäten – fördere Dezentralisierung Netz Netz Emails Client, den ich Remote verwenden kann Leicht erweiterbar Emails lokal Filter Offenes Format Adressen Netz Netz Abholen Transportformat? Pull Subject 1 Email = 1 File Keine Spuren X-List-ID Mit Hierarchien am Server Beliebige Einfaches Suchen Header Verlässliches Suchen Verarbeitung mit Unix Tools Client, den ich Remote verwenden kann Leicht erweiterbar Emails lokal Filter Offenes Format Adressen Netz Netz Abholen Transportformat? Pull Subject 1 Email = 1 File Keine Spuren X-List-ID Mit Hierarchien am Server Beliebige Einfaches Suchen Header Verlässliches Suchen Verarbeitung mit Unix Tools mbox Maildir mh Client, den ich Remote verwenden kann Leicht erweiterbar Emails lokal Filter Offenes Format Adressen Netz Netz Abholen Transportformat? Pull Subject 1 Email = 1 File Keine Spuren X-List-ID Mit Hierarchien am Server Beliebige Einfaches Suchen Header Verlässliches Suchen Verarbeitung mit Unix Tools mbox Maildir mh tmp 1439306571.1269_0.elvis ~/Post/Technik/Wikitech new 1448267819.5940_0.spencer ... 1457079728.2000_0.spencer:2, cur 1456839383.9873_0.nepomuk:2,SR 1457166567.23654_0.spencer:2,S ... Client, den ich Remote verwenden kann Leicht erweiterbar Filter Adressen Netz Netz Abholen Pull Subject Maildir Keine Spuren X-List-ID am Server Beliebige Header Client, den ich Remote verwenden kann Leicht erweiterbar Filter Adressen Netz Netz Abholen Pull Subject Maildir Keine Spuren X-List-ID am Server Beliebige Header fetchmail getmail mpop ..
    [Show full text]
  • SMTP (Simple Mail Transfer Protocol)
    P1: JsY JWBS001A-60.tex WL041/Bidgoli WL041-Bidgoli.cls May 12, 2005 3:27 Char Count= 0 SMTP (Simple Mail Transfer Protocol) Vladimir V. Riabov, Rivier College Introduction 1 SMTP Security Issues 12 SMTP Fundamentals 1 SMTP Vulnerabilities 12 SMTP Model and Protocol 2 SMTP Server Buffer Overflow Vulnerability 15 User Agent 4 Mail Relaying SMTP Vulnerability 15 Sending e-Mail 4 Mail Relaying SMTP Vulnerability in Microsoft Mail Header Format 4 Windows 2000 15 Receiving e-Mail 4 Encapsulated SMTP Address Vulnerability 15 The SMTP Destination Address 4 Malformed Request Denial of Service 16 Delayed Delivery 4 Extended Verb Request Handling Flaw 16 Aliases 5 Reverse DNS Response Buffer Overflow 16 Mail Transfer Agent 5 Firewall SMTP Filtering Vulnerability 16 SMTP Mail Transaction Flow 5 Spoofing 16 SMTP Commands 6 Bounce Attack 16 Mail Service Types 6 Restricting Access to an Outgoing Mail SMTP Service Extensions 8 Server 17 SMTP Responses 8 Mail Encryption 17 SMTP Server 8 Bastille Hardening System 17 On-Demand Mail Relay 8 POP and IMAP Vulnerabilities 17 Multipurpose Internet Mail Extensions Standards, Organizations, and (MIME) 8 Associations 18 MIME-Version 10 Internet Assigned Numbers Authority 18 Content-Type 10 Internet Engineering Task Force Working Content-Transfer-Encoding 10 Groups 18 Content-Id 11 Internet Mail Consortium 18 Content-Description 11 Mitre Corporation 18 Security Scheme for MIME 11 Conclusion 18 Mail Transmission Types 11 Glossary 18 Mail Access Modes 11 Cross References 19 Mail Access Protocols 11 References 19 POP3 11 Further Reading 22 IMAP4 12 INTRODUCTION and IMAP4), SMTP software, vulnerability and security issues, standards, associations, and organizations.
    [Show full text]
  • Understanding Post Office Protocol (POP3)
    Understanding Post Office Protocol (POP3) Author: Conrad Chung, 2BrightSparks Introduction Most Internet users with email accounts would have used some form of “client” software (Outlook, Thunderbird etc.) to access and manage their email at one point or another. To retrieve emails, these email clients may require the configuration of Post Office Protocol (or POP3) before messages can be downloaded from the server. This article will help readers understand what POP3 is and how it works. What is Post Office Protocol? The Post Office Protocol (POP3) is an Internet standard protocol used by local email software clients to retrieve emails from a remote mail server over a TCP/IP connection. Since the first version was created in 1984, the Post Office Protocol (currently at Version 3) has since became one of the most popular protocols and is used by virtually every email client to date. Its popularity lies in the protocol’s simplicity to configure, operate and maintain. Email servers hosted by Internet service providers also use POP3 to receive and hold emails intended for their subscribers. Periodically, these subscribers will use email client software to check their mailbox on the remote server and download any emails addressed to them. Once the email client has downloaded the emails, they are usually deleted from the server, although some email clients allow users to specify that mails be copied or saved on the server for a period of time. Email clients generally use the well-known TCP port 110 to connect to a POP3 server. If encrypted communication is supported on the POP3 server, users can optionally choose to connect either by using the STLS command after the protocol initiation stage or by using POP3S, which can use the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) on TCP port 995 to connect to the server.
    [Show full text]
  • Getting Started with Eudora 5.1 for Windows 95/98/ME/NT/2000 Author Teresa Sakata
    WIN9X003 July 2003 Getting Started with Eudora 5.1 For Windows 95/98/ME/NT/2000 Author Teresa Sakata Introduction ..............................................................................................................................................................1 POP and IMAP Servers ............................................................................................................................................2 Requirements ............................................................................................................................................................2 Changes From Version 4.3.x ....................................................................................................................................3 Issues ........................................................................................................................................................................3 Where do I get Eudora? ............................................................................................................................................4 Getting Started..........................................................................................................................................................4 Installation ................................................................................................................................................................4 Configuring Eudora ..................................................................................................................................................5
    [Show full text]
  • What Is the Difference Between Email Protocols
    What Is The Difference Between Email Protocols Interactions between email servers and users are governed by email protocols. The most common incoming email protocols are POP, and IMAP. Most email applications/programs support one or more of these. This article is to help users understand and choose which protocol should be selected for each user’s situation. Outgoing Incoming POP (Post Office Protocol): IMAP (Internet Message Access Protocol): SSL (Secure Socket Layer): Differences Between POP and IMAP Backups / Email Loss Outgoing SMTP (Simple Mail Transfer Protocol) is the protocol used in sending (outgoing) emails. SMTP is the protocol always used for sending (outgoing) emails. Incoming POP (Post Office Protocol) and IMAP (Internet Message Access Protocol) are two different protocols that do the same thing differently. They are both used in receiving emails from a mail server and can both are available for standard and secure (?) connections. POP (Post Office Protocol): POP is an email accessing protocol used to download emails from a mail server. Applications like Outlook and Outlook Express using POP will download all emails from the server to the user’s computer, and then delete them on the server. Generally POP server uses port 110 to listen to the POP requests or securely using SSL (Secure Socket Layer) (?) POP uses port number 995. The POP protocol assumes that there is only one client/computer that will be connecting to the mailbox. Even though there is an option in most mail applications to leave the copies of the emails in the server, it is not generally used due to various reasons.
    [Show full text]
  • Argosoft Mail Server Pro User Guide
    http://www.argosoft.com Argosoft Mail Server Pro User Guide June 2002 1 Introduction Thank you for choosing Argosoft Mail Server Pro. This lightweight and extremely affordable mail server is robust, stable, easy to configure, easy to manage and is fully capable of competing head to head with any mail server on the market. It can perform all basic e-mail tasks, and much more. It is fully functional mail system, which supports most popular protocols, SMTP, POP3, Finger, and has a built-in Web server, to give users quick and easy access to their email via any Web browser, which supports HTTP 1.0 or later. The web interface can also be used to administer the mail server. While this easy to use mail server is pretty much obvious in terms of use there are few little things that even a seasoned e-mail expert may not stumble across immediately. This document is basic guide to getting started! Features • Has true support of multiple domains - you can create accounts with the same name, which belong to different domains • Supports multiple IP homes (virtual domains) • Has built in mailing list server • Has WAP interface • Allows setup of domain administrators - users who can change domain related information via the Web interface; • Filtering of mail according to IP addresses of server which attempts to relay mail to local users • ORDB and MAPS support • Supports distribution lists; • Supports auto responders; • Supports basic filters; • Unlimited message size (there is a limit of 5 Megs for freeware version); • Can listen on single IP address, rather than all addresses available on your computer; • Has built-in web server.
    [Show full text]
  • GNU Guix Cookbook Tutorials and Examples for Using the GNU Guix Functional Package Manager
    GNU Guix Cookbook Tutorials and examples for using the GNU Guix Functional Package Manager The GNU Guix Developers Copyright c 2019 Ricardo Wurmus Copyright c 2019 Efraim Flashner Copyright c 2019 Pierre Neidhardt Copyright c 2020 Oleg Pykhalov Copyright c 2020 Matthew Brooks Copyright c 2020 Marcin Karpezo Copyright c 2020 Brice Waegeneire Copyright c 2020 Andr´eBatista Copyright c 2020 Christine Lemmer-Webber Copyright c 2021 Joshua Branson Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents GNU Guix Cookbook ::::::::::::::::::::::::::::::: 1 1 Scheme tutorials ::::::::::::::::::::::::::::::::: 2 1.1 A Scheme Crash Course :::::::::::::::::::::::::::::::::::::::: 2 2 Packaging :::::::::::::::::::::::::::::::::::::::: 5 2.1 Packaging Tutorial:::::::::::::::::::::::::::::::::::::::::::::: 5 2.1.1 A \Hello World" package :::::::::::::::::::::::::::::::::: 5 2.1.2 Setup:::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.1 Local file ::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.2 `GUIX_PACKAGE_PATH' ::::::::::::::::::::::::::::::::: 9 2.1.2.3 Guix channels ::::::::::::::::::::::::::::::::::::::: 10 2.1.2.4 Direct checkout hacking:::::::::::::::::::::::::::::: 10 2.1.3 Extended example ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Proceedings Template
    0 - IMAP in 90 Days or How to Migrate 25,000 Users to IMAP in Three Months Jay Graham Computing Services and Systems Development University of Pittsburgh 419 South Bellefield Avenue Pittsburgh, PA 15217 (412) 624-5244 [email protected] ABSTRACT Pittsburgh campus. Extensive use of user logs, forwarding data and distribution was critical to the process. The final phase The University of Pittsburgh began the Internet Message Access involved the migration of 25,000 users from VMS Mail, Unix Protocol (IMAP) Project in the spring of 1997 as an evaluation Pine and POP mail to the new environment by April 1, 2000. project investigating the replacement options for the legacy e-mail systems and a POP3 service. The project was initially divided into two phases---Phase 1 to deploy an IMAP server for campus- Keywords wide use and Phase 2 to identify and provide a reliable, high quality, enterprise-wide IMAP client. A sub-group of the IMAP IMAP, e-mail, POP, legacy, client-server project team was formed to identify requirements and evaluate clients. Cyrusoft International's Mulberry was found to meet the ever changing requirements of the campus computing labs and 1. INTRODUCTION have sufficient features and functionality that users would be compelled to switch from their legacy clients to the new Electronic mail has become a primary tool used by many large environment. organizations to enhance daily communication. E-mail between managers, workers, customers, students, teachers or parents often A critical third phase was added to the IMAP project which serves as a more efficient, cost effective and convenient form of required a phase-out of the legacy e-mail systems by April 1, 2000 interaction.
    [Show full text]
  • Sysinfotools Maildir Converter
    SysInfoTools MailDir Converter SysInfoTools MailDir Converter Table of Contents 1. SysInfotools MailDir Converter .................................................................................. 2 2. Overview ................................................................................................................... 2 3. Getting Started .......................................................................................................... 3 Installation procedure ............................................................................................... 4 4. Order and Activation .................................................................................................. 4 How to Order ............................................................................................................ 4 How to Activate ......................................................................................................... 4 5. Using SysInfoTools MailDir Converter ....................................................................... 5 Understanding the User Interface .............................................................................. 6 Button Used .............................................................................................................. 6 How to use MailDir Converter Tool ............................................................................ 7 6. Uninstall the Software .............................................................................................. 13 7. Legal Notice ...........................................................................................................
    [Show full text]
  • Designing a User Interface for the Innovative E-Mail Client Semester Thesis
    Designing a User Interface for the Innovative E-mail Client Semester Thesis Student: Alexandra Burns Supervising Professor: Prof. Bertrand Meyer Supervising Assistants: Stephanie Balzer, Joseph N. Ruskiewicz December 2005 - April 2006 1 Abstract Email Clients have become a crucial application, both in business and for per- sonal use. The term information overload refers to the time consuming issue of keeping up with large amounts of incoming and stored email. Users face this problem on a daily basis and therefore benefit from an email client that allows them to efficiently search, display and store their email. The goal of this thesis is to build a graphical user interface for the innovative email client developed in a previous master thesis. It also explores the possibilities of designing a user interface outside of the business rules that apply for commercial solutions. 1 Contents 1 Introduction 4 2 Existing Work 6 2.1 ReMail ................................. 6 2.1.1 Methods ............................ 6 2.1.2 Problems Identified ...................... 7 2.1.3 Proposed Solutions ...................... 7 2.1.4 Assessment .......................... 8 2.2 Inner Circle .............................. 8 2.2.1 Methods ............................ 8 2.2.2 Problems Identified ...................... 9 2.2.3 Proposed Solutions ...................... 9 2.2.4 Assessment .......................... 10 2.3 TaskMaster .............................. 10 2.3.1 Methods ............................ 10 2.3.2 Problems Identified ...................... 11 2.3.3 Proposed Solution ...................... 11 2.3.4 Assessment .......................... 12 2.4 Email Overload ............................ 12 2.4.1 Methods ............................ 12 2.4.2 Problems Identified ...................... 13 2.4.3 Proposed Solutions ...................... 13 2.4.4 Assessment .......................... 14 3 Existing Solutions 16 3.1 Existing Email Clients .......................
    [Show full text]
  • Mathematics Department's New Email Service
    Mathematics Department’s New Email Service The department’s new email service employs the widely-used IMAP email protocol to allow you to read and organize your email. You may use the Math web-based email service, http://webmail.math.vt.edu, and/or email software on Unix systems, such as elm, mutt or pine. The IMAP protocol stores your email on a department server computer that daily saves your email and files to backup tapes. The server does not have an infinite supply of disk storage, so you will need to periodically delete email you no longer need or transfer it to your PC or Mac for archival.1 You may use the webmail service in conjunction with other email applications. Elm Elm is no longer supported. You may use mutt which is very similar. Pine Before running pine, you must update your existing pine settings with this command, /local/calvin/bin/updatepinerc PID where PID is your Virginia Tech PID. This will create a new .pinerc file in your home directory containing settings for using the new Math Email system. A copy of your original .pinerc file is named .pinerc-pre4.64 in your home directory. If you have previously used an older version of pine, any of your old settings that were not migrated to the new .pinerc will be listed. These are saved in a file named pinerc- settings. If you want to continue using any old settings, you must edit .pinerc to include them. Pine groups mailboxes into collections. One collection will be any mailboxes on the mail server.
    [Show full text]
  • Postfix Catch All and Mutt
    Postfix Catch All and Mutt End goal: having postfix saving all of the emails for a domain to a single “mailbox” in maildir format, and being able to send email using mutt (or similar). Specifics to my setup I'm not going to open port 25 on my server, I'm going through Net7's spam filter, which will then forward to my server on port 8025. So I need to open port 8025. The rule was already there for port 25, I just need to edit the thing. Make Postfix listen to another port There is always the plan of using iptables to redirect the traffic. You can do it in Postfix as well. Open master.cf and find this line: smtp inet n - - - - smtpd The smtp word up front is actually a port. You can replace it with this line: 8025 inet n - - - - smtpd If you restart Postfix and check with netstat it should be listening to another port. Setting up Maildir delivery By default Postfix will output emails to a single file in /var/mail/. I'd rather have the Maildir format which separates emails into different files that I can individually move and/or delete. I'm going off the rails here trying out things. Looks like we're going to need these configuration options in main.cf: home_mailbox = Maildir/ mailbox_command = Make sure mailbox_command isn't set somewhere else in the file. Reload Postfix. We should be able to test that this is working using a known user on the system. You can telnet-test like so: EHLO test MAIL FROM:<[email protected]> RCPT TO:<william> DATA Test.
    [Show full text]