General :: Procmail: Forwarding Just Does Not Work?
Mar 13, 2011
I've spent pretty much the whole night trying to figure out how I can achieve the following: If a certain Keyword, say [key], is in the subject line, then the email is forwarded to a list of people.
My recipe (now) looks like this:
Code:
:0
* ^Subject: .*[key].*
! my-email@gmail.com
The (verbose) procmail logfile gives me this:
[Code]....
Is my recipe wrong in any way? I pretty much copied it from available ones.
It's a university server, so I'm no admin, just a user. How can I figure out whether some setting that the admin made prevents procmail from calling sendmail or whatever?
I have an OpenGL program in a Linux server. I want to run the program remotely with X forwarding, but it fails, whereas programs such as xclock and xeyes work fine. (I confirmed that the program works in the local desktop environment.) Below is additional information.
I have Postfix and Spamassassin setup on Ubuntu Server 9.10. The mail is working perfectly. Spamassassin is correctly marking messages as spam. My problem is with the milter and procmail. On past servers I was able to reject spam based on score via the spamass-milter. For whatever reason I can not get it to work. I have also tried with procmail, again, it does not work. Here are the relative lines in their respective config files:
I have procmail parsing the subject line of incoming e-mail and depositing individual files in a folder that match the procmail recipe.I want to have that recipe spawn a perl script to parse the file to pull out specific information. I've googled this and found many examples but none of them work.When it finds a matching inbound message it logs it correctly in the charge.log file, writes the message in charges/new/xxx but skips the /home/rowan/billing.pl script.
I have 2 guest machines on 1 VBox host installed : - one guest with hostname 'debian' is configured as follows and has IP Forwarding enabled to be able to route traffic from eht1 to eth0.
Code: eth0 Link encap:Ethernet HWaddr 08:00:27:f1:ef:5f inet addr:10.0.2.1 Bcast:10.0.2.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fef1:ef5f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
I am trying to set up mutt with fetchmail and procmail on server space that's not mine. I have access to /home/myusername but not to /var/spool/myusername. Everything seems to work well, but I have no idea where fetchmail (or procmail) is dropping off my mail.
I have a question regarding port forwarding. I have a fedora server, with two eth cards: eth0 ---> external IP, eth1 ----> LAN IP I use SNAT for connection sharing. I also have an internet domain hosted on this server... let's call it [URL] Anyway, one of our computers in the LAN has some kind of web server on it, which must be accessed from the internet on the port 23700.
So, using iptables -t nat -A PREROUTING -i eth0 -p tcp -m tcp --dport 23700 -j DNAT --to 192.168.1.25 (the IP of the network computer) Everything works perfectly fine from outside the lan. When I type [URL], I connect to that computer. My problem is that inside the lan, typing [URL] does not work! It only works if I enter it by IP 192.168.1.25:23700 Is there any way to make the server forward my request to that specific computer even if I'm inside the LAN?
I'm trying to understand and set up port forwarding with iptables. So far I've read a lengthy tutorial on iptables, and I've Googled for hours, searched this forum, but I've been unable to come up with a solution that works for me.The situation I would like to achieve is the following: on one machine, there is a TCP server running bound to its external IP, port 9999. I would like to let another machine connect to this TCP server on port 9000 by forwarding port 9000 to 9999.All the policies of the iptables chains are set to ACCEPT; and I have set net.ipv4.ip_forward = 1. I have no problems using SNAT/MASQUERADE on the same server machine.I have tried the following:
In order to test this rule, I started a TCP echo server on port 9999. I can connect to it on port 9999, but not on port 9000- this gives me 'connection timed out'. When I do 'iptables -t nat -L -v', I can see that the rule does get matched once per connection attempt.
I was able to do on Debian and Ubuntu Servers X applications running on remote servers where I was able to login via SSH. Tried the same with CentOS did not worked. in /etc/ssh/sshd_config
How do I write a procmail recipe that executes a shell script without affecting delivery?(in this case, something that sends me a DM via Twitter) I don't want to affect further processing of the message - it should continue on its way and the output of the script should be ignored.
I have a machine with Ubuntu Server and VMware Workstation 7 installed. I have tried NAT port forwarding to gain Remote Desktop access to a Windows virtual machine, but it did not work for whatever reason. I've done this by editing the nat.conf file in the /etc/vmware/vmnet8/nat directory. Unfortunately it still does not work. Also, I would like to ask if it is possible to port forward using the virtual machine itself and not the host.
I've been beating myself over the head with iptables and CANNOT get port forwarding to work. Here's my situation: Static LAN IP on eth0 Static internet IP on eth1 ip_forward is turned on by uncommenting in sysctl.conf Here's the output of iptables-save:
Code: # Generated by iptables-save v1.4.4 on Tue Mar 8 10:34:12 2011 *nat :PREROUTING ACCEPT [2443:347058]
[Code]...
Edit: by the way, the intended purpose of this machine is to server as a gateway and firewall. MASQUERADE is working, for whatever that is worth. And the host behind the firewall that is serving up http is definitely working too. All that is not working is getting hosts on the internet talking to hosts behind the firewall.
I used the following 2 rules in iptables to forwarding some packagesiptables -t nat -A PREROUTING -p tcp --dport 8000 -j DNAT --to-destination 192.168.0.244:8000iptables -t nat -A POSTROUTING -p tcp --dport 8000 -j MASQUERADEIt works perfectly before, the kernel was 2.6.18-92.1.22.el5.After we did a update, the kernel now is 2.6.18-128.7.1.el5.and the forwarding is stop.I just wondering where can I get some debug information. I checked /var/log/message, dmesg ... seems nothing there.
we have here a few openSUSE-machines (some 11.1 and 11.2) which mounts their /home from a NFS-Server and imports the users via NIS. I now wanted to use X-Forwarding via SSH, but that doesn't work with NIS-Users.On my machine I use Gnome and my XAUTHORITY-Variable points to /var/run/gdm/auth-for-bup_deg-E3TMSz/database
Why isn't the default ~/.Xauthority-File used for my cookies? What do I have to change to get X-Forwarding in my Setup running?
I have 2 different networks: the first one is gateway machine (eth0), and the second is a private machine (eth1). So, I've configured the iptables and forwarding stuff and when I try to ping google.com on the gateway machine, it works, while it doesn't work on the private network. Note: I am using VmWare 7. I need your quick assistance about this issue.
I'll explain this in one sentence: Is it possible to program a port-binding shellcode in which people across the Internet can connect to, without being thwarted by the router blocking their data because the port its bound to doesn't allow port-forwarding
I have just set up shorewall on my router running Arch Linux. The external network is on eth0 and the internal network on eth1.I have set it up for masquerading and that works fine and I can open ports to the firewall. But I'm having trouble with port forwarding to my internal machines.The problem I have is that when port 22350 is forwarded to 192.168.1.3 on my local network, checking the port with nmap from a remote computer gives me:
I have my .procmailrc file set up to pipe mail to a simple php script I've written. The only thing the script does at this point is echo back a "hello" message. However, procmail does not execute the script properly.
here is what i need to do: [url]..... resolves to 209.5.5.5 which is my public IP on the external side of my router. Router is setup to forward (port forwarding) all port 80 based traffic to internal ip 192.168.1.10 which I want that server to lookup the request, and for web1 forward to 192.168.1.101, for web2 to .102 etc....how can i acheive this? What do i need to use?
I'm using sendmail and I'm trying to set up some forwarding accounts. It seems simple enough but all the results I've gotten on Google so far are pretty unhelpful. Isn't there a straightforward tutorial somewhere?
I am using sendmail-8.13 & procmail as an MDA. Now as our mail users are increasing I need to put up mailbox quota limit for every user. I have gone through the search engine but could not found any effective help to configure mailbox quota with sendmail & procmail.
So my question is, where do I put .procmailrc? An examples I found on the net has the procmailrc in the users mail directory, but there are no user mail directories on the sendmail server. It is used purely to relay mail to the Exchange server.
I am trying to filter out attachment emails using procmail. I have tried this: Code: #Config: SHELL=/bin/sh PATH=/bin:/usr/bin:/usr/bin MAILDIR="/var/mail/root" LOGFILE=/var/log/procmail.log LOGABSTRACT=ALL VERBOSE=ON :0 *^Content-Transfer-Encoding: base64$ { | echo $LASTFOLDER } [/code]
As you can probably guess, this line "Content-Transfer-Encoding: base64" appears when emails come with attachments, but the result of this filter is: Code: procmail: No match on "^Content-Transfer-Encoding: base64" procmail: Skipped "| echo $LASTFOLDER" procmail: Assigning "echo" procmail: Skipped "| $LASTFOLDER" procmail: Assigning "LASTFOLDER=/var/mail/root/msg.OFT" procmail: Opening "/var/mail/root/msg.OFT" procmail: Acquiring kernel-lock procmail: Notified comsat: "root@0:/var/mail/root/msg.OFT" From root Mon Apr 11 01:23:37 2011 Subject: Folder: /var/mail/root/msg.OFT 26051
The result showed as if there was no match, futhermore, the bash code that I am trying to run: echo "$LASTFOLDER" seemed not to be ran as bash? And does anyone know how I can test my procmail filter on some testing platform sandbox so I don't have to send a bunch of emails everytime I change the file and waste time and disk space testing new filters?
I have been trying to get procmail working on CentOS 5.2. I don't need anything fancy, just an auto reply for a "noreply@" account. Looking at the sendmail configuration, it appears procmail is the MDA. I have looked at many different tutorials and how-tos, but most are old, and/or the locations/paths and setups are markedly different from the defaults on my system. Can anyone recommend a good CentOS-based tutorial on Procmail w/ recipes? (I have an RHEL book and it's no help either.) Thank you for your time and consideration.
Recently we are receiving lots of spam email specially ( Viagra). I want to use spamassassen to filter the spams so I need to configure procmail as local mail delivery agent.At the moment I am using prosfix for mail delivery agent and our server is Centos 5. I did google it but couldn't find a good instruction.
