Re: enable username authentication
sorted it i ran chown apache:apache /var/www/html/logs and temp the database wouldnt connect as the username i put was "root" NOT roundcube and the SMTP test didnt work as the sender should be my whole email address "robert.w...@robina.ddns.net" thanks
Re: PATCH: Wildcard key and inline-maps
Sorry, but it still doesnt work. I took a "vanilla" 3.1-20150721 and
patched it again, checked if the patch applied correctly (searching for
register_maps_byname() in smtpd_check.c etc.) and compiled the sources.
When I leave out the leading "{" and the ending "}" it seems to work,
but only if
check_mumble_access inline:{send...@zwackl.de=OK},static:{REJECT BAD
SENDER}
When I specify
check_mumble_access inline:{send...@zwackl.de=DUNNO},static:{REJECT
BAD SENDER}
the static map applies but ends with a reject.
How would you test it? My ideas are running low :-/
Thanks for your help!
Dominik
Am 27.07.2015 um 12:44 schrieb Wietse Venema:
/usr/sbin/postconf: warning: main.cf: syntax error after '}' in "{
send...@zwackl.de=OK }, static: { REJECT BAD SENDER } }"
There should be no SPACE after ":". Also, I haven't tested this
with postconf, assuming that it would be fine as long as every ":{
has a matching "}".
Wietse
Re: PATCH: Wildcard key and inline-maps
Dominik Chilla:
> Sorry, but it still doesnt work. I took a "vanilla" 3.1-20150721 and
> patched it again, checked if the patch applied correctly (searching for
> register_maps_byname() in smtpd_check.c etc.) and compiled the sources.
> When I leave out the leading "{" and the ending "}" it seems to work,
> but only if
>check_mumble_access inline:{send...@zwackl.de=OK},static:{REJECT BAD
> SENDER}
The new code was implemented to expect this:
check_sender_access {
inline:{send...@zwackl.de=OK}
static:{REJECT BAD SENDER}
}
(This time I added whitespace and newlines for readability.)
But, when you do this:
smtpd_sender_restrictions =
check_sender_access inline:{send...@zwackl.de=OK}
check_sender_access static:{REJECT BAD SENDER}
then it would solve the problem, too.
Wietse
Re: PATCH: Wildcard key and inline-maps
On Tue, Jul 28, 2015 at 11:37:19PM +0200, Dominik Chilla wrote:
> Sorry, but it still doesnt work. I took a "vanilla" 3.1-20150721 and patched
> it again, checked if the patch applied correctly (searching for
> register_maps_byname() in smtpd_check.c etc.) and compiled the sources.
>
> When I leave out the leading "{" and the ending "}" it seems to work, but
> only if
> check_mumble_access inline:{send...@zwackl.de=OK},static:{REJECT BAD SENDER}
That's wrong, it parses as:
check_mumble_access inline:{send...@zwackl.de=OK},
static:{REJECT BAD SENDER}
which is very different.
> When I specify
> check_mumble_access inline:{send...@zwackl.de=DUNNO},static:{REJECT BAD
> SENDER}
>
> the static map applies but ends with a reject.
>
> How would you test it? My ideas are running low :-/
You need to combine the two maps into one logical map:
check_mumble_access {
inline:{send...@zwackl.de=DUNNO},
static:{REJECT BAD SENDER}
}
Then if the first map returns DUNNO, the second should not be
consulted, unless the implementation is not yet quite right.
--
Viktor.
Re: PATCH: Wildcard key and inline-maps
Am 29.07.2015 um 00:01 schrieb Viktor Dukhovni:
On Tue, Jul 28, 2015 at 11:37:19PM +0200, Dominik Chilla wrote:
Sorry, but it still doesnt work. I took a "vanilla" 3.1-20150721 and patched
it again, checked if the patch applied correctly (searching for
register_maps_byname() in smtpd_check.c etc.) and compiled the sources.
When I leave out the leading "{" and the ending "}" it seems to work, but
only if
check_mumble_access inline:{send...@zwackl.de=OK},static:{REJECT BAD SENDER}
That's wrong, it parses as:
check_mumble_access inline:{send...@zwackl.de=OK},
static:{REJECT BAD SENDER}
which is very different.
Got it! It was a kind of an act of desperation :(
When I specify
check_mumble_access inline:{send...@zwackl.de=DUNNO},static:{REJECT BAD
SENDER}
the static map applies but ends with a reject.
How would you test it? My ideas are running low :-/
You need to combine the two maps into one logical map:
check_mumble_access {
inline:{send...@zwackl.de=DUNNO},
static:{REJECT BAD SENDER}
}
Yes, and that´s what I wanted to do.
Then if the first map returns DUNNO, the second should not be
consulted, unless the implementation is not yet quite right.
I don´t know why, but it works now!? The config is the same as before
(checked by diff).
As Wietse already pointed out, postconf doesn´t cover this case yet:
/usr/sbin/postconf: warning: main.cf: syntax error after '}' in
"{send...@zwackl.de=DUNNO},static:{REJECT BAD SENDER}}"
/usr/sbin/postconf: warning: main.cf: syntax error after '}' in
"{recipie...@zwackl.de=DUNNO},static:{REJECT BAD RECIPIENT}}"
Thank you very much for your help and the very fast solution!
... and sorry for my blindness ;)
Dominik
Re: SPF and forwarding
On Tue, 2015-07-28 at 16:50 -0400, Alex wrote: > Hi Andrew, > > > > This requires that you have access to the account from which the email > > > is being forwarded, correct? In my case, it is a single remote sender > > > that is being forwarded on to gmail. > > > > No, you need access to the account *to* which the email is forwarded. So > > assuming that the scenario is someone who has their own personal domain and > > is > > forwarding it to a gmail account that they own, then it should be possible. > > > > Of course, it would require each of your users to make this change, but > > they > > have the incentive to do so if it stops all their email ending up in their > > spam folder. > > Can I ask you to clarify? I'm not sure I understand. > > I'm trying to accomplish this for one specific mailbox right now. > > I have u...@company1.com sends mail to me at supp...@mycompany.com, > which then forwards it to u...@gmail.com where it is tagged as spam. > > I've added supp...@mycompany.com as an alternative address in gmail. I > don't have access to u...@company1.com. Yes, exactly that. You're telling Google Mail that mail arriving at u...@gmail.com might have actually been sent to supp...@mycompany.com instead. At least, that's the way I understand it, from reading the support topic previously posted. > Is that what you're doing? I've not actually tried it myself. It's just that I had a user with a similar problem (forwarding via my server), and this seemed to resolve it for them. Andy
Re: PATCH: Wildcard key and inline-maps
Dominik Chilla:
> As Wietse already pointed out, postconf doesn?t cover this case yet:
> /usr/sbin/postconf: warning: main.cf: syntax error after '}' in
> "{send...@zwackl.de=DUNNO},static:{REJECT BAD SENDER}}"
> /usr/sbin/postconf: warning: main.cf: syntax error after '}' in
> "{recipie...@zwackl.de=DUNNO},static:{REJECT BAD RECIPIENT}}"
Yup, I can reproduce that error message. I'll look into this
in the train to work tomorrow.
Wietse
OS accounts/users with @
Is it possible to make postfix handle OS usernames with @ in them? How to do it? My question is inspired (closely related but not identical) by http://serverfault.com/q/709153/163277 | Q: Postfix virtual domain mapping user for a user a linux name containing @ -- A. Filip
Re: OS accounts/users with @
On Wed, Jul 29, 2015 at 07:04:23AM +0200, Andrzej A. Filip wrote: > Is it possible to make postfix handle OS usernames with @ in them? The local(8) delivery agent does not support these. If you hand these off to some other delivery agent, then it is up to that agent. > How to do it? Can't be done. -- Viktor.
