similar to: Dovecot Quota Problem

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

The kernel patch series just sent (Subject: "Btrfs: scrub: print path to corrupted files and trigger nodatasum fixup") introduces two new ioctls to do in-kernel filesystem path construction. This series provides the corresponding userspace changes, adding two new commands to the btrfs utility: -- btrfs resolve inode [-v] <inode> <path> resolves an <inode> to all

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

Hi, Martijn sent the following patch to me in private and agreed that i post it here. In any other program in OpenBSD base, i'd probably agree with the basic approach. Regarding OpenSSH, however, i worry whether wcwidth(3) can be used. While wcwidth(3) is POSIX, it is not ISO C. Does OpenSSH target platforms that don't provide wcwidth(3)? If so, do you think the problem can be solved

How can I disable mail delivery for a user yet still allow access to their mailbox from another account which their mail is shared to? If I put them in a userdb which has "deny = yes" that just disables their ability to login, yes? And they would still have mail delivered. I want to disable their ability to login AND bounce all mail delivered to them, preferably solely through dovecot

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

Am 12.06.2020 um 02:03 schrieb Ralph Seichter: > * Andreas Born: > >> There exists one problem: at this stage of mail reception you have no >> body content nor header information on which a milter may perform >> deeper analysis, only envelope data. > > I am not sure what you mean by "this stage of mail reception", or what I meant the different stages when

While testing raid-auto-repair patches I''m going to send out later, I just found the very last bug in my current scrub patch series: Changelog v4->v5: - fixed a deadlock when fixup is taking longer while scrub is about to end Original message follows: ------------------------ This patch set introduces two new features for scrub. They share the backref iteration code which is the

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

On Jan 13, 2015, at 8:30 PM, Reindl Harald <h.reindl at thelounge.net> wrote: > > so what you want in your OP is just DISCARD in a sieve script and there is no point in "Using Dovecot LMTP it would be more optimal to kick a 5xx back" when the desired result is DISCARD > > why do you want the burden of keep the SMTP session with the client open until the mail is

Hi, I scrubbed a BTRFS volume (mounted as a VFS root) and got several errors. However I am not able to make btrfs print the path of the corrupted files... E.g. kernel log gives : [51078.682876] btrfs: unable to fixup (regular) error at logical 51241746432 on dev /dev/root [51078.683013] btrfs: checksum error at logical 51242385408 on dev /dev/root, sector 102196320, root 684, inode 60676040,

Hi all, I've had to deal with a sudden surge of backscatter email lately. Would anyone be able to suggest to solutions that worked for them regarding this problem? We are using Scalix 11 as our email platform. It uses Sendmail MTA for those who may not be familiar. Thanks, Matt -- Stand before it and there is no beginning. Follow it and there is no end. Stay with the ancient Tao, Move

Hi, I successfully configured dovecot using virtual users (and LDAP/AD). deliver is the LDA and verifies if the user exists (as recommended in the WIKI). However, the howtos in the Wiki say *nothing* about the case that the recipients should be verified *before* receiving the messages (prevent backscatter, ...). All configurations in the dovecot-Wiki (postfix and exim) just accept the mails

Am 26.01.2015 um 08:52 schrieb Steffen Kaiser: > On Sun, 25 Jan 2015, Joseph Tam wrote: >> St?phane Cottin writes: > >>> dspam already send errors to syslog, the point here is to never loose >>> email contents. This was a wrong design, i'm now use a wrapper instead >>> ( see my previous post for details ). > >> You're stilling going to lose

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

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 Unicode U+FEFF ZERO WIDTH NO-BREAK SPACE character (AKA byte order mark) between "First" and "Last" :) Since that is passed as the -f parameter to

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 secondary MX for domain bbbbb.co.uk do I just add a Connect:bbbbb.co.uk RELAY statement into /etc/mail/access and restart sendmail Obviously I have the DNS MX records for the domain are

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. >

Hi all, I'm working with radar remote sensing data and want to measure the height of 3d spikes created by backscatter from bright objects. My thought is to fit a gaussian density function to each spike and extract the x, y and z location of the peak. Can anybody give me a hint of how to do this? Thanks, Alan [[alternative HTML version deleted]]

Am 11.06.2020 um 19:15 schrieb Ralph Seichter: > Generating backscatter is definitely not a good move, and it is even > prone to punish yourself. Better to reject the offending message with > a 5xx status code and some explanatory text or the URL. > > The various tests required to come to a decision about accepting or > rejecting the message can be executed in a milter.