Hi all,
I've just installed Qmailtoaster on a test system and I'm having some
trouble with message delivery. For various legacy reasons I'm not
using a bog standard Qmailtoaster build, we have an existing
Qmailrocks system but I'd like to transition to an RPMed system.
Briefly, I've stripped
Hi,
After some works i did, we could reach in Yahoo Inbux.
The way:
1- Be sure your ip / domain is NOT in black list.
2- SPF record (Maybe reverse DNS needed).
3- Send emails a couple times to Yahoo accounts and
always say that this is NOT Bulk.
So, Yahoo LEARNS that and next times, no problems
Yes, I use Jakes method and it works fine.
Thank You Jake!
Jake Vickers wrote:
Gabriel Lai wrote:
Hello,
Have anyone tried replication over internet? SSH protocol? 24hours?
Please share.
I backup my machines nightly using rsync over ssh. I have also tested
using SSHFS, which worked as
Firdaus Tjahyadi wrote:
Dear Friends
a few days a have alot spam like this
The hottest pick this year!
It just doesn't get any better than this. Booming sector, tightly held, with
an incredible PR blitz starting up. Not only that, but the company is set to
Will McDonald wrote:
Hi all,
I've just installed Qmailtoaster on a test system and I'm having some
trouble with message delivery. For various legacy reasons I'm not
using a bog standard Qmailtoaster build, we have an existing
Qmailrocks system but I'd like to transition to an RPMed system.
David Milholen wrote:
Yes, I use Jakes method and it works fine.
Thank You Jake!
I finally got around to writing up a quick how-to on this subject on the
wiki, under Tips and Tricks for those that are interested.
You're welcome.
smime.p7s
Description: S/MIME Cryptographic
I've installed but I do not have a simscan-toaster.spec file in the
/usr/src/redhat/SPECS directory.
Thanks
- Original Message -
From: Quinn Comendant [EMAIL PROTECTED]
To: qmailtoaster-list@qmailtoaster.com
Sent: Monday, December 18, 2006 8:46 PM
Subject: RE: [qmailtoaster]
On 19/12/06, Jake Vickers [EMAIL PROTECTED] wrote:
Will McDonald wrote:
Hi all,
I've just installed Qmailtoaster on a test system and I'm having some
trouble with message delivery. For various legacy reasons I'm not
using a bog standard Qmailtoaster build, we have an existing
Qmailrocks
Thank you for the replies, fellas.
I'm pretty sure the reason that our messages are flagged is because we are
using the IP given to us by our local cable company, and do not have the
ability to add a reverse DNS entry that matches our domain.
I found this post while skimming some of the forums
Brad Fuller wrote:
I'm a newbie to DNS, but from my understanding reverse DNS is not something
we can do ourselves without the help of our ISP. Please correct me if I am
wrong.
- Brad
You are correct. Unless you do some ISP things on your own. Like set
up your own DNS server.
+
On 19/12/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
Greetings, Will.
In tcp.rules I have...
[EMAIL PROTECTED] smtp]# cat /etc/tcprules.d/tcp.smtp
127.:allow,RELAYCLIENT=
I've added a virtual domain, 'testdom.com' and a user in that domain.
Looks like SPF related trouble. Try to modify
Quinn Comendant wrote:
I wrote a couple weeks ago about how best to trace the path of an email (an
its errors) through the different multilog files. It clearly isn't an easy
task. Whenever a customer asks me I lost an email I usually spend 10-30
minutes greping, sorting, and
Coming to this mid-thread as I've only just subscribed since starting
to tinker with Qmailtoaster. Has Splunk been mentioned as a
possibility?
http://www.splunk.com/
http://www.google.co.uk/search?hl=enq=site%3Ahttp%3A%2F%2Fwww.cuddletech.com%2Fblog%2F+splunkmeta=
This isn't something I've
Check out dyndns.org. My server is on a dynamic IP address, and I don't have
any problem (that I know of). I use their customdns service for my dns, and
selectively use their mailhop service (for domains that block dynamic IPs).
Both services are quite affordable, and well worth it. I've had no
Alexey Loukianov wrote:
Hello all,
I'm forced to run a bunch of SA-specialized servers to be able to
handle processing of all the incoming mail to the corporate servers.
All the SA hosts utilize the same HA mysql for bayest storage DB, and
a simple king of load-balancing for SA is achieved
Will McDonald wrote:
On 19/12/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
Greetings, Will.
In tcp.rules I have...
[EMAIL PROTECTED] smtp]# cat /etc/tcprules.d/tcp.smtp
127.:allow,RELAYCLIENT=
I've added a virtual domain, 'testdom.com' and a user in that domain.
Looks like SPF
On 19/12/06, Eric Shubes [EMAIL PROTECTED] wrote:
Will McDonald wrote:
On 19/12/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
Greetings, Will.
In tcp.rules I have...
[EMAIL PROTECTED] smtp]# cat /etc/tcprules.d/tcp.smtp
127.:allow,RELAYCLIENT=
I've added a virtual domain,
Will McDonald wrote:
On 19/12/06, Eric Shubes [EMAIL PROTECTED] wrote:
Will McDonald wrote:
On 19/12/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
Greetings, Will.
In tcp.rules I have...
[EMAIL PROTECTED] smtp]# cat /etc/tcprules.d/tcp.smtp
127.:allow,RELAYCLIENT=
I've added a
So it is safe to remove all signs of DK in the tcp.smtp file? Is this then
the correct format that will leave it functioning:
:allow,BADMIMETYPE=,BADLOADERTYPE=M,CHKUSER_RCPTLIMIT=50,CHKUSER_WRONG
RCPTLIMIT=10,QMAILQUEUE=/var/qmail/bin/simscan
-Original Message-
From: Eric Shubes
On 19/12/06, Eric Shubes [EMAIL PROTECTED] wrote:
Will McDonald wrote:
On 19/12/06, Eric Shubes [EMAIL PROTECTED] wrote:
Will McDonald wrote:
On 19/12/06, Alexey Loukianov [EMAIL PROTECTED] wrote:
Greetings, Will.
In tcp.rules I have...
[EMAIL PROTECTED] smtp]# cat
Dan Herbon wrote:
So it is safe to remove all signs of DK in the tcp.smtp file?
Yes. You might want to keep DKSIGN for signing outgoing email if you've set
up DK properly (generated key key and modified DNS appropriately).
Is this then
the correct format that will leave it functioning:
Well that broke my email delivery.
When I did:
Also, be sure to change the symlink for qmail-queue:
# cd /var/qmail/bin
# rm -f qmail-queue; ln -s qmail-queue.orig qmail-queue
And then removed DKQUEUE=/var/qmail/bin/qmail-queue.orig from the
tcp.smtp file. Leaving the last line in the tcp.smtp
Did you double-check your symlink? It'll let you create the link even if
it's 'broken' (points to something non-existent). I fat fingered it once,
specifying qmail-queue-orig instead of qmail-queue.orig.
Dan Herbon wrote:
Well that broke my email delivery.
When I did:
Also, be sure to
Hey man, how about a subject line?
Dan Herbon wrote:
oans.com
X-AntiAbuse: This header was added to track abuse, please include it with any
abuse report
X-AntiAbuse: Primary Hostname - web10.cfnsi.com
X-AntiAbuse: Original Domain - qmailtoaster.com
X-AntiAbuse: Originator/Caller UID/GID -
Splunk looks *awesome*!
Will: when/if you get this running please let us/me know how well it works with
qmail, et al.
All: I'll continue to research this, but for the next month or so Im pretty
booked with projects so I can't give no love here.
Quinn
On Tue, 19 Dec 2006 16:46:18 +,
Rats. You caught me! ;P
That was a copy-and-paste error on my part (copied the path to the spamassassin
RPM from a different document, then changed the file name to simscan leaving
the same version. Sorry for the confusion. ;P
Quinn
The permissions on qmail-queue.orig were set to 711 somehow! Once I reset
them to 4711 mail started flowing.
-Original Message-
From: Eric Shubes [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 19, 2006 3:20 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] 554 mail
On Mon, 18 Dec 2006 18:49:34 -0800, Quinn Comendant wrote:
Are there any others?
Just to keep this info in the same thread, here is one that I had previously
mentioned...
John M. Simpson wrote:
This is a script that i run as a cron job every hour. it goes through
/service/*/log/main and
All,
Splunk is Very Neat. But, it's no good at deciphering qmail's logs (or
at least, I never had any luck writing a custom search to provide the
information that I need to see.) Also, for the quantity of email logs
that I generate per day (500MB), Splunk becomes non-free.
Qmail's logging is,
Joseph Lundgren wrote:
All,
Splunk is Very Neat. But, it's no good at deciphering qmail's logs (or
at least, I never had any luck writing a custom search to provide the
information that I need to see.) Also, for the quantity of email logs
that I generate per day (500MB), Splunk becomes
On Tue, 19 Dec 2006 16:24:54 -0500, Jake Vickers wrote:
I have to agree. The logging in QMail plain sucks. It's almost made
me switch to Postfix a few times. Unfortunately, I don't see any way
of correlating the messages without modifying the patches, since
there is no common
Qmail-track is pretty much what I was looking for. Thanks Joseph!
With that and a tool for statistical summaries I'd say we'd have our log bases
covered.
Quinn
On Tue, 19 Dec 2006 13:03:50 -0800, Joseph Lundgren wrote:
The best tool that I found to get proper information about the
I know it's been talked about on the list before, but I finally got
tired enough of RBLs taking a LONG time and wrote a quick script to
check them. I know, a little late with the submission port, but better
late than never.
What it does is check a list of RBLs (defined in the head of the
Hi Jake,
Nice script!
One small thing, I downloaded this directly to a centos box using wget.
And that resulted in a dos lf file. So getting quite a few errors when you
run it then.
I allready converted it using vi, but maybe you can put a unix lf version
online instead.
Thanks for the
Thanks Jake
I noticed a couple things:
- dig times out at 5 seconds by default, so if anybody set CEILING at more than
5 it will fail anyways, but you could set the +time=$CEILING option.
- If a DNSBL is offline, won't dig return instantly with a NXDOMAIN? I guess
that doesn't matter since
On 12/19/06, Jake Vickers [EMAIL PROTECTED] wrote:
Firdaus Tjahyadi wrote:
Dear Friends
a few days a have alot spam like this
The hottest pick this year!
It just doesn't get any better than this. Booming sector, tightly held,
with
an incredible PR blitz starting up. Not only that,
Hi,
Problem may be because of static ip. Maybe they listed
some ip ranges as suspicious mail sender.
And a question, i did reverse dns look up at:
http://remote.12dt.com/
and it resulted my ip to my domain adress. Good or
not? Should it be to mail.mydomain.com or only
mydomain.com?
And did
37 matches
Mail list logo
