similar to: Dealing with backscatter

Displaying 20 results from an estimated 5000 matches similar to: "Dealing with backscatter"

2020 Jun 11
11
handling spam from gmail.
I am sick of this gmail spam. Does anyone know a solution where I can do something like this: 1. received email from adcpni444 at gmail.com 2. system recognizes this email address has been 'whitelisted', continue with 7. 3. system recognizes as this email never been seen before 4. auto reply with something like (maybe with a wait time of x hours): Your message did not receive the
2010 Feb 04
2
sendmail mail relay backscatter issue.
Hi Folks, I have a couple of questions which I hope that you will be able to assist with, first some background. I run a few sendmail servers that run MailScanner/Spamassassin/sendmail (current versions) on Centos 5.4 and Centos 4.8 These boxes accept mail for a large number of domains (6000+) scan the mail removing spam and then forward the ham to another server for delivery. I am attempting to
2007 Mar 25
4
Cannot execute /usr/bin/fetchmail
Hello everyone, I'm setting up a fetchmail command to run every five minutes so I can get email from another POP3 account. The fetchmail package was installed via yum. I can execute the command manually on the command line. But I'm having trouble when it's run from cron. I have noticed that commands run via cron and execute via /bin/sh, so I tried to run the fetchmail command
2015 Aug 26
5
please block user
On 08/26/2015 12:11 PM, g wrote: > > > On 08/26/15 13:11, Valeri Galtsev wrote: >> On Wed, August 26, 2015 12:55 pm, James A. Peltier wrote: > <<>> > > something no one seems to have mentioned, so i will.. > >>> | >> Received: from mx2.loverhearts.com (mx2.loverhearts.com > > loverhearts.com is a single page that seems to do nothing. and
2015 Feb 13
4
Centos 6 Sendmail backup MX Config
On Fri, February 13, 2015 11:04 am, Les Mikesell wrote: > On Fri, Feb 13, 2015 at 9:57 AM, Ken Smith <kens at kensnet.org> wrote: >> Hi All, >> >> I'm just wanting to check that my understanding of the settings is >> correct >> as my web searches are finding a lot of dated information. >> >> If I want a Centos 6 sendmail system act as the
2020 Jun 11
5
SV: handling spam from gmail.
I know it is not dovecot who should fix this. But anyone using dovecot is using an MTA, and receiving spam ;) I know how to look at email headers. Spf and dkim is not solving anything here. -----Original Message----- From: Sebastian Nielsen [mailto:sebastian at sebbe.eu] Sent: donderdag 11 juni 2020 10:23 To: Marc Roos; 'dovecot'; 'users' Subject: SV: handling spam from
2011 Apr 26
2
dovecot & OCFS2 Cluster
Robert Schetterer <robert at schetterer.org> writes: >> Anyway, why use lmtp over lda ? > > i.e avoid backscatter by overquota A clarification on this: backscatter (or rather, ambiguous NDR notices that claim many users are over quota rather than just one) is a result of a local mailer that support multiple recipient delivery in one invocation, but can only return one result
2017 Dec 10
2
hosting emails at home
Hello Mike, Yes, I am using a static IP address, but in theory, you could use a dynamic one. Nothing technically would prevent email exchanges between two boxes, as long as the SPF records are up to date and the DKIM is properly setup. Unfortunately, some ISPs are simply blacklisting full range of private IP addresses just because they are not officials / commercials. Kind regards, Andr? On
2010 Apr 20
1
[oOT] ploenk.net@eplus.blackberry.com please fix your mail forwarding
I've received a bunch of these blackberry backscatter messages over the past week and have been unable to determine which list user is the cause of this. Whoever is forwarding your email to the blackberry address below, please fix the situation. It's becoming really annoying receiving these backscatter bounces that give no clue as to what the nature of the problem is. Thanks. Your
2012 Mar 29
1
my spammer list
Hello, Thanks to some nice people on here and other forums I have pretty much finalized my whole mail system on centos 6.x. With all the checks, greylisting, dev/null of any 8+ spam level SA, I still get a few mails. It seems like everytime I enable a new protectant, the mail stops spamming for a few hours...then the spammers decide I am worthy of using better methods against me..and more
2017 Dec 10
4
hosting emails at home
I have dovecot postfix setup on my home server as well. I use a virtual server in the cloud as my mx record and mail relay and have my home record on dynamic dns. It's really effective. On Dec 10, 2017 2:37 PM, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > On December 10, 2017 2:49:35 PM EST, "Andr? Rodier" <andre at rodier.me> >
2015 Aug 27
2
please block user
On 08/27/15 09:31, m.roth at 5-cent.us wrote: <> > *sigh* > And they're probably sent by a script running on the PC of a fat, > 47 yr old guy living in a basement and making money this way.... > . i seriously doubt it. several of the responses could not have been from a fat 47 yo guy. -- peace out. If Bill Gates got a dime for every time Windows crashes... ...oh, wait.
2017 Dec 10
2
hosting emails at home
Which part? Hosting the email server at home or the relay in the cloud? On Dec 10, 2017 14:53, "Fabian A. Santiago" <fsantiago at garbage-juice.com> wrote: > On December 10, 2017 3:39:05 PM EST, Stephan H <herker at gmail.com> wrote: > >I have dovecot postfix setup on my home server as well. I use a > >virtual > >server in the cloud as my mx record
2015 Feb 13
2
Centos 6 Sendmail backup MX Config
On Fri, February 13, 2015 11:52 am, Les Mikesell wrote: > On Fri, Feb 13, 2015 at 11:39 AM, Valeri Galtsev > <galtsev at kicp.uchicago.edu> wrote: >> >>> Otherwise it accept junk that your primary rejects >> >> Not exactly. If greylisting on primary is set, but on backup MX is not, >> still what is killed by greylisting by primary MX, almost never
2015 Feb 13
2
Centos 6 Sendmail backup MX Config
On Fri, Feb 13, 2015 at 12:45 PM, Valeri Galtsev <galtsev at kicp.uchicago.edu> wrote: > >>> >> In this case the secondary MX has the same RBL's etc etc as the primary. >> I do see the spammers sending their junk to the secondary more than the >> primary MX. Agree the secondary does not know the difference between >> valid and invalid addresses. >
2006 Jul 07
2
protocol for "Surge MAX"
I am sorry if this is an FAQ, but there doesn't seem to be searchable archives, and the supported manufacturer's list doesn't include "surge master". Google was also not much help. I have just put a Linux box and the customer has a "surge max " UPS. Anyone any ideas what protocol it uses? There is a Green serial cable. The manufacturers web site is here:
2018 Feb 27
1
Quota status to postfix in distributed environment
Out of curiosity would it be possible to configure dovecot in such a way that if a message had been accepted by postfix because it couldn't check quota the message was delivered anyway, despite being over quota? I'd much rather that then risk backscatter. (I used to have quotas, but with the size of disks I've found it easier to simply have a "clue bat?approach and a reasonable
2019 Feb 10
1
offtopic: rant about thoughtless enabling DMARC checks
On 2/10/19 3:46 PM, Michael A. Peters via dovecot wrote: > On 2/10/19 3:42 PM, Noel Butler via dovecot wrote: >> On 10/02/2019 12:49, Benny Pedersen via dovecot wrote: >> >>> >>> fixing mailman will be the fail, solve it by letting opendkim and >>> opendmarc not reject detected maillist will be solution, >> >> >> A general broad mailing
2010 Jan 05
2
Dovecot Quota Problem
I'm using Dovecot LDA with Exim. I'm also using Dictionary Quotas in a MySQL database. I want to avoid backscatter completely, so I set "quota_full_tempfail = yes" and handle quota checking in the Exim RCPT ACL during the SMTP session. The problem lies in the case where a user's account is nearly full. Smaller messages will continue to come through, but a larger message
2019 Mar 24
1
Weird things in the mail queue
Hi Aki, Am 21.02.19 um 12:55 schrieb Aki Tuomi: > > On 21.2.2019 13.47, Lionel Elie Mamane via dovecot wrote: >> I noticed a mail stuck in my mail queue. dovecot-lda was returning >> error 64 Invalid parameter given. (EX_USAGE). >> >> Weird, weird, weird. After some sleuthing, I found the sender address >> was FirstLast at domain.tld, with a UTF8-encoded