Quinn Comendant wrote:
> This might work better then:
>
> $(echo $RECIPIENT | sed -E "s/^${HOST}-([EMAIL PROTECTED])+.*/[EMAIL
> PROTECTED]/")
>
> This is assuming no usernames have a - in their username.
>
> Q
>
>
> On Sat, 18 Nov 2006 13:14:28 -0600, Matt Decker wrote:
>> The following doe
This might work better then:
$(echo $RECIPIENT | sed -E "s/^${HOST}-([EMAIL PROTECTED])+.*/[EMAIL
PROTECTED]/")
This is assuming no usernames have a - in their username.
Q
On Sat, 18 Nov 2006 13:14:28 -0600, Matt Decker wrote:
> The following doesn't work in a few cases:
>
> $(echo $RECIPIE
Just a follow up / FYI...
The following doesn't work in a few cases:
$(echo $RECIPIENT | sed -r 's/[^-]+-//') in place of [EMAIL PROTECTED] in your
.qmail file
And the cases are:
1. If the domain actually has a dash in it (ie. some-domain.com) (note:
as a hack I repeated the sed command which
The current version of qmailadmin doesn't do this for me. What version are you
running? Have you customized the install at all via qmailadmin-toaster.spec?
Quinn
On Tue, 14 Nov 2006 08:16:03 -0600, Matt Decker wrote:
> Whenever someone updates their password their folder location is
> appended
It should work the same as the normal .qmail file.
Try something simple, just to be sure the file works. Create a .qmail-username
file with the following for testing:
&[EMAIL PROTECTED]
Send an email to username and see if the message is forwarded.
Also try fixing the perms on this file:
chow
Quinn Comendant wrote:
I too am confronting the issues with simscan not knowing the actual destination
user account. I haven't setup SQL bayes (yet -- I hope to soon) but I am using
per-user SQL user prefs.
I have been living with this limitation because blocking spam at the SMTP level is ve
Jake Vickers wrote:
Matt Decker wrote:
I'm migrating my qmail toaster from a site wide spamassassin setup to
a per user (MySQL based) setup. The problem I had with this was that
simscan doesn't know the final main account delivery email address
for forwards and domain aliases. This is also
Matt Decker wrote:
I'm migrating my qmail toaster from a site wide spamassassin setup to
a per user (MySQL based) setup. The problem I had with this was that
simscan doesn't know the final main account delivery email address for
forwards and domain aliases. This is also a problem when email h
I too am confronting the issues with simscan not knowing the actual destination
user account. I haven't setup SQL bayes (yet -- I hope to soon) but I am using
per-user SQL user prefs.
I have been living with this limitation because blocking spam at the SMTP level
is very important (IMHO) both f
I'm migrating my qmail toaster from a site wide spamassassin setup to a
per user (MySQL based) setup. The problem I had with this was that
simscan doesn't know the final main account delivery email address for
forwards and domain aliases. This is also a problem when email has
multiple recipie
10 matches
Mail list logo